Data as of Nov 6, 2026
2.132.80.0/21
768 residential-proxy exits · 30 daysJSC Kazakhtelecom
Residential-proxy exits
Proxy exits
768
38% of its addresses · 30 days
Always-on exits
713
93% of its exits
Spread
3 of 8
/24s with at least one exit
Providers
34
selling exits here
Oct 7, 2026 – Nov 5, 2026
Exits seen per day
738K observations
/24s with the most always-on exits
| /24 | Always-on exits | Proxy exits | |
|---|---|---|---|
| 2.132.80.0/24 | 241 | 256 | |
| 2.132.81.0/24 | 238 | 256 | |
| 2.132.82.0/24 | 234 | 254 |
Proxy providers listing exits
- 711Proxy
- AnyIP
- BirdProxies
- BottingTools
- Bright Data
- ByteProxies
- Byteful
- DataImpulse
- Decodo
- Evomi
- FlashProxy
- Geonode
- GoProxies
- GonzoProxy
- IPRoyal
- Infatica
- InfiniteProxies
- Kookey
- LemonBright
- Maskify
- NSocks
- Oxylabs
- PacketStream
- Proxy-Seller
- Proxy4U
- ProxyEmpire
- ProxyRack
- ProxyWing
- Proxying
- Proxyma
- StrikeProxy
- Thordata
- ThunderProxy
- Webshare
Announcements
Less specific
Covering announcements
| Prefix | Origin | Type | Proxy exits | Holder | RPKI |
|---|---|---|---|---|---|
| 2.132.0.0/14 since Jan 2011 | AS9198 | Residential | 61,220 2,327 always on | JSC Kazakhtelecom |
More specific
Announcements inside
| Prefix | Origin | Type | Proxy exits | Holder | RPKI |
|---|---|---|---|---|---|
| 2.132.80.0/23 since Oct 22, 2026 | AS9198 | Residential | 512 479 always on | JSC Kazakhtelecom | |
| 2.132.82.0/23 since Oct 22, 2026 | AS9198 | Residential | 254 234 always on | JSC Kazakhtelecom |
Registrations in this block
The registry's network records over this block, widest first, each under its parent.
| Range | Addresses | Netname | Holder | Type | Created | Abuse contact |
|---|---|---|---|---|---|---|
| 2.132.0.0/14 | 262,144 | KZ-KAZAKTELECOM-20101223 | JSC Kazakhtelecom (ORG-KDNA1-RIPE) · KZ | ALLOCATED PA | Dec 23, 2010 | abuse@ |
| └ 2.132.80.0/21 | 2,048 | MTNMCKAZAKTELECOMJSC | JSC Kazakhtelecom, Kazakhstan Online Backbone | ASSIGNED PA | Sep 16, 2015 | abuse@ 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
Announced by
Covering announcement 2.132.0.0/17
- Prefix
- 2.132.0.0/17
- Announced by
- AS9198 JSC Kazakhtelecom
- Type
- Residential
- Proxy exits
- 8,593
- Always-on exits
- 793
- RPKI
- RPKI valid
- Netname
- KZ-KAZAKTELECOM-20101223
- Registrant
- JSC Kazakhtelecom
- RIR
- RIPE NCC
Origin network
AS9198
KZ
- Name
- JSC Kazakhtelecom
- Type
- Internet provider
- Registered
- Feb 23, 1999
- Domain
- telecom.kz
- Website
- www.telecom.kz
- Industry
- Internet Service Provider (ISP)
- Spamhaus ASN-DROP
- not listed
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.1 yr
- Origin networks
- 1
RPKI
Route origin authorizations
| ROA prefix | ASN | Max len | Anchor | Verdict |
|---|---|---|---|---|
| 2.132.0.0/17 | AS9198 | /17 | RIPE | RPKI valid |
| 2.132.0.0/14 | AS9198 | /24 | RIPE | RPKI valid |
IRR
Route objects on 2.132.0.0/17
| Origin | Registry | Description | Maintainer | Modified |
|---|---|---|---|---|
| AS9198 | RIPE | Kazakhtelecom Data Network Administration | KNIC-MNT | Dec 6, 2011 |
Whois
Registration for this announcement
- Range
- 2.
132. 0. 0/ 14 - Netname
- KZ-KAZAKTELECOM-20101223
- Registrant
- JSC Kazakhtelecom
- Registrant country
- KZ
- Organization
- JSC Kazakhtelecom (ORG-KDNA1-RIPE)
- Org country
- KZ
- Type
- ALLOCATED PA
- Created
- Dec 23, 2010
- Updated
- Jun 23, 2016
- Maintainer
- RIPE-NCC-HM-MNT
- RIR
- RIPE NCC
- Country
- KZ
- Delegated
- Dec 23, 2010
- Status
- assigned
Report abuse
Abuse contact
- abuse@
telecom. kz - Name
- Kazakhtelecom Network Information Center
- Handle
- KNIC1-RIPE