Data as of Nov 11, 2026

5.104.232.0/21

150 residential-proxy exits · 30 days

JSC Kazakhtelecom

Announcement
this exact prefix
RPKI valid
Announced by
Type
Residential
69% of it

Residential-proxy exits

Proxy exits
150
7.3% of its addresses · 30 days
Always-on exits
2
1.3% of its exits
Spread
6 of 8
/24s with at least one exit
Providers
102
selling exits here
Oct 12, 2026 – Nov 10, 2026

Exits seen per day

15K observations
  • Residential
  • Business

/24s with the most always-on exits

Proxy providers listing exits

  • 2Captcha
  • 711Proxy
  • 911Proxy
  • 9Proxy
  • ASHBURNPROXIES
  • Ake.net
  • AnyIP
  • B2Proxy
  • BartProxies
  • BestProxy
  • BirdProxies
  • BlurPath
  • BottingTools
  • BuyingProxy
  • ByteProxies
  • Byteful
  • CatProxies
  • CliProxy
  • DataImpulse
  • Datarama
  • Decodo
  • EVOPROXY
  • EZProxies
  • EnigmaProxy
  • Evomi
  • FLEETPROXY
  • FastProxy
  • FlashProxy
  • GSocks
  • Geonix
  • Geonode
  • GhostConnect
  • GloryCloud
  • GonzoProxy
  • HideProxy
  • IPFly
  • IPOasis
  • IPPeak
  • IPRoyal
  • Infatica
  • InfiniteProxies
  • KindProxy
  • Kookey
  • LUMIPROXY
  • LemonBright
  • LemonLabs
  • LemonPrime
  • LudaxProxy
  • MangoProxy
  • Maskify
  • MoMoProxy
  • NSocks
  • NextProxy
  • NiuProxy
  • NodeMaven
  • NodeProxy
  • NovProxy
  • NovaProxy
  • Novada
  • Oxylabs
  • PROXYSCRAPE
  • PROXYWING_BASIC
  • PrivateProxy
  • ProxiesVision
  • Proxio
  • Proxiware
  • Proxmint
  • Proxy-Cheap
  • Proxy-Seller
  • Proxy302
  • Proxy4U
  • ProxyEmpire
  • ProxyGeo
  • ProxyHat
  • ProxyRack
  • ProxyWing
  • Proxyma
  • PuraRoute
  • Q2IP
  • QUANTICDATA
  • RH7Proxy
  • RainProxy
  • RapidProxy
  • RealProxy
  • ResiProxies
  • RoamProxy
  • SPYDERPROXY_PREMIUM
  • Shifter
  • Smartproxy
  • StrikeProxy
  • SwiftProxy
  • TORCHPROXIES_BASIC
  • TalorData
  • Thordata
  • ThunderProxy
  • VantageProxies
  • VibeProxies
  • VitalExclusive
  • VitalProxy
  • YumiProxy
  • ZENPROXY_LITE
  • ZENPROXY_PREMIUM

Announcements

More specific

Announcements inside

PrefixOriginTypeProxy exitsHolderRPKI
5.104.232.0/23
since Mar 2020
AS9198Residential79
2 always on
JSC Kazakhtelecom
5.104.238.0/23
since Mar 2020
AS9198Residential70JSC Kazakhtelecom

Registrations in this block

The registry's network records over the announcement: those covering it, widest first, then every record inside it, under its parent.

