Data as of Nov 15, 2026

88.204.252.136/29

1 residential-proxy exit · 30 days

JSC Kazakhtelecom

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

Residential-proxy exits

Proxy exits
1
13% of its addresses · 30 days
Always-on exits
1
100% of its exits
Providers
32
selling exits here
Oct 16, 2026 – Nov 14, 2026

Exits seen per day

82 observations

Proxy providers listing exits

  • 2Captcha
  • 711Proxy
  • 911Proxy
  • ASHBURNPROXIES
  • Ake.net
  • AnyIP
  • BestProxy
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CROXY
  • Decodo
  • FlashProxy
  • Geonode
  • GonzoProxy
  • Infatica
  • InfiniteProxies
  • Kookey
  • LUMIPROXY
  • LemonBright
  • MangoProxy
  • NSocks
  • Proxy-Seller
  • ProxyEmpire
  • ProxyWing
  • Proxyma
  • RainProxy
  • Shifter
  • Smartproxy
  • VitalExclusive
  • ZENPROXY_PREMIUM

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
88.204.128.0/17
since Dec 2005
AS9198Residential741
61 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.252.136/298UPRAVLENIESIFROVIZASIIGU UpravleniesifrovizasiiASSIGNED PAFeb 17, 2022abuse@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.252.0/24

Routing history

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