Data as of Nov 11, 2026

2.133.20.0/23

54 residential-proxy exits · 30 days

JSC Kazakhtelecom

Announcement
this exact prefix
RPKI valid
Announced by
Type
Residential
Risk
0 / 100 · Low

Residential-proxy exits

Proxy exits
54
11% of its addresses · 30 days
Spread
2 of 2
/24s with at least one exit
Providers
64
selling exits here
Oct 12, 2026 – Nov 10, 2026

Exits seen per day

2.3K observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
2.133.21.0/24028
2.133.20.0/24026

Proxy providers listing exits

  • 711Proxy
  • Ake.net
  • B2Proxy
  • BestProxy
  • BirdProxies
  • BlurPath
  • BottingTools
  • BuyingProxy
  • ByteProxies
  • Byteful
  • CliProxy
  • DataImpulse
  • Datarama
  • Decodo
  • EZProxies
  • EnigmaProxy
  • Evomi
  • FlashProxy
  • GSocks
  • Geonix
  • Geonode
  • GhostConnect
  • GloryCloud
  • GonzoProxy
  • IPFly
  • IPPeak
  • IPRoyal
  • Infatica
  • InfiniteProxies
  • KindProxy
  • Kookey
  • LemonBright
  • LemonLabs
  • LemonPrime
  • MangoProxy
  • MoMoProxy
  • NSocks
  • NodeProxy
  • NovaProxy
  • Novada
  • Oxylabs
  • Proxio
  • Proxiware
  • Proxy-Seller
  • Proxy4U
  • ProxyEmpire
  • ProxyGeo
  • ProxyHat
  • ProxyRack
  • ProxyWing
  • Proxyma
  • PuraRoute
  • RainProxy
  • RapidProxy
  • RolaProxy
  • Shifter
  • Smartproxy
  • StrikeProxy
  • TalorData
  • Thordata
  • ThunderProxy
  • VantageProxies
  • VitalData
  • VitalExclusive

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
2.133.0.0/18
since Jan 2017
AS9198Residential3,823
32 always on
JSC Kazakhtelecom
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 the announcement: those covering it, widest first, then every record inside it, under its parent.

RangeAddressesNetnameHolderTypeCreatedAbuse contact
2.132.0.0/14262,144KZ-KAZAKTELECOM-20101223JSC Kazakhtelecom (ORG-KDNA1-RIPE) · KZALLOCATED PADec 23, 2010abuse@telecom.kz
└ 2.133.20.0/23512GPON_FTTH_SERVICESAstanaASSIGNED PAJun 8, 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.

Network & registry

Routing timeline

Covering aggregate above, the prefix's own history below

Summary

Routing history

Pattern
Stable
First seen
Dec 2020
Current origin since
Sep 2021 · 5.1 yr
Origin networks
1