RangeAddressesNetnameHolderTypeCreatedAbuse contact
5.104.232.0/212,048KZ-KAZAKTELECOM-20110102JSC Kazakhtelecom (ORG-KDNA1-RIPE) · KZALLOCATED PAJul 2, 2012abuse@telecom.kz
└ 5.104.232.0/23512GPON_FTTH_SERVICESJSC KazakhtelecomASSIGNED PAJun 19, 2020abuse@telecom.kz
via KZ-KAZAKTELECOM-20110102
└ 5.104.234.0/24256IP_NBIunknownASSIGNED PAMay 21, 2026abuse@telecom.kz
via KZ-KAZAKTELECOM-20110102
└ 5.104.235.0/304HOMECREDITAstana, str Ilyas Zhansugurov 8/1ASSIGNED PAJan 22, 2025abuse@telecom.kz
via KZ-KAZAKTELECOM-20110102
└ 5.104.235.4/304RGUEkologKontrAstanaASSIGNED PAFeb 10, 2023abuse@telecom.kz
via KZ-KAZAKTELECOM-20110102
└ 5.104.235.8/298QRITYMOBILETELECOMAstanaASSIGNED PAJan 15, 2025abuse@telecom.kz
via KZ-KAZAKTELECOM-20110102
└ 5.104.235.16/298MTNMC_Kazakhtelecom_DSCvDNS # INTERNET#RPZ VM/HC VMASSIGNED PAFeb 21, 2023abuse@telecom.kz
via KZ-KAZAKTELECOM-20110102
└ 5.104.235.24/304RGUFINASTAstanaASSIGNED PAJan 11, 2024abuse@telecom.kz
via KZ-KAZAKTELECOM-20110102
└ 5.104.235.28/304ADMPREZIAstanaASSIGNED PAJan 22, 2025abuse@telecom.kz
via KZ-KAZAKTELECOM-20110102
└ 5.104.235.32/304TOOSMARTCOMMUNAstanaASSIGNED PAFeb 28, 2025abuse@telecom.kz
via KZ-KAZAKTELECOM-20110102
└ 5.104.235.48/2816DISSC Kazakhtelecom, Direction of Information SystemsASSIGNED PAJul 19, 2019abuse@telecom.kz
via KZ-KAZAKTELECOM-20110102
└ 5.104.235.80/298ENRC_MANAGMENTunknownASSIGNED PAAug 20, 2026abuse@telecom.kz
via KZ-KAZAKTELECOM-20110102
└ 5.104.235.88/298IP_NBILLC «nbi»ASSIGNED PAOct 8, 2020abuse@telecom.kz
via KZ-KAZAKTELECOM-20110102
└ 5.104.235.96/304MKZOLOTOAstanaASSIGNED PAApr 10, 2025abuse@telecom.kz
via KZ-KAZAKTELECOM-20110102
└ 5.104.235.100/304TOORAZIONLAZIYAAstanaASSIGNED PAMar 6, 2023abuse@telecom.kz
via KZ-KAZAKTELECOM-20110102
└ 5.104.235.104/304SHKOLA13_ASTAstanaASSIGNED PAJan 17, 2025abuse@telecom.kz
via KZ-KAZAKTELECOM-20110102
└ 5.104.235.108/304IP_MTB_KAZAKHSTANNur-SultanASSIGNED PANov 1, 2022abuse@telecom.kz
via KZ-KAZAKTELECOM-20110102
└ 5.104.235.112/304IP_AIMYSHEVCo-locationASSIGNED PAJan 29, 2019abuse@telecom.kz
via KZ-KAZAKTELECOM-20110102
└ 5.104.235.120/304TOO_RAHATASNur-SultanASSIGNED PAJan 29, 2021abuse@telecom.kz
via KZ-KAZAKTELECOM-20110102
└ 5.104.235.128/2732IP_ELECTRONIC_COMMERCE_CENTERAstanaASSIGNED PAMar 29, 2023abuse@telecom.kz
via KZ-KAZAKTELECOM-20110102
└ 5.104.235.160/298TLSZ_FNPRAVdlyaGrazhAstanaASSIGNED PAJan 6, 2023abuse@telecom.kz
via KZ-KAZAKTELECOM-20110102
└ 5.104.235.168/298IP_KAZSATGROUP_LOGISTICLLC ?kazsatgroup Logistic?ASSIGNED PAMay 13, 2019abuse@telecom.kz
via KZ-KAZAKTELECOM-20110102
└ 5.104.235.176/304SAMRUKKAZYNATRUSTg.AstanaASSIGNED PAJan 14, 2025abuse@telecom.kz
via KZ-KAZAKTELECOM-20110102
└ 5.104.235.180/304POS_YKRAINANur-SultanASSIGNED PAJul 4, 2022abuse@telecom.kz
via KZ-KAZAKTELECOM-20110102
└ 5.104.235.184/304ARGROUP_KZNur-Sultan., Kerey Zhanibek Handar str. 32ASSIGNED PADec 10, 2021abuse@telecom.kz
via KZ-KAZAKTELECOM-20110102
└ 5.104.235.188/304ARGROUP_KZNur-Sultan., Kerey Zhanibek Handar str. 32ASSIGNED PADec 10, 2021abuse@telecom.kz
via KZ-KAZAKTELECOM-20110102
└ 5.104.235.192/2732IP_DKPDKPASSIGNED PAJan 10, 2019abuse@telecom.kz
via KZ-KAZAKTELECOM-20110102
└ 5.104.235.240/298MEZHDUNAR_SHKOLANur-SultanASSIGNED PAJan 29, 2021abuse@telecom.kz
via KZ-KAZAKTELECOM-20110102
└ 5.104.235.248/298FNEKOMAOGKPRDGRAJDANunknownASSIGNED PAFeb 27, 2026abuse@telecom.kz
via KZ-KAZAKTELECOM-20110102
└ 5.104.236.16/2816CANALIZAPROGNAstanaASSIGNED PAOct 22, 2025abuse@telecom.kz
via KZ-KAZAKTELECOM-20110102
└ 5.104.236.36/304MECHTA_MARKETAstanaASSIGNED PAFeb 6, 2019abuse@telecom.kz
via KZ-KAZAKTELECOM-20110102
└ 5.104.236.40/304PROFKOLLEDZHAstanaASSIGNED PAFeb 7, 2019abuse@telecom.kz
via KZ-KAZAKTELECOM-20110102
└ 5.104.236.44/304TOO_BASHKIRAstanaASSIGNED PAFeb 7, 2019abuse@telecom.kz
via KZ-KAZAKTELECOM-20110102
└ 5.104.236.48/304INTERNATKAZHAstanaASSIGNED PAFeb 13, 2019abuse@telecom.kz
via KZ-KAZAKTELECOM-20110102
└ 5.104.236.56/298AO_TELEKOMNur-SultanASSIGNED PAApr 2, 2022abuse@telecom.kz
via KZ-KAZAKTELECOM-20110102
└ 5.104.236.88/298TOO_CENTRISSLEDAstanaASSIGNED PAFeb 18, 2019abuse@telecom.kz
via KZ-KAZAKTELECOM-20110102
└ 5.104.236.104/304TOO_KAZINVESTAstanaASSIGNED PAMar 14, 2019abuse@telecom.kz
via KZ-KAZAKTELECOM-20110102
└ 5.104.236.108/304NobelDentalAstanaASSIGNED PAFeb 3, 2025abuse@telecom.kz
via KZ-KAZAKTELECOM-20110102
└ 5.104.236.128/25128IP_DKPRent a RackASSIGNED PASep 25, 2023abuse@telecom.kz
via KZ-KAZAKTELECOM-20110102
└ 5.104.237.0/25128KSN_DENSAULYKAkkol cityASSIGNED PAApr 16, 2025abuse@telecom.kz
via KZ-KAZAKTELECOM-20110102
└ 5.104.237.128/25128KSN_DENSAULYKAkkol cityASSIGNED PAApr 16, 2025abuse@telecom.kz
via KZ-KAZAKTELECOM-20110102
└ 5.104.238.0/23512GPON_FTTH_SERVICESJSC KazakhtelecomASSIGNED PAMay 21, 2021abuse@telecom.kz
via KZ-KAZAKTELECOM-20110102

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

2,048 addresses
TypeAddressesShareRanges
Residential1,41269%15
Business62831%36
Mobile80.39%1

Network & registry

Routing timeline

Who has announced this prefix

Summary

Routing history

Pattern
Stable
First seen
Jul 2012
Current origin since
Jan 2016 · 11 yr
Origin networks
2
Last change of origin
Jan 2016
Recorded history

History

Handoffs
1