Data as of Nov 12, 2026
2.133.128.0/18
3,875 residential-proxy exits · 30 daysJSC Kazakhtelecom
Residential-proxy exits
Proxy exits
3,875
24% of its addresses · 30 days
Always-on exits
30
0.77% of its exits
Spread
61 of 64
/24s with at least one exit
Providers
122
selling exits here
Oct 13, 2026 – Nov 11, 2026
Exits seen per day
324K observations
- Residential
- Business
/24s with the most always-on exits
| /24 | Always-on exits | Proxy exits | |
|---|---|---|---|
| 2.133.132.0/24 | 3 | 44 | |
| 2.133.181.0/24 | 2 | 67 | |
| 2.133.182.0/24 | 2 | 66 | |
| 2.133.152.0/24 | 2 | 62 | |
| 2.133.159.0/24 | 2 | 61 | |
| 2.133.130.0/24 | 2 | 9 | |
| 2.133.136.0/24 | 1 | 98 | |
| 2.133.175.0/24 | 1 | 79 | |
| 2.133.165.0/24 | 1 | 78 | |
| 2.133.156.0/24 | 1 | 75 | |
| 2.133.164.0/24 | 1 | 73 | |
| 2.133.154.0/24 | 1 | 73 | |
| 2.133.169.0/24 | 1 | 73 | |
| 2.133.172.0/24 | 1 | 72 | |
| 2.133.157.0/24 | 1 | 70 | |
| 2.133.184.0/24 | 1 | 66 | |
| 2.133.133.0/24 | 1 | 58 | |
| 2.133.189.0/24 | 1 | 58 | |
| 2.133.179.0/24 | 1 | 43 | |
| 2.133.134.0/24 | 1 | 42 | |
| 2.133.147.0/24 | 1 | 24 | |
| 2.133.128.0/24 | 1 | 8 | |
| 2.133.145.0/24 | 1 | 6 | |
| 2.133.142.0/24 | 0 | 122 |
Proxy providers listing exits
- 2Captcha
- 711Proxy
- 911Proxy
- 9Proxy
- ASHBURNPROXIES
- Ake.net
- AnyIP
- B2Proxy
- BartProxies
- BestProxy
- BirdProxies
- BlurPath
- BottingTools
- BuyingProxy
- ByteProxies
- Byteful
- CatProxies
- CliProxy
- DataImpulse
- Datarama
- Decodo
- EVOPROXY
- EZProxies
- EnigmaProxy
- Evomi
- FLEETPROXY
- FastProxy
- FlashProxy
- GSocks
- Geonix
- Geonode
- GhostConnect
- GloryCloud
- GoProxies
- GonzoProxy
- HPROXY
- HideProxy
- HydraProxy
- IPCola
- IPFly
- IPMUSK
- IPOasis
- IPPeak
- IPRoyal
- Infatica
- InfiniteProxies
- JoyProxy
- KindProxy
- KocerRoxy
- Kookey
- LUMIPROXY
- LemonBright
- LemonLabs
- LemonPrime
- LightningProxies
- LudaxProxy
- MagneticProxy
- MangoProxy
- Maskify
- MoMoProxy
- NSocks
- NextProxy
- NiuProxy
- NodeMaven
- NodeProxy
- NovProxy
- NovaProxy
- Novada
- Oxylabs
- PROXYON
- PROXYSCRAPE
- PROXYWING_BASIC
- PSBProxy
- PacketStream
- PrivateByte
- PrivateProxy
- ProxiesVision
- Proxio
- Proxiware
- Proxmint
- Proxy-Cheap
- Proxy-Seller
- Proxy302
- Proxy4U
- ProxyEmpire
- ProxyGeo
- ProxyHat
- ProxyRack
- ProxyStyler
- ProxyWing
- Proxying
- Proxyma
- PuraRoute
- Q2IP
- QUANTICDATA
- RH7Proxy
- RainProxy
- RapidProxy
- ResiProxies
- RoamProxy
- RolaProxy
- SPYDERPROXY_BASIC
- SPYDERPROXY_PREMIUM
- Shifter
- Smartproxy
- StrikeProxy
- SwiftProxy
- TORCHPROXIES_BASIC
- TORCHPROXIES_PREMIUM
- TORCHPROXIES_X
- TalorData
- Thordata
- ThunderProxy
- TrueProxies
- VantageProxies
- VibeProxies
- VitalData
- VitalExclusive
- VitalProxy
- YumiProxy
- ZENPROXY_LITE
- ZENPROXY_PREMIUM
Announcements
Less specific
Covering announcements
| Prefix | Origin | Type | Proxy exits | Holder | RPKI |
|---|---|---|---|---|---|
| 2.132.0.0/14 since Jan 2011 | AS9198 | Residential | 62,166 1,842 always on | JSC Kazakhtelecom |
Nesting
More-specifics by size
Sized by addresses, colored by each announcement's type. Click a tile with children to zoom in, a leaf to open it.
More specific
Announcements inside
| Prefix | Origin | Type | Proxy exits | Holder | RPKI |
|---|---|---|---|---|---|
| 2.133.132.0/22 since Dec 2016 | AS9198 | Residential | 184 5 always on | JSC Kazakhtelecom | |
| 2.133.136.0/21 since Dec 2016 | AS9198 | Residential | 850 1 always on | JSC Kazakhtelecom | |
| 2.133.149.0/24 since Oct 22, 2026 | AS9198 | Residential | JSC Kazakhtelecom | ||
| 2.133.150.0/24 since Jun 2026 | AS9198 | Residential | JSC Kazakhtelecom | ||
| 2.133.151.0/24 since Jun 2026 | AS9198 | Residential | JSC Kazakhtelecom | ||
| 2.133.152.0/21 since Jun 2017 | AS9198 | Residential | 553 7 always on | JSC Kazakhtelecom | |
| 2.133.160.0/22 since Jun 2017 | AS9198 | Residential | 275 | JSC Kazakhtelecom | |
| 2.133.164.0/22 since Sep 2017 | AS9198 | Residential | 282 2 always on | JSC Kazakhtelecom | |
| 2.133.176.0/20 since Sep 2021 | AS9198 | Residential | 992 7 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 | abuse@ |
| └ 2.133.147.184/30 | 4 | ITTSTSIK_ | Taldykorgan | ASSIGNED PA | Apr 2, 2024 | abuse@ via KZ-KAZAKTELECOM-20101223 |
| └ 2.133.147.192/30 | 4 | KRB_ | Taldykorgan | ASSIGNED PA | Mar 26, 2024 | abuse@ via KZ-KAZAKTELECOM-20101223 |
| └ 2.133.147.196/30 | 4 | SNP_ | Almatinskaya oblast | ASSIGNED PA | Mar 26, 2024 | abuse@ via KZ-KAZAKTELECOM-20101223 |
| └ 2.133.147.200/30 | 4 | KARAVAN | Taldykorgan | ASSIGNED PA | Mar 26, 2024 | abuse@ via KZ-KAZAKTELECOM-20101223 |
| └ 2.133.147.204/30 | 4 | KRB_ | Taldykorgan | ASSIGNED PA | Mar 27, 2024 | abuse@ via KZ-KAZAKTELECOM-20101223 |
| └ 2.133.147.208/30 | 4 | IP_ | Taldykorgan | ASSIGNED PA | Mar 27, 2024 | abuse@ via KZ-KAZAKTELECOM-20101223 |
| └ 2.133.147.212/30 | 4 | AKSU_ | Taldykorgan | ASSIGNED PA | Mar 27, 2024 | abuse@ via KZ-KAZAKTELECOM-20101223 |
| └ 2.133.147.216/30 | 4 | GU_ | Taldykorgan | ASSIGNED PA | Mar 27, 2024 | abuse@ via KZ-KAZAKTELECOM-20101223 |
| └ 2.133.147.220/30 | 4 | GU_ | Taldykorgan | ASSIGNED PA | Mar 27, 2024 | abuse@ via KZ-KAZAKTELECOM-20101223 |
| └ 2.133.147.224/30 | 4 | GU_ | Taldykorgan | ASSIGNED PA | Mar 27, 2024 | abuse@ via KZ-KAZAKTELECOM-20101223 |
| └ 2.133.147.232/30 | 4 | SARKAN_ | Taldykorgan | ASSIGNED PA | Mar 27, 2024 | abuse@ via KZ-KAZAKTELECOM-20101223 |
| └ 2.133.147.236/30 | 4 | GU_ | Taldykorgan | ASSIGNED PA | Apr 3, 2024 | abuse@ via KZ-KAZAKTELECOM-20101223 |
| └ 2.133.147.240/30 | 4 | ITTSTSIK_ | Taldykorgan | ASSIGNED PA | Mar 28, 2024 | abuse@ via KZ-KAZAKTELECOM-20101223 |
| └ 2.133.147.248/30 | 4 | KARAVAN | Taldykorgan | ASSIGNED PA | Mar 28, 2024 | abuse@ via KZ-KAZAKTELECOM-20101223 |
| └ 2.133.147.252/30 | 4 | PS-8 | unknown | ASSIGNED PA | Mar 28, 2024 | abuse@ via KZ-KAZAKTELECOM-20101223 |
| └ 2.133.148.128/27 | 32 | KHORGOS | Taldykorgan | ASSIGNED PA | Mar 14, 2025 | abuse@ via KZ-KAZAKTELECOM-20101223 |
| └ 2.133.148.176/28 | 16 | Alvia | unknown | ASSIGNED PA | May 26, 2026 | abuse@ via KZ-KAZAKTELECOM-20101223 |
| └ 2.133.148.192/26 | 64 | MTNMC_ | Otegen Batyra | ASSIGNED PA | Jan 12, 2026 | abuse@ via KZ-KAZAKTELECOM-20101223 |
| └ 2.133.150.0/24 | 256 | MTNMC_ | Almaty | ASSIGNED PA | Jun 23, 2026 | abuse@ via KZ-KAZAKTELECOM-20101223 |
| └ 2.133.151.0/24 | 256 | MTNMC_ | Almaty | ASSIGNED PA | Jun 23, 2026 | abuse@ via KZ-KAZAKTELECOM-20101223 |
| └ 2.133.152.0/22 | 1,024 | GPON_ | JSC Kazakhtelecom, Pavlodar Affiliate | ASSIGNED PA | May 13, 2011 | abuse@ via KZ-KAZAKTELECOM-20101223 |
| └ 2.133.156.0/23 | 512 | GPON_ | JSC Kazakhtelecom | ASSIGNED PA | Jun 26, 2014 | abuse@ via KZ-KAZAKTELECOM-20101223 |
| └ 2.133.158.0/23 | 512 | ALMATYTELECOM | JSC Kazakhtelecom, Almaty Affiliate | ASSIGNED PA | May 12, 2011 | abuse@ via KZ-KAZAKTELECOM-20101223 |
| └ 2.133.160.0/23 | 512 | GPON_ | JSC Kazakhtelecom | ASSIGNED PA | Jan 4, 2017 | abuse@ via KZ-KAZAKTELECOM-20101223 |
| └ 2.133.162.0/23 | 512 | GPON_ | JSC Kazakhtelecom | ASSIGNED PA | Jan 4, 2017 | abuse@ via KZ-KAZAKTELECOM-20101223 |
| └ 2.133.164.0/23 | 512 | GPON_ | JSC Kazakhtelecom | ASSIGNED PA | Jan 4, 2017 | abuse@ via KZ-KAZAKTELECOM-20101223 |
| └ 2.133.166.0/23 | 512 | MTNMCKAZAKTELECOMJSC | JSC Kazakhtelecom | ASSIGNED PA | Jan 4, 2017 | abuse@ via KZ-KAZAKTELECOM-20101223 |
| └ 2.133.168.0/21 | 2,048 | GPON_ | Almaty | ASSIGNED PA | Nov 9, 2015 | abuse@ via KZ-KAZAKTELECOM-20101223 |
| └ 2.133.176.0/20 | 4,096 | GPON_ | JSC Kazakhtelecom | ASSIGNED PA | Jun 11, 2020 | 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.
Composition
The types across the prefix's announced space, by addresses.
Announced space
Address share
Announced space
Types across the prefix
16,384 addresses
| Type | Addresses | Share | Ranges | |
|---|---|---|---|---|
| Residential | 14,540 | 89% | 52 | |
| Business | 1,844 | 11% | 411 |
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 2011
- Current origin since
- Dec 2016 · 9.9 yr
- Origin networks
- 1
RPKI
Route origin authorizations
| ROA prefix | ASN | Max len | Anchor | Verdict |
|---|---|---|---|---|
| 2.133.128.0/18 | AS9198 | /18 | RIPE | RPKI valid |
| 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 | Dec 6, 2011 |
IRR inside
Route objects inside
| Prefix | Origin | Registry | Description | Maintainer | Modified |
|---|---|---|---|---|---|
| 2.133.128.0/24 | AS9198 | RIPE | Kazakhtelecom Data Network Administration | KNIC-MNT | Dec 6, 2011 |
| 2.133.130.0/23 | AS9198 | RIPE | Kazakhtelecom Data Network Administration | KNIC-MNT | Dec 6, 2012 |
| 2.133.144.0/21 | AS9198 | RIPE | Kazakhtelecom Data Network Administration | KNIC-MNT | Jun 11, 2012 |
| 2.133.160.0/20 | 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
- abuse@
telecom. kz - Name
- Kazakhtelecom Network Information Center
- Handle
- KNIC1-RIPE