Data as of Nov 12, 2026

2.134.14.0/24

12 residential-proxy exits · 30 days

JSC Kazakhtelecom

Announcement
RPKI valid
Announced by
Type
Business

Residential-proxy exits

Proxy exits
12
4.7% of its addresses · 30 days
Providers
27
selling exits here
Oct 13, 2026 – Nov 11, 2026

Exits seen per day

341 observations

Proxy providers listing exits

  • 711Proxy
  • 911Proxy
  • ASHBURNPROXIES
  • Ake.net
  • BestProxy
  • EZProxies
  • FastProxy
  • FlashProxy
  • IPFly
  • IPPeak
  • Infatica
  • LUMIPROXY
  • LemonBright
  • NSocks
  • NiuProxy
  • Proxiware
  • Proxy-Seller
  • Proxyma
  • PuraRoute
  • RainProxy
  • RoamProxy
  • RolaProxy
  • Shifter
  • Smartproxy
  • ThunderProxy
  • VitalExclusive
  • ZENPROXY_PREMIUM

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
2.132.0.0/14
since Jan 2011
AS9198Residential63,045
1,850 always on
JSC Kazakhtelecom

Registrations in this block

The registry's network records over this block, widest first, each under its parent.

RangeAddressesNetnameHolderTypeCreatedAbuse contact
2.132.0.0/14262,144KZ-KAZAKTELECOM-20101223JSC Kazakhtelecom (ORG-KDNA1-RIPE) · KZALLOCATED PADec 23, 2010abuse@telecom.kz
└ 2.134.14.0/304NCERKInderbor IndeASSIGNED PAFeb 28, 2025abuse@telecom.kz
via KZ-KAZAKTELECOM-20101223
└ 2.134.14.4/304NCERKKulsary ZhylyASSIGNED PAFeb 28, 2025abuse@telecom.kz
via KZ-KAZAKTELECOM-20101223
└ 2.134.14.8/304NCERKMakhambet MahaASSIGNED PAFeb 28, 2025abuse@telecom.kz
via KZ-KAZAKTELECOM-20101223
└ 2.134.14.12/304NCERKMakat MakatskiyASSIGNED PAFeb 28, 2025abuse@telecom.kz
via KZ-KAZAKTELECOM-20101223
└ 2.134.14.16/304NCERKAkkistau IssadASSIGNED PAFeb 28, 2025abuse@telecom.kz
via KZ-KAZAKTELECOM-20101223
└ 2.134.14.20/304NCERKMiyalyASSIGNED PAFeb 28, 2025abuse@telecom.kz
via KZ-KAZAKTELECOM-20101223
└ 2.134.14.24/304NCERKAtyrauASSIGNED PAFeb 28, 2025abuse@telecom.kz
via KZ-KAZAKTELECOM-20101223
└ 2.134.14.28/304ATYRMUZEYAtyrauASSIGNED PAMar 25, 2025abuse@telecom.kz
via KZ-KAZAKTELECOM-20101223
└ 2.134.14.32/304SCHOOLISATAIAtyrauASSIGNED PAMar 26, 2025abuse@telecom.kz
via KZ-KAZAKTELECOM-20101223
└ 2.134.14.36/304SENTRPODERJKSEMAtyrauASSIGNED PAApr 22, 2025abuse@telecom.kz
via KZ-KAZAKTELECOM-20101223
└ 2.134.14.40/304ODELZANYTSKULSAtyrauASSIGNED PAFeb 28, 2025abuse@telecom.kz
via KZ-KAZAKTELECOM-20101223
└ 2.134.14.44/304UILSKIOKRUGAtyrauASSIGNED PAMar 3, 2025abuse@telecom.kz
via KZ-KAZAKTELECOM-20101223
└ 2.134.14.48/304ATYRMUZEYAtyrauASSIGNED PAMar 25, 2025abuse@telecom.kz
via KZ-KAZAKTELECOM-20101223
└ 2.134.14.52/304SCHOOLISATAIAtyrauASSIGNED PAMar 26, 2025abuse@telecom.kz
via KZ-KAZAKTELECOM-20101223
└ 2.134.14.56/304SCHOOLISATAIAtyrauASSIGNED PAMar 26, 2025abuse@telecom.kz
via KZ-KAZAKTELECOM-20101223
└ 2.134.14.60/304SELHOZMAKATAtyrauASSIGNED PAMar 28, 2025abuse@telecom.kz
via KZ-KAZAKTELECOM-20101223
└ 2.134.14.64/2664ASTELAtyrauASSIGNED PAJul 21, 2025abuse@telecom.kz
via KZ-KAZAKTELECOM-20101223
└ 2.134.14.128/304ORGDNEVPOLUSTACIONARAtyrauASSIGNED PAFeb 18, 2025abuse@telecom.kz
via KZ-KAZAKTELECOM-20101223
└ 2.134.14.132/304OTDELTRANSPORTAAtyrauASSIGNED PAFeb 18, 2025abuse@telecom.kz
via KZ-KAZAKTELECOM-20101223
└ 2.134.14.136/304METODOSENTRAtyrauASSIGNED PASep 8, 2025abuse@telecom.kz
via KZ-KAZAKTELECOM-20101223
└ 2.134.14.140/304SCHOOLGIM44AtyrauASSIGNED PAFeb 26, 2025abuse@telecom.kz
via KZ-KAZAKTELECOM-20101223
└ 2.134.14.144/304ORLEUAtyrau cityASSIGNED PAFeb 21, 2025abuse@telecom.kz
via KZ-KAZAKTELECOM-20101223
└ 2.134.14.148/304YASLISAD18BALDYRGANAtyrauASSIGNED PAFeb 26, 2025abuse@telecom.kz
via KZ-KAZAKTELECOM-20101223
└ 2.134.14.152/304DETSKAIADEREVNYAunknownASSIGNED PAFeb 17, 2026abuse@telecom.kz
via KZ-KAZAKTELECOM-20101223
└ 2.134.14.156/304VETSTANSYAKYZYLKOGAtyrauASSIGNED PAFeb 26, 2025abuse@telecom.kz
via KZ-KAZAKTELECOM-20101223
└ 2.134.14.160/304IRGLTDunknownASSIGNED PAApr 17, 2026abuse@telecom.kz
via KZ-KAZAKTELECOM-20101223
└ 2.134.14.164/304KURMANGAZYBOLNICAunknownASSIGNED PAMay 13, 2026abuse@telecom.kz
via KZ-KAZAKTELECOM-20101223
└ 2.134.14.168/304VETSTANSYAKYZYLKOGAtyrauASSIGNED PAFeb 26, 2025abuse@telecom.kz
via KZ-KAZAKTELECOM-20101223
└ 2.134.14.172/304VETSTANSYAKYZYLKOGAtyrauASSIGNED PAFeb 26, 2025abuse@telecom.kz
via KZ-KAZAKTELECOM-20101223
└ 2.134.14.176/304VETSTANSYAKYZYLKOGAtyrauASSIGNED PAFeb 26, 2025abuse@telecom.kz
via KZ-KAZAKTELECOM-20101223
└ 2.134.14.180/304VETSTANSYAKYZYLKOGunknownASSIGNED PAApr 17, 2026abuse@telecom.kz
via KZ-KAZAKTELECOM-20101223
└ 2.134.14.184/304VETSTANSYAKYZYLKOGAtyrauASSIGNED PAFeb 26, 2025abuse@telecom.kz
via KZ-KAZAKTELECOM-20101223
└ 2.134.14.188/304VETSTANSYAKYZYLKOGAtyrauASSIGNED PAFeb 26, 2025abuse@telecom.kz
via KZ-KAZAKTELECOM-20101223
└ 2.134.14.192/304TOROSIPunknownASSIGNED PASep 29, 2026abuse@telecom.kz
via KZ-KAZAKTELECOM-20101223
└ 2.134.14.196/304AKIMATZHANAKARATONAtyrauASSIGNED PANov 13, 2024abuse@telecom.kz
via KZ-KAZAKTELECOM-20101223
└ 2.134.14.200/304TEEZLOGISTICSKulsaryASSIGNED PANov 18, 2024abuse@telecom.kz
via KZ-KAZAKTELECOM-20101223
└ 2.134.14.204/304AKZHAKIMGAtyrauASSIGNED PAOct 2, 2025abuse@telecom.kz
via KZ-KAZAKTELECOM-20101223
└ 2.134.14.208/2816NISGUWAtyrauASSIGNED PAJul 19, 2024abuse@telecom.kz
via KZ-KAZAKTELECOM-20101223
└ 2.134.14.224/304ATYROBLTERRINSPEKCIYAAtyrauASSIGNED PAJun 27, 2024abuse@telecom.kz
via KZ-KAZAKTELECOM-20101223
└ 2.134.14.228/304ATYROBLTERRINSPEKCIYAAtyrauASSIGNED PAJun 10, 2024abuse@telecom.kz
via KZ-KAZAKTELECOM-20101223
└ 2.134.14.232/304KOMITETRYBHOZAtyrauASSIGNED PAJun 11, 2024abuse@telecom.kz
via KZ-KAZAKTELECOM-20101223
└ 2.134.14.236/304SPORTSCHOOLGEMAtyrauASSIGNED PAJun 11, 2024abuse@telecom.kz
via KZ-KAZAKTELECOM-20101223
└ 2.134.14.240/304SANEPIDKONTRAtyrauASSIGNED PAJun 20, 2024abuse@telecom.kz
via KZ-KAZAKTELECOM-20101223
└ 2.134.14.244/304UPRAVLENIEPREDRINIMATELSTVAAtyrauASSIGNED PAJun 14, 2024abuse@telecom.kz
via KZ-KAZAKTELECOM-20101223
└ 2.134.14.248/304AFLPRAVGRARAZHDANAtyrauASSIGNED PAJun 14, 2024abuse@telecom.kz
via KZ-KAZAKTELECOM-20101223
└ 2.134.14.252/304MAHAMBETRAIONBOLNICAAtyrauASSIGNED PAJun 18, 2024abuse@telecom.kz
via KZ-KAZAKTELECOM-20101223

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

Routing timeline

Covering aggregate above, the prefix's own history below

2.134.0.0/18

Routing history

Pattern
Stable
First seen
Jan 2011
Current origin since
Oct 2016 · 10 yr
Origin networks
1