Data as of Nov 10, 2026
2.134.0.0/18
3,709 residential-proxy exits · 30 daysJSC Kazakhtelecom
Residential-proxy exits
Proxy exits
3,709
23% of its addresses · 30 days
Always-on exits
42
1.1% of its exits
Spread
54 of 64
/24s with at least one exit
Providers
118
selling exits here
Oct 11, 2026 – Nov 9, 2026
Exits seen per day
247K observations
- Residential
- Business
/24s with the most always-on exits
| /24 | Always-on exits | Proxy exits | |
|---|---|---|---|
| 2.134.17.0/24 | 3 | 73 | |
| 2.134.42.0/24 | 3 | 69 | |
| 2.134.16.0/24 | 3 | 60 | |
| 2.134.39.0/24 | 3 | 53 | |
| 2.134.38.0/24 | 2 | 72 | |
| 2.134.30.0/24 | 2 | 71 | |
| 2.134.43.0/24 | 2 | 65 | |
| 2.134.25.0/24 | 2 | 63 | |
| 2.134.8.0/24 | 2 | 60 | |
| 2.134.40.0/24 | 2 | 60 | |
| 2.134.27.0/24 | 2 | 57 | |
| 2.134.37.0/24 | 2 | 56 | |
| 2.134.51.0/24 | 1 | 103 | |
| 2.134.45.0/24 | 1 | 76 | |
| 2.134.31.0/24 | 1 | 74 | |
| 2.134.26.0/24 | 1 | 70 | |
| 2.134.22.0/24 | 1 | 68 | |
| 2.134.18.0/24 | 1 | 64 | |
| 2.134.29.0/24 | 1 | 63 | |
| 2.134.23.0/24 | 1 | 62 | |
| 2.134.33.0/24 | 1 | 61 | |
| 2.134.24.0/24 | 1 | 61 | |
| 2.134.7.0/24 | 1 | 61 | |
| 2.134.19.0/24 | 1 | 59 |
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
- FuseProxy
- GSocks
- Geonix
- Geonode
- GhostConnect
- GloryCloud
- GoProxies
- GonzoProxy
- HPROXY
- HideProxy
- HydraProxy
- IPCola
- IPFly
- IPMUSK
- IPOasis
- IPPeak
- IPRoyal
- Infatica
- InfiniteProxies
- KindProxy
- KocerRoxy
- Kookey
- LUMIPROXY
- LemonBright
- LemonLabs
- LemonPrime
- LightningProxies
- LudaxProxy
- MangoProxy
- Maskify
- MoMoProxy
- NSocks
- NextProxy
- NiuProxy
- NodeMaven
- NodeProxy
- NovProxy
- NovaProxy
- Novada
- Oxylabs
- PROXYON
- PROXYSCRAPE
- PROXYWING_BASIC
- PacketStream
- PrivateByte
- PrivateProxy
- Proxies.fo
- ProxiesVision
- Proxio
- Proxiware
- Proxmint
- Proxy-Seller
- Proxy302
- Proxy4U
- ProxyEmpire
- ProxyGeo
- ProxyHat
- ProxyRack
- ProxyStyler
- ProxyWing
- Proxying
- Proxyma
- PuraRoute
- Q2IP
- QUANTICDATA
- RH7Proxy
- RainProxy
- RapidProxy
- RealProxy
- ResiProxies
- RoamProxy
- RolaProxy
- SPYDERPROXY_BASIC
- SPYDERPROXY_PREMIUM
- Shifter
- Smartproxy
- StrikeProxy
- SwiftProxy
- 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 | 61,303 2,294 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.134.4.0/22 since Sep 2017 | AS9198 | Residential | 232 3 always on | JSC Kazakhtelecom | |
| 2.134.8.0/22 since Oct 2016 | AS9198 | Residential | 221 2 always on | JSC Kazakhtelecom | |
| 2.134.16.0/20 since Sep 2021 | AS9198 | Residential | 1,037 20 always on | JSC Kazakhtelecom | |
| 2.134.32.0/22 since Oct 2016 | AS9198 | Residential | 212 1 always on | JSC Kazakhtelecom | |
| 2.134.36.0/22 since Jan 2017 | AS9198 | Residential | 229 7 always on | JSC Kazakhtelecom | |
| 2.134.40.0/24 since Jan 2021 | AS9198 | Residential | 60 2 always on | JSC Kazakhtelecom | |
| 2.134.42.0/24 since May 2019 | AS9198 | Residential | 69 3 always on | JSC Kazakhtelecom | |
| 2.134.43.0/24 since May 2019 | AS9198 | Residential | 65 2 always on | JSC Kazakhtelecom | |
| 2.134.44.0/22 since Feb 2018 | AS9198 | Residential | 345 1 always on | JSC Kazakhtelecom | |
| 2.134.48.0/21 since Dec 2014 | AS9198 | Residential | 868 1 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.134.4.0/22 | 1,024 | GPON_ | JSC Kazakhtelecom | ASSIGNED PA | Oct 25, 2019 | abuse@ via KZ-KAZAKTELECOM-20101223 |
| └ 2.134.8.0/22 | 1,024 | GPON_ | JSC Kazakhtelecom | ASSIGNED PA | Jan 5, 2017 | abuse@ via KZ-KAZAKTELECOM-20101223 |
| └ 2.134.12.0/30 | 4 | AGENTSTVO_ | Qostanai | ASSIGNED PA | Dec 31, 2024 | abuse@ via KZ-KAZAKTELECOM-20101223 |
| └ 2.134.12.4/30 | 4 | ZARECH_ | unknown | ASSIGNED PA | Feb 17, 2026 | abuse@ via KZ-KAZAKTELECOM-20101223 |
| └ 2.134.12.8/30 | 4 | AO_ | unknown | ASSIGNED PA | May 13, 2026 | abuse@ via KZ-KAZAKTELECOM-20101223 |
| └ 2.134.12.12/30 | 4 | DEPART_ | Qostanai | ASSIGNED PA | Jan 5, 2025 | abuse@ via KZ-KAZAKTELECOM-20101223 |
| └ 2.134.12.16/30 | 4 | EPK_ | Amangeldy | ASSIGNED PA | Mar 5, 2025 | abuse@ via KZ-KAZAKTELECOM-20101223 |
| └ 2.134.12.20/30 | 4 | MIKRK_ | unknown | ASSIGNED PA | Jun 22, 2026 | abuse@ via KZ-KAZAKTELECOM-20101223 |
| └ 2.134.12.24/30 | 4 | SHKOLA_ | Qostanai | ASSIGNED PA | Jan 6, 2025 | abuse@ via KZ-KAZAKTELECOM-20101223 |
| └ 2.134.12.28/30 | 4 | RUD_ | unknown | ASSIGNED PA | Feb 17, 2026 | abuse@ via KZ-KAZAKTELECOM-20101223 |
| └ 2.134.12.32/30 | 4 | RUD_ | unknown | ASSIGNED PA | Feb 17, 2026 | abuse@ via KZ-KAZAKTELECOM-20101223 |
| └ 2.134.12.36/30 | 4 | RUD_ | unknown | ASSIGNED PA | Feb 17, 2026 | abuse@ via KZ-KAZAKTELECOM-20101223 |
| └ 2.134.12.40/30 | 4 | OTDEL_ | RC Tobyl | ASSIGNED PA | Feb 17, 2025 | abuse@ via KZ-KAZAKTELECOM-20101223 |
| └ 2.134.12.44/30 | 4 | SRED_ | Qostanai | ASSIGNED PA | Jan 8, 2025 | abuse@ via KZ-KAZAKTELECOM-20101223 |
| └ 2.134.12.48/30 | 4 | OTDEL_ | unknown | ASSIGNED PA | Apr 10, 2026 | abuse@ via KZ-KAZAKTELECOM-20101223 |
| └ 2.134.12.52/30 | 4 | CENTR_ | Malaia Churakovka | ASSIGNED PA | Jan 8, 2025 | abuse@ via KZ-KAZAKTELECOM-20101223 |
| └ 2.134.12.56/30 | 4 | SHKOLA_ | Tobyl | ASSIGNED PA | Jan 8, 2025 | abuse@ via KZ-KAZAKTELECOM-20101223 |
| └ 2.134.12.60/30 | 4 | RUD_ | unknown | ASSIGNED PA | Feb 17, 2026 | abuse@ via KZ-KAZAKTELECOM-20101223 |
| └ 2.134.12.64/30 | 4 | ALTYNSARIN_ | Malaia Churakovka | ASSIGNED PA | Jan 8, 2025 | abuse@ via KZ-KAZAKTELECOM-20101223 |
| └ 2.134.12.68/30 | 4 | ALTYNSARIN_ | Malaia Churakovka | ASSIGNED PA | Jan 8, 2025 | abuse@ via KZ-KAZAKTELECOM-20101223 |
| └ 2.134.12.72/30 | 4 | RUDN_ | Rudnyi | ASSIGNED PA | Jan 16, 2025 | abuse@ via KZ-KAZAKTELECOM-20101223 |
| └ 2.134.12.76/30 | 4 | MOLOD_ | Karabalyk | ASSIGNED PA | Jan 17, 2025 | abuse@ via KZ-KAZAKTELECOM-20101223 |
| └ 2.134.12.80/30 | 4 | RUD_ | unknown | ASSIGNED PA | Feb 17, 2026 | abuse@ via KZ-KAZAKTELECOM-20101223 |
| └ 2.134.12.84/30 | 4 | OTD_ | RC Torgai | ASSIGNED PA | Feb 11, 2025 | abuse@ via KZ-KAZAKTELECOM-20101223 |
| └ 2.134.12.88/30 | 4 | TOO_ | Karabalyk | ASSIGNED PA | Jun 26, 2025 | abuse@ via KZ-KAZAKTELECOM-20101223 |
| └ 2.134.12.92/30 | 4 | KOST_ | Tobyl | ASSIGNED PA | Jan 30, 2025 | abuse@ via KZ-KAZAKTELECOM-20101223 |
| └ 2.134.12.96/30 | 4 | OLZHA_ | Konstantinovka | ASSIGNED PA | Feb 3, 2025 | abuse@ via KZ-KAZAKTELECOM-20101223 |
| └ 2.134.12.100/30 | 4 | OOSH_ | RC Arkalyk | ASSIGNED PA | Feb 11, 2025 | abuse@ via KZ-KAZAKTELECOM-20101223 |
| └ 2.134.12.104/30 | 4 | MIKRK_ | unknown | ASSIGNED PA | Jun 22, 2026 | abuse@ via KZ-KAZAKTELECOM-20101223 |
| └ 2.134.12.108/30 | 4 | OTDEL_ | RC Tobyl | ASSIGNED PA | Feb 17, 2025 | abuse@ via KZ-KAZAKTELECOM-20101223 |
| └ 2.134.12.112/30 | 4 | MIKRK_ | unknown | ASSIGNED PA | Jun 22, 2026 | abuse@ via KZ-KAZAKTELECOM-20101223 |
| └ 2.134.12.116/30 | 4 | AULIEKOL_ | RC Auliekol | ASSIGNED PA | Feb 26, 2025 | abuse@ via KZ-KAZAKTELECOM-20101223 |
| └ 2.134.12.120/30 | 4 | MIKRK_ | unknown | ASSIGNED PA | Jun 22, 2026 | abuse@ via KZ-KAZAKTELECOM-20101223 |
| └ 2.134.12.124/30 | 4 | POLITEH_ | unknown | ASSIGNED PA | Feb 23, 2026 | abuse@ via KZ-KAZAKTELECOM-20101223 |
| └ 2.134.12.128/30 | 4 | MIKRK_ | unknown | ASSIGNED PA | Jun 22, 2026 | abuse@ via KZ-KAZAKTELECOM-20101223 |
| └ 2.134.12.132/30 | 4 | MIKRK_ | unknown | ASSIGNED PA | Jun 22, 2026 | abuse@ via KZ-KAZAKTELECOM-20101223 |
| └ 2.134.12.136/30 | 4 | OTDEL_ | RC Ubaganskoe | ASSIGNED PA | Feb 18, 2025 | abuse@ via KZ-KAZAKTELECOM-20101223 |
| └ 2.134.12.140/30 | 4 | OTDEL_ | RC Ubaganskoe | ASSIGNED PA | Feb 18, 2025 | abuse@ via KZ-KAZAKTELECOM-20101223 |
| └ 2.134.12.144/30 | 4 | MIKRK_ | unknown | ASSIGNED PA | Jun 22, 2026 | abuse@ via KZ-KAZAKTELECOM-20101223 |
| └ 2.134.12.148/30 | 4 | MIKRK_ | unknown | ASSIGNED PA | Jun 22, 2026 | abuse@ via KZ-KAZAKTELECOM-20101223 |
| └ 2.134.12.152/30 | 4 | TOO_ | Fedorovka | ASSIGNED PA | Mar 7, 2025 | abuse@ via KZ-KAZAKTELECOM-20101223 |
| └ 2.134.12.156/30 | 4 | MIKRK_ | unknown | ASSIGNED PA | Jun 22, 2026 | abuse@ via KZ-KAZAKTELECOM-20101223 |
| └ 2.134.12.160/30 | 4 | OTDEL_ | RC Borovskoi | ASSIGNED PA | Mar 13, 2025 | abuse@ via KZ-KAZAKTELECOM-20101223 |
| └ 2.134.12.164/30 | 4 | GU_ | RC Taiynsha | ASSIGNED PA | Mar 28, 2025 | abuse@ via KZ-KAZAKTELECOM-20101223 |
| └ 2.134.12.168/30 | 4 | DET_ | RC Auliekol | ASSIGNED PA | Feb 18, 2025 | abuse@ via KZ-KAZAKTELECOM-20101223 |
| └ 2.134.12.172/30 | 4 | IP_ | unknown | ASSIGNED PA | Feb 18, 2025 | abuse@ via KZ-KAZAKTELECOM-20101223 |
| └ 2.134.12.176/30 | 4 | OTDEL_ | RC Ubaganskoe | ASSIGNED PA | Feb 19, 2025 | abuse@ via KZ-KAZAKTELECOM-20101223 |
| └ 2.134.12.180/30 | 4 | OTDEL_ | RC Ubaganskoe | ASSIGNED PA | Feb 19, 2025 | abuse@ via KZ-KAZAKTELECOM-20101223 |
| └ 2.134.12.184/30 | 4 | TOO_ | RC Ozernoe | ASSIGNED PA | Mar 27, 2025 | abuse@ via KZ-KAZAKTELECOM-20101223 |
| └ 2.134.12.188/30 | 4 | TELERADIO_ | RC Kostanai | ASSIGNED PA | Feb 19, 2025 | abuse@ via KZ-KAZAKTELECOM-20101223 |
| └ 2.134.12.192/30 | 4 | DET_ | RC Auliekol | ASSIGNED PA | Feb 20, 2025 | abuse@ via KZ-KAZAKTELECOM-20101223 |
| └ 2.134.12.196/30 | 4 | DEN_ | unknown | ASSIGNED PA | Mar 26, 2026 | abuse@ via KZ-KAZAKTELECOM-20101223 |
| └ 2.134.12.200/30 | 4 | OTDEL_ | RC Ubaganskoe | ASSIGNED PA | Feb 20, 2025 | abuse@ via KZ-KAZAKTELECOM-20101223 |
| └ 2.134.12.204/30 | 4 | NAO_ | 65 Al-Farabi Ave., Kostanay | ASSIGNED PA | Feb 21, 2025 | abuse@ via KZ-KAZAKTELECOM-20101223 |
| └ 2.134.12.208/30 | 4 | KST_ | RC Kostanai | ASSIGNED PA | Feb 21, 2025 | abuse@ via KZ-KAZAKTELECOM-20101223 |
| └ 2.134.12.212/30 | 4 | OTD_ | unknown | ASSIGNED PA | Aug 21, 2026 | abuse@ via KZ-KAZAKTELECOM-20101223 |
| └ 2.134.12.216/30 | 4 | OTDEL_ | RC Tobyl | ASSIGNED PA | Feb 24, 2025 | abuse@ via KZ-KAZAKTELECOM-20101223 |
| └ 2.134.12.220/30 | 4 | TOO_ | RC Uzunkol | ASSIGNED PA | Mar 18, 2025 | abuse@ via KZ-KAZAKTELECOM-20101223 |
| └ 2.134.12.224/30 | 4 | PRAVITELSTVO_ | Qostanai | ASSIGNED PA | Mar 28, 2025 | abuse@ via KZ-KAZAKTELECOM-20101223 |
| └ 2.134.12.228/30 | 4 | NCERK | Fedorovka | ASSIGNED PA | Feb 28, 2025 | abuse@ via KZ-KAZAKTELECOM-20101223 |
| └ 2.134.12.232/30 | 4 | NCERK | Rudny | ASSIGNED PA | Feb 28, 2025 | abuse@ via KZ-KAZAKTELECOM-20101223 |
| └ 2.134.12.236/30 | 4 | AEROPORT_ | unknown | ASSIGNED PA | Aug 19, 2026 | abuse@ via KZ-KAZAKTELECOM-20101223 |
| └ 2.134.12.240/30 | 4 | TOO_ | Oktiabrskoe | ASSIGNED PA | Apr 8, 2025 | abuse@ via KZ-KAZAKTELECOM-20101223 |
| └ 2.134.12.244/30 | 4 | NCERK | Arkaly | ASSIGNED PA | Feb 28, 2025 | abuse@ via KZ-KAZAKTELECOM-20101223 |
| └ 2.134.12.248/30 | 4 | NCERK | Denisovka | ASSIGNED PA | Feb 28, 2025 | abuse@ via KZ-KAZAKTELECOM-20101223 |
| └ 2.134.12.252/30 | 4 | NCERK | Lisakovsk | ASSIGNED PA | Feb 28, 2025 | abuse@ via KZ-KAZAKTELECOM-20101223 |
| └ 2.134.13.0/30 | 4 | NCERK | Zhelezinsky | ASSIGNED PA | Feb 28, 2025 | abuse@ via KZ-KAZAKTELECOM-20101223 |
| └ 2.134.13.4/30 | 4 | GUROZSOSH | unknown | ASSIGNED PA | Mar 13, 2026 | abuse@ via KZ-KAZAKTELECOM-20101223 |
| └ 2.134.13.8/30 | 4 | GUOTDELOBRAZOVANIYA | Bayanaulskiy Rayon | ASSIGNED PA | Aug 14, 2025 | abuse@ via KZ-KAZAKTELECOM-20101223 |
| └ 2.134.13.16/30 | 4 | KGUKOMSERVIC | PAVLODAR | ASSIGNED PA | Mar 4, 2025 | abuse@ via KZ-KAZAKTELECOM-20101223 |
| └ 2.134.13.24/30 | 4 | ABAISOSH | Maisk | ASSIGNED PA | Mar 28, 2025 | abuse@ via KZ-KAZAKTELECOM-20101223 |
| └ 2.134.13.28/30 | 4 | OBLREBLCENTR | Pavlodar | ASSIGNED PA | Mar 4, 2025 | abuse@ via KZ-KAZAKTELECOM-20101223 |
| └ 2.134.13.40/30 | 4 | SHKOLA1TER | PAVLODAR | ASSIGNED PA | Mar 5, 2025 | abuse@ via KZ-KAZAKTELECOM-20101223 |
| └ 2.134.13.44/30 | 4 | GUSOSH4 | BAYANAUL | ASSIGNED PA | Mar 17, 2025 | abuse@ via KZ-KAZAKTELECOM-20101223 |
| └ 2.134.13.48/30 | 4 | SSHAINAKOL | AKSU | ASSIGNED PA | Jun 20, 2025 | abuse@ via KZ-KAZAKTELECOM-20101223 |
| └ 2.134.13.52/30 | 4 | GUSOSH2 | Pavlodar | ASSIGNED PA | Mar 6, 2025 | abuse@ via KZ-KAZAKTELECOM-20101223 |
| └ 2.134.13.56/30 | 4 | Pravitgrazhdan | unknown | ASSIGNED PA | Jun 2, 2026 | abuse@ via KZ-KAZAKTELECOM-20101223 |
| └ 2.134.13.60/30 | 4 | SOSH14 | Pavlodar | ASSIGNED PA | Mar 6, 2025 | abuse@ via KZ-KAZAKTELECOM-20101223 |
| └ 2.134.13.64/27 | 32 | GUTCIT | unknown | ASSIGNED PA | Mar 3, 2026 | abuse@ via KZ-KAZAKTELECOM-20101223 |
| └ 2.134.13.96/27 | 32 | IP_ | unknown | ASSIGNED PA | Apr 1, 2026 | abuse@ via KZ-KAZAKTELECOM-20101223 |
| └ 2.134.13.128/30 | 4 | MIKRK_ | unknown | ASSIGNED PA | Jun 22, 2026 | abuse@ via KZ-KAZAKTELECOM-20101223 |
| └ 2.134.13.132/30 | 4 | MIKRK_ | unknown | ASSIGNED PA | Jun 22, 2026 | abuse@ via KZ-KAZAKTELECOM-20101223 |
| └ 2.134.13.136/30 | 4 | MIKRK_ | unknown | ASSIGNED PA | Jun 22, 2026 | abuse@ via KZ-KAZAKTELECOM-20101223 |
| └ 2.134.13.140/30 | 4 | MIKRK_ | unknown | ASSIGNED PA | Jun 22, 2026 | abuse@ via KZ-KAZAKTELECOM-20101223 |
| └ 2.134.13.144/30 | 4 | MIKRK_ | unknown | ASSIGNED PA | Jun 22, 2026 | abuse@ via KZ-KAZAKTELECOM-20101223 |
| └ 2.134.13.148/30 | 4 | MIKRK_ | unknown | ASSIGNED PA | Jun 22, 2026 | abuse@ via KZ-KAZAKTELECOM-20101223 |
| └ 2.134.13.152/30 | 4 | MIKRK_ | unknown | ASSIGNED PA | Jun 22, 2026 | abuse@ via KZ-KAZAKTELECOM-20101223 |
| └ 2.134.13.156/30 | 4 | MIKRK_ | unknown | ASSIGNED PA | Jun 22, 2026 | abuse@ via KZ-KAZAKTELECOM-20101223 |
| └ 2.134.13.160/30 | 4 | MIKRK_ | unknown | ASSIGNED PA | Jun 22, 2026 | abuse@ via KZ-KAZAKTELECOM-20101223 |
| └ 2.134.13.164/30 | 4 | MIKRK_ | unknown | ASSIGNED PA | Jun 22, 2026 | abuse@ via KZ-KAZAKTELECOM-20101223 |
| └ 2.134.13.168/30 | 4 | MIKRK_ | unknown | ASSIGNED PA | Jun 22, 2026 | abuse@ via KZ-KAZAKTELECOM-20101223 |
| └ 2.134.13.172/30 | 4 | MIKRK_ | unknown | ASSIGNED PA | Jun 22, 2026 | abuse@ via KZ-KAZAKTELECOM-20101223 |
| └ 2.134.13.176/30 | 4 | MIKRK_ | unknown | ASSIGNED PA | Jun 22, 2026 | abuse@ via KZ-KAZAKTELECOM-20101223 |
| └ 2.134.13.180/30 | 4 | MIKRK_ | unknown | ASSIGNED PA | Jun 22, 2026 | abuse@ via KZ-KAZAKTELECOM-20101223 |
| └ 2.134.13.184/30 | 4 | MIKRK_ | unknown | ASSIGNED PA | Jun 16, 2026 | abuse@ via KZ-KAZAKTELECOM-20101223 |
| └ 2.134.13.188/30 | 4 | MIKRK_ | unknown | ASSIGNED PA | Jun 16, 2026 | abuse@ via KZ-KAZAKTELECOM-20101223 |
| └ 2.134.13.192/30 | 4 | MIKRK_ | unknown | ASSIGNED PA | Jun 16, 2026 | abuse@ via KZ-KAZAKTELECOM-20101223 |
| └ 2.134.13.196/30 | 4 | MIKRK_ | unknown | ASSIGNED PA | Jun 16, 2026 | abuse@ via KZ-KAZAKTELECOM-20101223 |
| └ 2.134.13.200/30 | 4 | MIKRK_ | unknown | ASSIGNED PA | Jun 16, 2026 | abuse@ via KZ-KAZAKTELECOM-20101223 |
| └ 2.134.13.204/30 | 4 | MIKRK_ | unknown | ASSIGNED PA | Jun 16, 2026 | abuse@ via KZ-KAZAKTELECOM-20101223 |
| └ 2.134.13.208/30 | 4 | MIKRK_ | unknown | ASSIGNED PA | Jun 16, 2026 | abuse@ via KZ-KAZAKTELECOM-20101223 |
| └ 2.134.13.212/30 | 4 | MIKRK_ | unknown | ASSIGNED PA | Jun 16, 2026 | abuse@ via KZ-KAZAKTELECOM-20101223 |
| └ 2.134.13.216/30 | 4 | MIKRK_ | unknown | ASSIGNED PA | Jun 22, 2026 | abuse@ via KZ-KAZAKTELECOM-20101223 |
| └ 2.134.13.220/30 | 4 | MIKRK_ | unknown | ASSIGNED PA | Jun 22, 2026 | abuse@ via KZ-KAZAKTELECOM-20101223 |
| └ 2.134.13.224/30 | 4 | MIKRK_ | unknown | ASSIGNED PA | Jun 22, 2026 | abuse@ via KZ-KAZAKTELECOM-20101223 |
| └ 2.134.13.228/30 | 4 | MIKRK_ | unknown | ASSIGNED PA | Jun 22, 2026 | abuse@ via KZ-KAZAKTELECOM-20101223 |
| └ 2.134.13.232/30 | 4 | MIKRK_ | unknown | ASSIGNED PA | Jun 22, 2026 | abuse@ via KZ-KAZAKTELECOM-20101223 |
| └ 2.134.13.236/30 | 4 | MIKRK_ | unknown | ASSIGNED PA | Jun 22, 2026 | abuse@ via KZ-KAZAKTELECOM-20101223 |
| └ 2.134.14.0/30 | 4 | NCERK | Inderbor Inde | ASSIGNED PA | Feb 28, 2025 | abuse@ via KZ-KAZAKTELECOM-20101223 |
| └ 2.134.14.4/30 | 4 | NCERK | Kulsary Zhyly | ASSIGNED PA | Feb 28, 2025 | abuse@ via KZ-KAZAKTELECOM-20101223 |
| └ 2.134.14.8/30 | 4 | NCERK | Makhambet Maha | ASSIGNED PA | Feb 28, 2025 | abuse@ via KZ-KAZAKTELECOM-20101223 |
| └ 2.134.14.12/30 | 4 | NCERK | Makat Makatskiy | ASSIGNED PA | Feb 28, 2025 | abuse@ via KZ-KAZAKTELECOM-20101223 |
| └ 2.134.14.16/30 | 4 | NCERK | Akkistau Issad | ASSIGNED PA | Feb 28, 2025 | abuse@ via KZ-KAZAKTELECOM-20101223 |
| └ 2.134.14.20/30 | 4 | NCERK | Miyaly | ASSIGNED PA | Feb 28, 2025 | abuse@ via KZ-KAZAKTELECOM-20101223 |
| └ 2.134.14.24/30 | 4 | NCERK | Atyrau | ASSIGNED PA | Feb 28, 2025 | abuse@ via KZ-KAZAKTELECOM-20101223 |
| └ 2.134.14.28/30 | 4 | ATYRMUZEY | Atyrau | ASSIGNED PA | Mar 25, 2025 | abuse@ via KZ-KAZAKTELECOM-20101223 |
| └ 2.134.14.32/30 | 4 | SCHOOLISATAI | Atyrau | ASSIGNED PA | Mar 26, 2025 | abuse@ via KZ-KAZAKTELECOM-20101223 |
| └ 2.134.14.36/30 | 4 | SENTRPODERJKSEM | Atyrau | ASSIGNED PA | Apr 22, 2025 | abuse@ via KZ-KAZAKTELECOM-20101223 |
| └ 2.134.14.40/30 | 4 | ODELZANYTSKULS | Atyrau | ASSIGNED PA | Feb 28, 2025 | abuse@ via KZ-KAZAKTELECOM-20101223 |
| └ 2.134.14.44/30 | 4 | UILSKIOKRUG | Atyrau | ASSIGNED PA | Mar 3, 2025 | abuse@ via KZ-KAZAKTELECOM-20101223 |
| └ 2.134.14.48/30 | 4 | ATYRMUZEY | Atyrau | ASSIGNED PA | Mar 25, 2025 | abuse@ via KZ-KAZAKTELECOM-20101223 |
| └ 2.134.14.52/30 | 4 | SCHOOLISATAI | Atyrau | ASSIGNED PA | Mar 26, 2025 | abuse@ via KZ-KAZAKTELECOM-20101223 |
| └ 2.134.14.56/30 | 4 | SCHOOLISATAI | Atyrau | ASSIGNED PA | Mar 26, 2025 | abuse@ via KZ-KAZAKTELECOM-20101223 |
| └ 2.134.14.60/30 | 4 | SELHOZMAKAT | Atyrau | ASSIGNED PA | Mar 28, 2025 | abuse@ via KZ-KAZAKTELECOM-20101223 |
| └ 2.134.14.64/26 | 64 | ASTEL | Atyrau | ASSIGNED PA | Jul 21, 2025 | abuse@ via KZ-KAZAKTELECOM-20101223 |
| └ 2.134.14.128/30 | 4 | ORGDNEVPOLUSTACIONAR | Atyrau | ASSIGNED PA | Feb 18, 2025 | abuse@ via KZ-KAZAKTELECOM-20101223 |
| └ 2.134.14.132/30 | 4 | OTDELTRANSPORTA | Atyrau | ASSIGNED PA | Feb 18, 2025 | abuse@ via KZ-KAZAKTELECOM-20101223 |
| └ 2.134.14.136/30 | 4 | METODOSENTR | Atyrau | ASSIGNED PA | Sep 8, 2025 | abuse@ via KZ-KAZAKTELECOM-20101223 |
| └ 2.134.14.140/30 | 4 | SCHOOLGIM44 | Atyrau | ASSIGNED PA | Feb 26, 2025 | abuse@ via KZ-KAZAKTELECOM-20101223 |
| └ 2.134.14.144/30 | 4 | ORLEU | Atyrau city | ASSIGNED PA | Feb 21, 2025 | abuse@ via KZ-KAZAKTELECOM-20101223 |
| └ 2.134.14.148/30 | 4 | YASLISAD18BALDYRGAN | Atyrau | ASSIGNED PA | Feb 26, 2025 | abuse@ via KZ-KAZAKTELECOM-20101223 |
| └ 2.134.14.152/30 | 4 | DETSKAIADEREVNYA | unknown | ASSIGNED PA | Feb 17, 2026 | abuse@ via KZ-KAZAKTELECOM-20101223 |
| └ 2.134.14.156/30 | 4 | VETSTANSYAKYZYLKOG | Atyrau | ASSIGNED PA | Feb 26, 2025 | abuse@ via KZ-KAZAKTELECOM-20101223 |
| └ 2.134.14.160/30 | 4 | IRGLTD | unknown | ASSIGNED PA | Apr 17, 2026 | abuse@ via KZ-KAZAKTELECOM-20101223 |
| └ 2.134.14.164/30 | 4 | KURMANGAZYBOLNICA | unknown | ASSIGNED PA | May 13, 2026 | abuse@ via KZ-KAZAKTELECOM-20101223 |
| └ 2.134.14.168/30 | 4 | VETSTANSYAKYZYLKOG | Atyrau | ASSIGNED PA | Feb 26, 2025 | abuse@ via KZ-KAZAKTELECOM-20101223 |
| └ 2.134.14.172/30 | 4 | VETSTANSYAKYZYLKOG | Atyrau | ASSIGNED PA | Feb 26, 2025 | abuse@ via KZ-KAZAKTELECOM-20101223 |
| └ 2.134.14.176/30 | 4 | VETSTANSYAKYZYLKOG | Atyrau | ASSIGNED PA | Feb 26, 2025 | abuse@ via KZ-KAZAKTELECOM-20101223 |
| └ 2.134.14.180/30 | 4 | VETSTANSYAKYZYLKOG | unknown | ASSIGNED PA | Apr 17, 2026 | abuse@ via KZ-KAZAKTELECOM-20101223 |
| └ 2.134.14.184/30 | 4 | VETSTANSYAKYZYLKOG | Atyrau | ASSIGNED PA | Feb 26, 2025 | abuse@ via KZ-KAZAKTELECOM-20101223 |
| └ 2.134.14.188/30 | 4 | VETSTANSYAKYZYLKOG | Atyrau | ASSIGNED PA | Feb 26, 2025 | abuse@ via KZ-KAZAKTELECOM-20101223 |
| └ 2.134.14.192/30 | 4 | TOROSIP | unknown | ASSIGNED PA | Sep 29, 2026 | abuse@ via KZ-KAZAKTELECOM-20101223 |
| └ 2.134.14.196/30 | 4 | AKIMATZHANAKARATON | Atyrau | ASSIGNED PA | Nov 13, 2024 | abuse@ via KZ-KAZAKTELECOM-20101223 |
| └ 2.134.14.200/30 | 4 | TEEZLOGISTICS | Kulsary | ASSIGNED PA | Nov 18, 2024 | abuse@ via KZ-KAZAKTELECOM-20101223 |
| └ 2.134.14.204/30 | 4 | AKZHAKIMG | Atyrau | ASSIGNED PA | Oct 2, 2025 | abuse@ via KZ-KAZAKTELECOM-20101223 |
| └ 2.134.14.208/28 | 16 | NISGUW | Atyrau | ASSIGNED PA | Jul 19, 2024 | abuse@ via KZ-KAZAKTELECOM-20101223 |
| └ 2.134.14.224/30 | 4 | ATYROBLTERRINSPEKCIYA | Atyrau | ASSIGNED PA | Jun 27, 2024 | abuse@ via KZ-KAZAKTELECOM-20101223 |
| └ 2.134.14.228/30 | 4 | ATYROBLTERRINSPEKCIYA | Atyrau | ASSIGNED PA | Jun 10, 2024 | abuse@ via KZ-KAZAKTELECOM-20101223 |
| └ 2.134.14.232/30 | 4 | KOMITETRYBHOZ | Atyrau | ASSIGNED PA | Jun 11, 2024 | abuse@ via KZ-KAZAKTELECOM-20101223 |
| └ 2.134.14.236/30 | 4 | SPORTSCHOOLGEM | Atyrau | ASSIGNED PA | Jun 11, 2024 | abuse@ via KZ-KAZAKTELECOM-20101223 |
| └ 2.134.14.240/30 | 4 | SANEPIDKONTR | Atyrau | ASSIGNED PA | Jun 20, 2024 | abuse@ via KZ-KAZAKTELECOM-20101223 |
| └ 2.134.14.244/30 | 4 | UPRAVLENIEPREDRINIMATELSTVA | Atyrau | ASSIGNED PA | Jun 14, 2024 | abuse@ via KZ-KAZAKTELECOM-20101223 |
| └ 2.134.14.248/30 | 4 | AFLPRAVGRARAZHDAN | Atyrau | ASSIGNED PA | Jun 14, 2024 | abuse@ via KZ-KAZAKTELECOM-20101223 |
| └ 2.134.14.252/30 | 4 | MAHAMBETRAIONBOLNICA | Atyrau | ASSIGNED PA | Jun 18, 2024 | abuse@ via KZ-KAZAKTELECOM-20101223 |
| └ 2.134.15.0/25 | 128 | IP_ | LLP "Conco" (ORG-LA2117-RIPE) | ASSIGNED PA | Sep 23, 2026 | abuse@ |
| └ 2.134.15.128/29 | 8 | MTNMC_ | Pavlodar | ASSIGNED PA | Aug 28, 2024 | abuse@ via KZ-KAZAKTELECOM-20101223 |
| └ 2.134.15.136/29 | 8 | MTNMC_ | Pavlodar | ASSIGNED PA | Aug 28, 2024 | abuse@ via KZ-KAZAKTELECOM-20101223 |
| └ 2.134.15.144/29 | 8 | MTNMC_ | Pavlodar | ASSIGNED PA | Aug 28, 2024 | abuse@ via KZ-KAZAKTELECOM-20101223 |
| └ 2.134.15.152/29 | 8 | MTNMC_ | Pavlodar | ASSIGNED PA | Aug 28, 2024 | abuse@ via KZ-KAZAKTELECOM-20101223 |
| └ 2.134.15.160/29 | 8 | MTNMC_ | Pavlodar | ASSIGNED PA | Aug 28, 2024 | abuse@ via KZ-KAZAKTELECOM-20101223 |
| └ 2.134.15.168/29 | 8 | MTNMC_ | Pavlodar | ASSIGNED PA | Aug 28, 2024 | abuse@ via KZ-KAZAKTELECOM-20101223 |
| └ 2.134.15.176/28 | 16 | IP_ | LLC Center for the Development of the Digital Economy | ASSIGNED PA | Oct 1, 2024 | abuse@ via KZ-KAZAKTELECOM-20101223 |
| └ 2.134.15.192/26 | 64 | IP_ | LLC Smartapps | ASSIGNED PA | Dec 13, 2024 | abuse@ via KZ-KAZAKTELECOM-20101223 |
| └ 2.134.16.0/20 | 4,096 | GPON_ | JSC Kazakhtelecom | ASSIGNED PA | Feb 2, 2018 | abuse@ via KZ-KAZAKTELECOM-20101223 |
| └ 2.134.32.0/22 | 1,024 | GPON_ | JSC Kazakhtelecom | ASSIGNED PA | Jan 5, 2017 | abuse@ via KZ-KAZAKTELECOM-20101223 |
| └ 2.134.36.0/22 | 1,024 | GPON_ | JSC Kazakhtelecom | ASSIGNED PA | Jan 5, 2017 | abuse@ via KZ-KAZAKTELECOM-20101223 |
| └ 2.134.41.0/24 | 256 | IP_ | unknown | ASSIGNED PA | Jun 2, 2026 | abuse@ via KZ-KAZAKTELECOM-20101223 |
| └ 2.134.42.0/24 | 256 | ALMATYTELECOM | JSC Kazakhtelecom | ASSIGNED PA | Jan 5, 2017 | abuse@ via KZ-KAZAKTELECOM-20101223 |
| └ 2.134.43.0/24 | 256 | MTNMCKAZAKTELECOMJSC | JSC Kazakhtelecom | ASSIGNED PA | Jan 5, 2017 | abuse@ via KZ-KAZAKTELECOM-20101223 |
| └ 2.134.44.0/22 | 1,024 | GPON_ | JSC Kazakhtelecom | ASSIGNED PA | Aug 2, 2018 | abuse@ via KZ-KAZAKTELECOM-20101223 |
| └ 2.134.48.0/21 | 2,048 | GPON_ | JSC Kazakhtelecom, Taraz Affiliate | ASSIGNED PA | May 15, 2011 | abuse@ via KZ-KAZAKTELECOM-20101223 |
| └ 2.134.56.0/22 | 1,024 | GPON_ | JSC Kazakhtelecom | ASSIGNED PA | Aug 2, 2018 | abuse@ via KZ-KAZAKTELECOM-20101223 |
| └ 2.134.60.0/22 | 1,024 | MTNMC_ | Almaty | ASSIGNED PA | May 15, 2026 | 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 | 15,440 | 94% | 18 | |
| Business | 944 | 5.8% | 155 |
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
- Oct 2016 · 10 yr
- Origin networks
- 1
RPKI
Route origin authorizations
| ROA prefix | ASN | Max len | Anchor | Verdict |
|---|---|---|---|---|
| 2.134.0.0/18 | AS9198 | /24 | 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.134.0.0/21 | AS9198 | RIPE | Kazakhtelecom Data Network Administration | KNIC-MNT | Feb 8, 2012 |
| 2.134.12.0/22 | AS9198 | RIPE | Kazakhtelecom Data Network Administration | KNIC-MNT | Jul 9, 2013 |
| 2.134.32.0/20 | AS9198 | RIPE | Kazakhtelecom Data Network Administration | KNIC-MNT | Feb 8, 2012 |
| 2.134.32.0/21 | AS9198 | RIPE | Kazakhtelecom Data Network Administration | KNIC-MNT | Mar 19, 2015 |
| 2.134.48.0/20 | AS9198 | RIPE | Kazakhtelecom Data Network Administration | KNIC-MNT | Feb 29, 2012 |
| 2.134.56.0/21 | AS9198 | RIPE | Kazakhtelecom Data Network Administration | KNIC-MNT | Mar 19, 2015 |
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