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

88.204.239.4/30

1 residential-proxy exit · 30 days

JSC Kazakhtelecom

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

Residential-proxy exits

Proxy exits
1
25% of its addresses · 30 days
Always-on exits
1
100% of its exits
Providers
41
selling exits here
Oct 12, 2026 – Nov 10, 2026

Exits seen per day

1.3K observations

Proxy providers listing exits

  • 2Captcha
  • 711Proxy
  • ASHBURNPROXIES
  • Ake.net
  • AnyIP
  • B2Proxy
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • EZProxies
  • Evomi
  • FastProxy
  • FlashProxy
  • Geonode
  • GonzoProxy
  • IPPeak
  • Infatica
  • InfiniteProxies
  • LemonBright
  • LightningProxies
  • LudaxProxy
  • NSocks
  • NodeMaven
  • NovaProxy
  • PrivateByte
  • PrivateProxy
  • Proxy-Seller
  • ProxyEmpire
  • Proxyma
  • RainProxy
  • RolaProxy
  • Shifter
  • Smartproxy
  • ThunderProxy
  • TrueProxies
  • VibeProxies
  • VitalExclusive
  • VitalProxy
  • YumiProxy
  • ZENPROXY_LITE

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
88.204.128.0/17
since Dec 2005
AS9198Residential739
37 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.239.4/304InfinityLifeMTAAstanaASSIGNED PAMar 11, 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

AnnouncementRouting historyRPKI & IRRWhois & abuse
Routing timeline

Covering aggregate above, the prefix's own history below

88.204.238.0/23

Routing history

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