Data as of Nov 18, 2026

88.204.208.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
12
100% of its addresses · listed by providers
Providers
47
selling exits here

Proxy providers listing exits

  • 2Captcha
  • 711Proxy
  • 911Proxy
  • 9HTTP
  • APROXY
  • BestProxy
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • FastProxy
  • FlashProxy
  • GSocks
  • Geonix
  • GonzoProxy
  • HydraProxy
  • IPOasis
  • Infatica
  • KocerRoxy
  • LUMIPROXY
  • LemonBright
  • LightningProxies
  • MangoProxy
  • NSocks
  • NiuProxy
  • NodeMaven
  • NodeProxy
  • Novada
  • Oxylabs
  • PROXYSALE
  • PROXY_CC
  • Proxies.fo
  • Proxy-Seller
  • ProxyEmpire
  • ProxyWing
  • Proxyma
  • PuraRoute
  • RainProxy
  • Shifter
  • Smartproxy
  • Thordata
  • ThunderProxy
  • VibeProxies
  • VitalData
  • VitalExclusive
  • VitalProxy
  • ZENPROXY_PREMIUM

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
88.204.128.0/17
since Dec 2005
AS9198Residential762
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.208.76/304RADIACIAVKODTASSIGNED PAMay 21, 2013abuse@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.208.0/23

Routing history

Pattern
Stable
First seen
May 2008
Current origin since
Nov 2023 · 3.0 yr
Origin networks
1