LAYER3 INTEL
Get started
Sign in
Data as of Nov 13, 2026

178.91.50.32/30

1 residential-proxy exit · 30 days

JSC Kazakhtelecom

Announcement
178.91.32.0/19
RPKI valid
Announced by
AS9198
Type
Business
Risk
0 / 100 · Low

Residential-proxy exits

Proxy exits
1
25% of its addresses · 30 days
Providers
36
selling exits here
Oct 14, 2026 – Nov 12, 2026

Exits seen per day

457 observations

Proxy providers listing exits

  • 2Captcha
  • 711Proxy
  • AnyIP
  • BestProxy
  • BirdProxies
  • ByteProxies
  • Byteful
  • CROXY
  • EnigmaProxy
  • GSocks
  • Geonix
  • GonzoProxy
  • Infatica
  • KocerRoxy
  • LemonBright
  • MangoProxy
  • NSocks
  • NodeProxy
  • NovaProxy
  • Novada
  • PROXYSALE
  • PROXY_CC
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyRack
  • ProxyWing
  • Proxyma
  • RainProxy
  • Shifter
  • Smartproxy
  • Thordata
  • ThunderProxy
  • VantageProxies
  • VitalExclusive
  • ZENPROXY_PREMIUM

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
178.88.0.0/14
since Dec 2009
AS9198Residential65,439
1,677 always on
JSC Kazakhtelecom

Registrations in this block

The registry's network records over this block, widest first, each under its parent.

RangeAddressesNetnameHolderTypeCreatedAbuse contact
178.88.0.0/14262,144KZ-KAZAKTELECOM-20091126JSC Kazakhtelecom (ORG-KDNA1-RIPE) · KZALLOCATED PANov 26, 2009abuse@telecom.kz
└ 178.91.50.32/304IPUKBAYEVAtyrauASSIGNED PAFeb 7, 2022abuse@telecom.kz
via KZ-KAZAKTELECOM-20091126

A contact marked “via” is the registry's: the record names none of its own, so the registry hands down its parent's.

Network & registry

AnnouncementRouting historyRPKI & IRRWhois & abuse
Routing timeline

Covering aggregate above, the prefix's own history below

178.91.32.0/19

Routing history

Pattern
Stable
First seen
Dec 2009
Current origin since
Aug 2025 · 1.3 yr
Origin networks
1