Data as of Nov 13, 2026

88.204.239.0/24

3 residential-proxy exits · 30 days

JSC Kazakhtelecom

Announcement
RPKI valid
Announced by
Type
Residential
53% of it

Residential-proxy exits

Proxy exits
3
1.2% of its addresses · 30 days
Always-on exits
1
33% of its exits
Providers
44
selling exits here
Oct 14, 2026 – Nov 12, 2026

Exits seen per day

2.8K observations

Proxy providers listing exits

  • 2Captcha
  • 711Proxy
  • ASHBURNPROXIES
  • Ake.net
  • AnyIP
  • B2Proxy
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • EZProxies
  • Evomi
  • FastProxy
  • FlashProxy
  • Geonode
  • GonzoProxy
  • IPPeak
  • IPROCKET_BASIC
  • IPROCKET_PREMIUM
  • Infatica
  • InfiniteProxies
  • LemonBright
  • LightningProxies
  • LudaxProxy
  • NSocks
  • NodeMaven
  • NovaProxy
  • PrivateByte
  • PrivateProxy
  • Proxy-Seller
  • ProxyEmpire
  • Proxyma
  • Q2IP
  • 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
AS9198Residential747
42 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
└ 88.204.239.8/304TOO_QUALCOMMFORASTLTDunknownASSIGNED PAMay 23, 2018abuse@telecom.kz
via KZ-KAZAKTELECOM-20051201
└ 88.204.239.12/304TOOASTANAGULDERITooAstanaGulderiASSIGNED PAJan 30, 2012abuse@telecom.kz
via KZ-KAZAKTELECOM-20051201
└ 88.204.239.16/298IP_ODT_AKTOBEIgor KorkinASSIGNED PAAug 25, 2017abuse@telecom.kz
via KZ-KAZAKTELECOM-20051201
└ 88.204.239.32/304KAZINFOSYSTEMSAstanaASSIGNED PANov 28, 2024abuse@telecom.kz
via KZ-KAZAKTELECOM-20051201
└ 88.204.239.36/304POSRKTYPCIIPOSRKTYPCIIASSIGNED PAJun 15, 2011abuse@telecom.kz
via KZ-KAZAKTELECOM-20051201
└ 88.204.239.40/298JASQADunknownASSIGNED PASep 15, 2026abuse@telecom.kz
via KZ-KAZAKTELECOM-20051201
└ 88.204.239.64/2816RGPNAYCHMEDCENTRRGPNAYCHMEDCENTRASSIGNED PAOct 8, 2009abuse@telecom.kz
via KZ-KAZAKTELECOM-20051201
└ 88.204.239.80/304KGU_DOLGOLETAstanaASSIGNED PAApr 25, 2023abuse@telecom.kz
via KZ-KAZAKTELECOM-20051201
└ 88.204.239.88/304ORIENTSOLUTIONSOrient Solutions ltdASSIGNED PAApr 1, 2007abuse@telecom.kz
via KZ-KAZAKTELECOM-20051201
└ 88.204.239.152/304DAIGGAGY DAIGGA, AstanaASSIGNED PAMay 22, 2008abuse@telecom.kz
via KZ-KAZAKTELECOM-20051201
└ 88.204.239.156/304TRADISHNALAstanaASSIGNED PADec 11, 2019abuse@telecom.kz
via KZ-KAZAKTELECOM-20051201
└ 88.204.239.160/304TOO_HYPEROPTIC_QASTANA,Abaya 27ASSIGNED PAMar 20, 2025abuse@telecom.kz
via KZ-KAZAKTELECOM-20051201
└ 88.204.239.180/304KSN_COMKAZComitet kaznacheystva Ministry of Finance of KazakhstanASSIGNED PAJun 6, 2016abuse@telecom.kz
via KZ-KAZAKTELECOM-20051201
└ 88.204.239.184/304TOO_BIOTECHNur-SultanASSIGNED PANov 29, 2023abuse@telecom.kz
via KZ-KAZAKTELECOM-20051201
└ 88.204.239.204/304TOO_SKIFTREIDg.AstanaASSIGNED PAMay 5, 2025abuse@telecom.kz
via KZ-KAZAKTELECOM-20051201
└ 88.204.239.208/304OSMPKZOSMPLLPASSIGNED PAJul 15, 2011abuse@telecom.kz
via KZ-KAZAKTELECOM-20051201
└ 88.204.239.212/304TOOINTEGRITYTOOINTEGRITYASSIGNED PAJun 29, 2017abuse@telecom.kz
via KZ-KAZAKTELECOM-20051201
└ 88.204.239.220/304RGPDGRUDPREZIDENTRGPDGRUDPREZIDENTASSIGNED PADec 21, 2011abuse@telecom.kz
via KZ-KAZAKTELECOM-20051201
└ 88.204.239.232/298SAMRUKJoint-stock company holding SAMRUK/P2P AstanaASSIGNED PASep 5, 2011abuse@telecom.kz
via KZ-KAZAKTELECOM-20051201
└ 88.204.239.240/298IP_KT_Clound_LabDinzhanov ErkinASSIGNED PAJan 30, 2012abuse@telecom.kz
via KZ-KAZAKTELECOM-20051201
└ 88.204.239.248/298TOODPDKAZTOODPDKAZASSIGNED PAJul 18, 2011abuse@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.

Composition

The types across the prefix's announced space, by addresses.

Announced space

Address share

Announced space

Types across the prefix

256 addresses
TypeAddressesShareRanges
Residential13653%9
Business12047%22

Network & registry

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