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

2.133.22.0/24

6 residential-proxy exits · 30 days

JSC Kazakhtelecom

Announcement
2.133.0.0/18
RPKI valid
Announced by
AS9198
Type
Business
73% of it

Residential-proxy exits

Proxy exits
6
2.3% of its addresses · 30 days
Providers
36
selling exits here
Oct 11, 2026 – Nov 9, 2026

Exits seen per day

570 observations

Proxy providers listing exits

  • 2Captcha
  • 711Proxy
  • ASHBURNPROXIES
  • BestProxy
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • FastProxy
  • FlashProxy
  • GSocks
  • Geonix
  • GonzoProxy
  • IPOasis
  • Infatica
  • LemonBright
  • LemonLabs
  • LightningProxies
  • MangoProxy
  • NSocks
  • NodeProxy
  • NovaProxy
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyHat
  • Proxyma
  • RainProxy
  • Shifter
  • Smartproxy
  • Thordata
  • VibeProxies
  • VitalExclusive
  • VitalProxy
  • ZENPROXY_PREMIUM

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
2.132.0.0/14
since Jan 2011
AS9198Residential61,303
2,294 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.133.22.32/304GKKPKAMERNYIORKESTRunknownASSIGNED PAFeb 2, 2024abuse@telecom.kz
via KZ-KAZAKTELECOM-20101223
└ 2.133.22.40/304OO_CHINGIRLAUKlishiva d 89 A in Chingirlau rn. ZKOASSIGNED PAFeb 5, 2024abuse@telecom.kz
via KZ-KAZAKTELECOM-20101223
└ 2.133.22.52/304OO_CHINGIRLAUChingirlauASSIGNED PAFeb 5, 2024abuse@telecom.kz
via KZ-KAZAKTELECOM-20101223
└ 2.133.22.56/304OO_CHINGIRLAUChingirlauASSIGNED PAFeb 5, 2024abuse@telecom.kz
via KZ-KAZAKTELECOM-20101223
└ 2.133.22.60/304OO_CHINGIRLAUChingirlauASSIGNED PAFeb 5, 2024abuse@telecom.kz
via KZ-KAZAKTELECOM-20101223
└ 2.133.22.64/304IPSERIKOVRUSTAMunknownASSIGNED PANov 6, 2026abuse@telecom.kz
via KZ-KAZAKTELECOM-20101223
└ 2.133.22.68/304GU_Zhangala_maslihatURALSKASSIGNED PAFeb 7, 2024abuse@telecom.kz
via KZ-KAZAKTELECOM-20101223
└ 2.133.22.72/304POLICLINICA_5URALSKASSIGNED PAApr 12, 2024abuse@telecom.kz
via KZ-KAZAKTELECOM-20101223
└ 2.133.22.76/304OTDEL_OBROZOVANIAAnkatiASSIGNED PAFeb 12, 2024abuse@telecom.kz
via KZ-KAZAKTELECOM-20101223
└ 2.133.22.80/304OTDEL_OBRAZOV_KAZTALOVSKOGO_RAIONAURALSKASSIGNED PAFeb 12, 2024abuse@telecom.kz
via KZ-KAZAKTELECOM-20101223
└ 2.133.22.84/304GKKP_Tsentr_dosugaURALSKASSIGNED PAFeb 12, 2024abuse@telecom.kz
via KZ-KAZAKTELECOM-20101223
└ 2.133.22.88/304OTDEL_OBROZOVANIASariOmirASSIGNED PAFeb 13, 2024abuse@telecom.kz
via KZ-KAZAKTELECOM-20101223
└ 2.133.22.104/304OTDEL_OBROZOVANIAAkzhaikASSIGNED PAFeb 13, 2024abuse@telecom.kz
via KZ-KAZAKTELECOM-20101223
└ 2.133.22.116/304KH_SKITunknownASSIGNED PAApr 22, 2026abuse@telecom.kz
via KZ-KAZAKTELECOM-20101223
└ 2.133.22.120/304GKKP_Tsentr_dosugaURALSKASSIGNED PAFeb 14, 2024abuse@telecom.kz
via KZ-KAZAKTELECOM-20101223
└ 2.133.22.128/304NCERKUralskASSIGNED PAFeb 28, 2025abuse@telecom.kz
via KZ-KAZAKTELECOM-20101223
└ 2.133.22.132/304NCERKAksai BurlinskyASSIGNED PAFeb 28, 2025abuse@telecom.kz
via KZ-KAZAKTELECOM-20101223
└ 2.133.22.136/304ZHANGALA_RAION_OOURALSKASSIGNED PAFeb 26, 2024abuse@telecom.kz
via KZ-KAZAKTELECOM-20101223
└ 2.133.22.140/304DEP_JUSTICEZKOASSIGNED PAJun 3, 2024abuse@telecom.kz
via KZ-KAZAKTELECOM-20101223
└ 2.133.22.144/304MEDKOLLEDZHUralskASSIGNED PAJan 17, 2025abuse@telecom.kz
via KZ-KAZAKTELECOM-20101223
└ 2.133.22.148/304ZHANGALA_RAION_OOURALSKASSIGNED PAFeb 26, 2024abuse@telecom.kz
via KZ-KAZAKTELECOM-20101223
└ 2.133.22.152/304ZHANGALA_RAION_OOURALSKASSIGNED PAFeb 26, 2024abuse@telecom.kz
via KZ-KAZAKTELECOM-20101223
└ 2.133.22.156/304ZHANGALA_RAION_OOURALSKASSIGNED PAFeb 27, 2024abuse@telecom.kz
via KZ-KAZAKTELECOM-20101223
└ 2.133.22.160/304GK_PRAVITELSTVO_GRASHDANunknownASSIGNED PAFeb 20, 2026abuse@telecom.kz
via KZ-KAZAKTELECOM-20101223
└ 2.133.22.164/304ZHANGALA_RAION_OOURALSKASSIGNED PAFeb 27, 2024abuse@telecom.kz
via KZ-KAZAKTELECOM-20101223
└ 2.133.22.168/304AKIMAT_POLTAVKAUralskASSIGNED PAFeb 27, 2024abuse@telecom.kz
via KZ-KAZAKTELECOM-20101223
└ 2.133.22.172/304ZHANGALA_RAION_OOURALSKASSIGNED PAFeb 27, 2024abuse@telecom.kz
via KZ-KAZAKTELECOM-20101223
└ 2.133.22.176/304ZHANGALA_RAION_OOURALSKASSIGNED PAFeb 27, 2024abuse@telecom.kz
via KZ-KAZAKTELECOM-20101223
└ 2.133.22.180/304ZHANGALA_RAION_OOURALSKASSIGNED PAFeb 27, 2024abuse@telecom.kz
via KZ-KAZAKTELECOM-20101223
└ 2.133.22.184/304GKKP_KOKKTLZHURALSKASSIGNED PAFeb 29, 2024abuse@telecom.kz
via KZ-KAZAKTELECOM-20101223
└ 2.133.22.188/304SOSH27unknownASSIGNED PAFeb 24, 2026abuse@telecom.kz
via KZ-KAZAKTELECOM-20101223
└ 2.133.22.192/304GKKPZHANGALYNSKYRCDOSUGAURALSKASSIGNED PAFeb 29, 2024abuse@telecom.kz
via KZ-KAZAKTELECOM-20101223
└ 2.133.22.196/304GU_CBSZKOASSIGNED PAApr 23, 2025abuse@telecom.kz
via KZ-KAZAKTELECOM-20101223
└ 2.133.22.200/304OTDEL_OBRAZOV_KAZTALOVSKOGO_RAIONAURALSKASSIGNED PAMar 1, 2024abuse@telecom.kz
via KZ-KAZAKTELECOM-20101223
└ 2.133.22.204/304FORESTCONSERVATIONORDAURALSKASSIGNED PAMar 1, 2024abuse@telecom.kz
via KZ-KAZAKTELECOM-20101223
└ 2.133.22.208/304GU_UPRAVLENIE_PO_DELAM_RELIGIIunknownASSIGNED PAMar 17, 2026abuse@telecom.kz
via KZ-KAZAKTELECOM-20101223
└ 2.133.22.212/304CSAUralskASSIGNED PAMar 2, 2024abuse@telecom.kz
via KZ-KAZAKTELECOM-20101223
└ 2.133.22.216/304OTDEL_OBRAZOV_KAZTALOVSKOGO_RAIONAURALSKASSIGNED PAMar 4, 2024abuse@telecom.kz
via KZ-KAZAKTELECOM-20101223
└ 2.133.22.220/304OTDEL_OBRAZOV_KAZTALOVSKOGO_RAIONAURALSKASSIGNED PAMar 4, 2024abuse@telecom.kz
via KZ-KAZAKTELECOM-20101223
└ 2.133.22.224/304GKP_VETERINARIYURALSKASSIGNED PAMar 4, 2024abuse@telecom.kz
via KZ-KAZAKTELECOM-20101223
└ 2.133.22.228/304Terektinskay_centralnay_raionnay_bolnicaunknownASSIGNED PAApr 21, 2026abuse@telecom.kz
via KZ-KAZAKTELECOM-20101223
└ 2.133.22.232/304AKIMAT_BUDARINO_OKRUGAkzhaikskyi RaionASSIGNED PAMar 4, 2024abuse@telecom.kz
via KZ-KAZAKTELECOM-20101223
└ 2.133.22.236/304ZHANGALA_RAION_OOURALSKASSIGNED PAMar 29, 2024abuse@telecom.kz
via KZ-KAZAKTELECOM-20101223
└ 2.133.22.240/304ZHANGALA_RAION_OOURALSKASSIGNED PAMar 5, 2024abuse@telecom.kz
via KZ-KAZAKTELECOM-20101223
└ 2.133.22.244/304ZHANGALA_RAION_OOURALSKASSIGNED PAMar 5, 2024abuse@telecom.kz
via KZ-KAZAKTELECOM-20101223
└ 2.133.22.248/304AKIMAT_FEDOROVKAURALSKASSIGNED PAMar 6, 2024abuse@telecom.kz
via KZ-KAZAKTELECOM-20101223
└ 2.133.22.252/304ZHANGALA_RAION_OOURALSKASSIGNED PAMar 6, 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.

Composition

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

Announced space

Address share

Announced space

Types across the prefix

256 addresses
TypeAddressesShareRanges
Business18873%47
Residential6827%6

Network & registry

AnnouncementRouting historyRPKI & IRRWhois & abuse
Routing timeline

Covering aggregate above, the prefix's own history below

2.133.0.0/18

Routing history

Pattern
Stable
First seen
Jan 2011
Current origin since
Jan 2017 · 9.8 yr
Origin networks
1