Data as of Nov 14, 2026

2.132.80.0/21

768 residential-proxy exits · 30 days

JSC Kazakhtelecom

Announcement
RPKI valid
Announced by
Type
Residential

Residential-proxy exits

Proxy exits
768
38% of its addresses · 30 days
Always-on exits
631
82% of its exits
Spread
3 of 8
/24s with at least one exit
Providers
44
selling exits here
Oct 15, 2026 – Nov 13, 2026

Exits seen per day

806K observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
2.132.80.0/24212256
2.132.82.0/24211255
2.132.81.0/24208256

Proxy providers listing exits

  • 711Proxy
  • AnyIP
  • BirdProxies
  • BottingTools
  • Bright Data
  • ByteProxies
  • Byteful
  • CliProxy
  • DataImpulse
  • Decodo
  • Evomi
  • FlashProxy
  • Geonode
  • GoProxies
  • GonzoProxy
  • IPRoyal
  • Infatica
  • Kookey
  • LemonBright
  • MangoProxy
  • Maskify
  • MoMoProxy
  • NSocks
  • NiuProxy
  • NodeProxy
  • NovaProxy
  • Oxylabs
  • PacketStream
  • PrivateProxy
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyRack
  • ProxyWing
  • Proxying
  • Proxyma
  • RainProxy
  • RapidProxy
  • Shifter
  • StrikeProxy
  • Thordata
  • ThunderProxy
  • VitalExclusive
  • Webshare

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
2.132.0.0/14
since Jan 2011
AS9198Residential63,191
1,822 always on
JSC Kazakhtelecom
More specific

Announcements inside

PrefixOriginTypeProxy exitsHolderRPKI
2.132.80.0/23
since Oct 22, 2026
AS9198Residential512
420 always on
JSC Kazakhtelecom
2.132.82.0/23
since Oct 22, 2026
AS9198Residential255
211 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.132.80.0/212,048MTNMCKAZAKTELECOMJSCJSC Kazakhtelecom, Kazakhstan Online BackboneASSIGNED PASep 16, 2015abuse@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.132.0.0/17

Routing history

Pattern
Stable
First seen
Jan 2011
Current origin since
Sep 2021 · 5.2 yr
Origin networks
1