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

2.134.13.0/24

7 residential-proxy exits · 30 days

JSC Kazakhtelecom

Announcement
2.134.0.0/18
RPKI valid
Announced by
AS9198
Type
Business
88% of it

Residential-proxy exits

Proxy exits
7
2.7% of its addresses · 30 days
Providers
39
selling exits here
Oct 12, 2026 – Nov 10, 2026

Exits seen per day

777 observations

Proxy providers listing exits

  • 2Captcha
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • EnigmaProxy
  • Evomi
  • FlashProxy
  • GSocks
  • Geonix
  • GonzoProxy
  • IPOasis
  • IPPeak
  • Infatica
  • InfiniteProxies
  • LemonBright
  • LemonLabs
  • MangoProxy
  • NSocks
  • NodeProxy
  • NovaProxy
  • Novada
  • PROXYSCRAPE
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyGeo
  • ProxyWing
  • Proxyma
  • RainProxy
  • Shifter
  • Smartproxy
  • Thordata
  • ThunderProxy
  • VantageProxies
  • VibeProxies
  • VitalExclusive
  • VitalProxy

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
2.132.0.0/14
since Jan 2011
AS9198Residential62,166
1,842 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.13.0/304NCERKZhelezinskyASSIGNED PAFeb 28, 2025abuse@telecom.kz
via KZ-KAZAKTELECOM-20101223
└ 2.134.13.4/304GUROZSOSHunknownASSIGNED PAMar 13, 2026abuse@telecom.kz
via KZ-KAZAKTELECOM-20101223
└ 2.134.13.8/304GUOTDELOBRAZOVANIYABayanaulskiy RayonASSIGNED PAAug 14, 2025abuse@telecom.kz
via KZ-KAZAKTELECOM-20101223
└ 2.134.13.16/304KGUKOMSERVICPAVLODARASSIGNED PAMar 4, 2025abuse@telecom.kz
via KZ-KAZAKTELECOM-20101223
└ 2.134.13.24/304ABAISOSHMaiskASSIGNED PAMar 28, 2025abuse@telecom.kz
via KZ-KAZAKTELECOM-20101223
└ 2.134.13.28/304OBLREBLCENTRPavlodarASSIGNED PAMar 4, 2025abuse@telecom.kz
via KZ-KAZAKTELECOM-20101223
└ 2.134.13.40/304SHKOLA1TERPAVLODARASSIGNED PAMar 5, 2025abuse@telecom.kz
via KZ-KAZAKTELECOM-20101223
└ 2.134.13.44/304GUSOSH4BAYANAULASSIGNED PAMar 17, 2025abuse@telecom.kz
via KZ-KAZAKTELECOM-20101223
└ 2.134.13.48/304SSHAINAKOLAKSUASSIGNED PAJun 20, 2025abuse@telecom.kz
via KZ-KAZAKTELECOM-20101223
└ 2.134.13.52/304GUSOSH2PavlodarASSIGNED PAMar 6, 2025abuse@telecom.kz
via KZ-KAZAKTELECOM-20101223
└ 2.134.13.56/304PravitgrazhdanunknownASSIGNED PAJun 2, 2026abuse@telecom.kz
via KZ-KAZAKTELECOM-20101223
└ 2.134.13.60/304SOSH14PavlodarASSIGNED PAMar 6, 2025abuse@telecom.kz
via KZ-KAZAKTELECOM-20101223
└ 2.134.13.64/2732GUTCITunknownASSIGNED PAMar 3, 2026abuse@telecom.kz
via KZ-KAZAKTELECOM-20101223
└ 2.134.13.96/2732IP_DIGITAL_ADEPTunknownASSIGNED PAApr 1, 2026abuse@telecom.kz
via KZ-KAZAKTELECOM-20101223
└ 2.134.13.128/304MIKRK_GCHPunknownASSIGNED PAJun 22, 2026abuse@telecom.kz
via KZ-KAZAKTELECOM-20101223
└ 2.134.13.132/304MIKRK_GCHPunknownASSIGNED PAJun 22, 2026abuse@telecom.kz
via KZ-KAZAKTELECOM-20101223
└ 2.134.13.136/304MIKRK_GCHPunknownASSIGNED PAJun 22, 2026abuse@telecom.kz
via KZ-KAZAKTELECOM-20101223
└ 2.134.13.140/304MIKRK_GCHPunknownASSIGNED PAJun 22, 2026abuse@telecom.kz
via KZ-KAZAKTELECOM-20101223
└ 2.134.13.144/304MIKRK_GCHPunknownASSIGNED PAJun 22, 2026abuse@telecom.kz
via KZ-KAZAKTELECOM-20101223
└ 2.134.13.148/304MIKRK_GCHPunknownASSIGNED PAJun 22, 2026abuse@telecom.kz
via KZ-KAZAKTELECOM-20101223
└ 2.134.13.152/304MIKRK_GCHPunknownASSIGNED PAJun 22, 2026abuse@telecom.kz
via KZ-KAZAKTELECOM-20101223
└ 2.134.13.156/304MIKRK_GCHPunknownASSIGNED PAJun 22, 2026abuse@telecom.kz
via KZ-KAZAKTELECOM-20101223
└ 2.134.13.160/304MIKRK_GCHPunknownASSIGNED PAJun 22, 2026abuse@telecom.kz
via KZ-KAZAKTELECOM-20101223
└ 2.134.13.164/304MIKRK_GCHPunknownASSIGNED PAJun 22, 2026abuse@telecom.kz
via KZ-KAZAKTELECOM-20101223
└ 2.134.13.168/304MIKRK_GCHPunknownASSIGNED PAJun 22, 2026abuse@telecom.kz
via KZ-KAZAKTELECOM-20101223
└ 2.134.13.172/304MIKRK_GCHPunknownASSIGNED PAJun 22, 2026abuse@telecom.kz
via KZ-KAZAKTELECOM-20101223
└ 2.134.13.176/304MIKRK_GCHPunknownASSIGNED PAJun 22, 2026abuse@telecom.kz
via KZ-KAZAKTELECOM-20101223
└ 2.134.13.180/304MIKRK_GCHPunknownASSIGNED PAJun 22, 2026abuse@telecom.kz
via KZ-KAZAKTELECOM-20101223
└ 2.134.13.184/304MIKRK_GCHPunknownASSIGNED PAJun 16, 2026abuse@telecom.kz
via KZ-KAZAKTELECOM-20101223
└ 2.134.13.188/304MIKRK_GCHPunknownASSIGNED PAJun 16, 2026abuse@telecom.kz
via KZ-KAZAKTELECOM-20101223
└ 2.134.13.192/304MIKRK_GCHPunknownASSIGNED PAJun 16, 2026abuse@telecom.kz
via KZ-KAZAKTELECOM-20101223
└ 2.134.13.196/304MIKRK_GCHPunknownASSIGNED PAJun 16, 2026abuse@telecom.kz
via KZ-KAZAKTELECOM-20101223
└ 2.134.13.200/304MIKRK_GCHPunknownASSIGNED PAJun 16, 2026abuse@telecom.kz
via KZ-KAZAKTELECOM-20101223
└ 2.134.13.204/304MIKRK_GCHPunknownASSIGNED PAJun 16, 2026abuse@telecom.kz
via KZ-KAZAKTELECOM-20101223
└ 2.134.13.208/304MIKRK_GCHPunknownASSIGNED PAJun 16, 2026abuse@telecom.kz
via KZ-KAZAKTELECOM-20101223
└ 2.134.13.212/304MIKRK_GCHPunknownASSIGNED PAJun 16, 2026abuse@telecom.kz
via KZ-KAZAKTELECOM-20101223
└ 2.134.13.216/304MIKRK_GCHPunknownASSIGNED PAJun 22, 2026abuse@telecom.kz
via KZ-KAZAKTELECOM-20101223
└ 2.134.13.220/304MIKRK_GCHPunknownASSIGNED PAJun 22, 2026abuse@telecom.kz
via KZ-KAZAKTELECOM-20101223
└ 2.134.13.224/304MIKRK_GCHPunknownASSIGNED PAJun 22, 2026abuse@telecom.kz
via KZ-KAZAKTELECOM-20101223
└ 2.134.13.228/304MIKRK_GCHPunknownASSIGNED PAJun 22, 2026abuse@telecom.kz
via KZ-KAZAKTELECOM-20101223
└ 2.134.13.232/304MIKRK_GCHPunknownASSIGNED PAJun 22, 2026abuse@telecom.kz
via KZ-KAZAKTELECOM-20101223
└ 2.134.13.236/304MIKRK_GCHPunknownASSIGNED PAJun 22, 2026abuse@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.

Composition

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

Announced space

Address share

Announced space

Types across the prefix

256 addresses
TypeAddressesShareRanges
Business22488%42
Residential3213%4

Network & registry

AnnouncementRouting historyRPKI & IRRWhois & abuse
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