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

88.204.201.4/30

No anonymizer space · no proxy exits in 30 days

JSC Kazakhtelecom

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

Residential-proxy exits

Proxy exits
7
100% of its addresses · listed by providers
Providers
40
selling exits here

Proxy providers listing exits

  • 2Captcha
  • 711Proxy
  • B2Proxy
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • EZProxies
  • EnigmaProxy
  • FastProxy
  • FlashProxy
  • GSocks
  • Geonix
  • GonzoProxy
  • IPFly
  • IPOasis
  • IPPeak
  • Infatica
  • LemonBright
  • LemonLabs
  • LemonPrime
  • MangoProxy
  • MoMoProxy
  • NodeProxy
  • NovaProxy
  • PROXYSCRAPE
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyHat
  • ProxyRack
  • Proxyma
  • PuraRoute
  • RainProxy
  • Shifter
  • Thordata
  • VantageProxies
  • VitalExclusive
  • VitalProxy

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
88.204.128.0/17
since Dec 2005
AS9198Residential750
35 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.201.4/304GUAAgPunknownASSIGNED PAJul 16, 2026abuse@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

AnnouncementRouting historyRPKI & IRRWhois & abuse
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