Data as of Nov 3, 2026
2.133.136.0/21
851 residential-proxy exits · 30 daysJSC Kazakhtelecom
Residential-proxy exits
Proxy exits
851
42% of its addresses · 30 days
Always-on exits
2
0.24% of its exits
Spread
8 of 8
/24s with at least one exit
Providers
93
selling exits here
Oct 4, 2026 – Nov 2, 2026
Exits seen per day
32K observations
/24s with the most always-on exits
| /24 | Always-on exits | Proxy exits | |
|---|---|---|---|
| 2.133.142.0/24 | 1 | 115 | |
| 2.133.136.0/24 | 1 | 101 | |
| 2.133.143.0/24 | 0 | 110 | |
| 2.133.139.0/24 | 0 | 108 | |
| 2.133.138.0/24 | 0 | 106 | |
| 2.133.141.0/24 | 0 | 105 | |
| 2.133.137.0/24 | 0 | 103 | |
| 2.133.140.0/24 | 0 | 102 |
Proxy providers listing exits
- 2Captcha
- 711Proxy
- 9Proxy
- Ake.net
- AnyIP
- B2Proxy
- BartProxies
- BestProxy
- BirdProxies
- BlurPath
- BottingTools
- BuyingProxy
- ByteProxies
- Byteful
- CatProxies
- CliProxy
- DataImpulse
- Datarama
- Decodo
- EZProxies
- EnigmaProxy
- Evomi
- FastProxy
- FlashProxy
- GSocks
- Geonix
- Geonode
- GhostConnect
- GloryCloud
- GoProxies
- GonzoProxy
- HideProxy
- HydraProxy
- IPCola
- IPFly
- IPOasis
- IPPeak
- IPRoyal
- Infatica
- InfiniteProxies
- KindProxy
- Kookey
- LemonBright
- LemonLabs
- LemonPrime
- LightningProxies
- LudaxProxy
- MangoProxy
- Maskify
- MoMoProxy
- NSocks
- NextProxy
- NiuProxy
- NodeMaven
- NodeProxy
- NovProxy
- NovaProxy
- Novada
- Oxylabs
- PrivateByte
- ProxiesVision
- Proxio
- Proxiware
- Proxmint
- Proxy-Seller
- Proxy302
- Proxy4U
- ProxyEmpire
- ProxyGeo
- ProxyHat
- ProxyRack
- ProxyWing
- Proxying
- Proxyma
- PuraRoute
- Q2IP
- RainProxy
- RapidProxy
- ResiProxies
- RoamProxy
- RolaProxy
- Shifter
- Smartproxy
- StrikeProxy
- SwiftProxy
- TalorData
- Thordata
- ThunderProxy
- VantageProxies
- VibeProxies
- VitalData
- VitalExclusive
- VitalProxy
Announcements
Less specific
Covering announcements
| Prefix | Origin | Type | Proxy exits | Holder | RPKI |
|---|---|---|---|---|---|
| 2.133.128.0/18 since Dec 2016 | AS9198 | Residential | 3,983 45 always on | JSC Kazakhtelecom | |
| 2.132.0.0/14 since Jan 2011 | AS9198 | Residential | 63,386 2,326 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.
| 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 | [email protected] |
| └ 2.133.136.0/22 | 1,024 | GPON_FTTH_SERVICES_KT | JSC Kazakhtelecom, Pavlodar Affiliate | ASSIGNED PA | May 13, 2011 | [email protected] via KZ-KAZAKTELECOM-20101223 |
| └ 2.133.140.0/22 | 1,024 | PVLMETRO | JSC Kazakhtelecom, Pavlodar Affiliate | ASSIGNED PA | May 13, 2011 | [email protected] 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
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
Summary
Routing history
- Pattern
- Stable
- First seen
- Jan 2016
- Current origin since
- Dec 2016 · 9.9 yr
- Origin networks
- 1
RPKI
Route origin authorizations
| ROA prefix | ASN | Max len | Anchor | Verdict |
|---|---|---|---|---|
| 2.133.136.0/21 | AS9198 | /24 | RIPE | RPKI valid |
| 2.133.128.0/18 | AS9198 | /18 | RIPE | Too specific |
| 2.132.0.0/14 | AS9198 | /24 | RIPE | RPKI valid |
IRR
Route objects on the exact prefix
| Origin | Registry | Description | Maintainer | Modified |
|---|---|---|---|---|
| AS9198 | RIPE | Kazakhtelecom Data Network Administration | KNIC-MNT | Jun 11, 2012 |
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
- [email protected]
- Name
- Kazakhtelecom Network Information Center
- Handle
- KNIC1-RIPE