Data as of Nov 19, 2026

88.204.203.76/30

No anonymizer space · no proxy exits in 30 days

JSC Kazakhtelecom

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

Residential-proxy exits

Proxy exits
6
100% of its addresses · listed by providers
Always-on exits
1
17% of its exits
Providers
53
selling exits here

Proxy providers listing exits

  • 2Captcha
  • 711Proxy
  • 9HTTP
  • AnyIP
  • BestProxy
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CROXY
  • CliProxy
  • Decodo
  • EnigmaProxy
  • FlashProxy
  • GSocks
  • Geonix
  • Geonode
  • GonzoProxy
  • IPFly
  • IPOasis
  • IPPeak
  • Infatica
  • InfiniteProxies
  • Kookey
  • LemonBright
  • LightningProxies
  • MangoProxy
  • NSocks
  • NodeMaven
  • NodeProxy
  • NovProxy
  • NovaProxy
  • Novada
  • PrivateProxy
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyRack
  • ProxyWing
  • Proxyma
  • PuraRoute
  • RainProxy
  • RoamProxy
  • Shifter
  • Smartproxy
  • StrikeProxy
  • Thordata
  • ThunderProxy
  • VantageProxies
  • VibeProxies
  • VitalExclusive
  • VitalProxy
  • ZENPROXY_PREMIUM

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
88.204.128.0/17
since Dec 2005
AS9198Residential767
68 always on
JSC Kazakhtelecom

Registrations in this block

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

RangeAddressesNetnameHolderTypeCreatedAbuse contact
88.204.128.0/1732,768KZ-KAZAKTELECOM-20051201JSC Kazakhtelecom (ORG-KDNA1-RIPE) · KZALLOCATED PADec 1, 2005abuse@telecom.kz
└ 88.204.203.76/304PRAVGRAZHPVLPavlodarASSIGNED PAJan 15, 2024abuse@telecom.kz
via KZ-KAZAKTELECOM-20051201

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

Routing timeline

Covering aggregate above, the prefix's own history below

88.204.200.0/22

Routing history

Pattern
Stable
First seen
May 2008
Current origin since
May 2008 · 19 yr
Origin networks
1