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

88.204.248.76/30

No anonymizer space · no proxy exits in 30 days

JSC Kazakhtelecom

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

Residential-proxy exits

Proxy exits
6
100% of its addresses · listed by providers
Providers
43
selling exits here

Proxy providers listing exits

  • 2Captcha
  • 711Proxy
  • 911Proxy
  • APROXY
  • AnyIP
  • BestProxy
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CROXY
  • CliProxy
  • EnigmaProxy
  • Evomi
  • FastProxy
  • GSocks
  • Geonix
  • Geonode
  • GonzoProxy
  • IPPeak
  • Infatica
  • InfiniteProxies
  • KocerRoxy
  • LemonBright
  • LemonLabs
  • LemonPrime
  • MangoProxy
  • NSocks
  • NodeProxy
  • NovaProxy
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • Proxyma
  • RainProxy
  • SIMPLYNODE
  • Shifter
  • Smartproxy
  • Thordata
  • ThunderProxy
  • VantageProxies
  • 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.248.76/304TOOBIRINSHILOMBARDKazigurtASSIGNED PASep 9, 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

AnnouncementRouting historyRPKI & IRRWhois & abuse
Routing timeline

Covering aggregate above, the prefix's own history below

88.204.248.0/23

Routing history

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