Data as of Nov 13, 2026
92.46.176.0/20
605 residential-proxy exits · 30 daysJSC Kazakhtelecom
Residential-proxy exits
Proxy exits
605
15% of its addresses · 30 days
Always-on exits
5
0.83% of its exits
Spread
16 of 16
/24s with at least one exit
Providers
117
selling exits here
Oct 14, 2026 – Nov 12, 2026
Exits seen per day
56K observations
- Residential
- Business
/24s with the most always-on exits
| /24 | Always-on exits | Proxy exits | |
|---|---|---|---|
| 92.46.182.0/24 | 1 | 82 | |
| 92.46.183.0/24 | 1 | 73 | |
| 92.46.181.0/24 | 1 | 63 | |
| 92.46.187.0/24 | 1 | 9 | |
| 92.46.184.0/24 | 1 | 9 | |
| 92.46.176.0/24 | 0 | 77 | |
| 92.46.180.0/24 | 0 | 69 | |
| 92.46.178.0/24 | 0 | 67 | |
| 92.46.177.0/24 | 0 | 66 | |
| 92.46.179.0/24 | 0 | 64 | |
| 92.46.191.0/24 | 0 | 7 | |
| 92.46.188.0/24 | 0 | 6 | |
| 92.46.185.0/24 | 0 | 4 | |
| 92.46.186.0/24 | 0 | 4 | |
| 92.46.189.0/24 | 0 | 4 | |
| 92.46.190.0/24 | 0 | 1 |
Proxy providers listing exits
- 2Captcha
- 711Proxy
- 911Proxy
- 9Proxy
- APROXY
- ASHBURNPROXIES
- Ake.net
- AnyIP
- B2Proxy
- BartProxies
- BestProxy
- BirdProxies
- BlurPath
- BottingTools
- BuyingProxy
- ByteProxies
- Byteful
- CROXY
- CatProxies
- CliProxy
- DataImpulse
- Datarama
- Decodo
- EVOPROXY
- EZProxies
- EnigmaProxy
- Evomi
- FastProxy
- FlashProxy
- GSocks
- Geonix
- Geonode
- GhostConnect
- GloryCloud
- GoProxies
- GonzoProxy
- HPROXY
- HideProxy
- IPFly
- IPMUSK
- IPOasis
- IPPeak
- IPROCKET_BASIC
- IPROCKET_PREMIUM
- IPRoyal
- Infatica
- InfiniteProxies
- KindProxy
- Kookey
- LUMIPROXY
- LemonBright
- LemonLabs
- LemonPrime
- LightningProxies
- LudaxProxy
- MangoProxy
- Maskify
- MoMoProxy
- NSocks
- NextProxy
- NiuProxy
- NodeProxy
- NovProxy
- NovaProxy
- Novada
- Oxylabs
- PROXYON
- PROXYSALE
- PROXYSCRAPE
- PROXYWING_BASIC
- PROXY_CC
- PrivateByte
- PrivateProxy
- ProxiesVision
- Proxio
- Proxiware
- Proxmint
- Proxy-Cheap
- Proxy-Seller
- Proxy302
- Proxy4U
- ProxyEmpire
- ProxyGeo
- ProxyHat
- ProxyRack
- ProxyWing
- Proxying
- Proxyma
- PuraRoute
- Q2IP
- QUANTICDATA
- RH7Proxy
- RainProxy
- RapidProxy
- ResiProxies
- RoamProxy
- RolaProxy
- SPYDERPROXY_BASIC
- SPYDERPROXY_PREMIUM
- Shifter
- Smartproxy
- 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 |
|---|---|---|---|---|---|
| 92.46.0.0/15 since Apr 2019 | AS50482 | Residential | 25,041 242 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 |
|---|---|---|---|---|---|---|
| 92.46.0.0/15 | 131,072 | KZ-KAZAKTELECOM-20071220 | JSC Kazakhtelecom (ORG-KDNA1-RIPE) · KZ | ALLOCATED PA | Dec 20, 2007 | abuse@ |
| └ 92.46.188.144/30 | 4 | MIKRK_ | Pavlodar | ASSIGNED PA | Mar 18, 2019 | abuse@ via KZ-KAZAKTELECOM-20071220 |
| └ 92.46.188.152/30 | 4 | DIS | SC Kazakhtelecom, Information Technology Division | ASSIGNED PA | Jun 10, 2024 | abuse@ via KZ-KAZAKTELECOM-20071220 |
| └ 92.46.188.160/30 | 4 | MIKRK_ | Pavlodar | ASSIGNED PA | Sep 9, 2019 | abuse@ via KZ-KAZAKTELECOM-20071220 |
| └ 92.46.188.164/30 | 4 | MIKRK_ | Pavlodar | ASSIGNED PA | Sep 9, 2019 | abuse@ via KZ-KAZAKTELECOM-20071220 |
| └ 92.46.188.168/30 | 4 | MIKRK_ | Pavlodar | ASSIGNED PA | Sep 9, 2019 | abuse@ via KZ-KAZAKTELECOM-20071220 |
| └ 92.46.188.172/30 | 4 | MIKRK_ | Pavlodar | ASSIGNED PA | Sep 9, 2019 | abuse@ via KZ-KAZAKTELECOM-20071220 |
| └ 92.46.188.176/30 | 4 | MIKRK_ | Pavlodar | ASSIGNED PA | Sep 9, 2019 | abuse@ via KZ-KAZAKTELECOM-20071220 |
| └ 92.46.188.180/30 | 4 | MIKRK_ | Pavlodar | ASSIGNED PA | Sep 9, 2019 | abuse@ via KZ-KAZAKTELECOM-20071220 |
| └ 92.46.188.184/30 | 4 | MIKRK_ | Pavlodar | ASSIGNED PA | Sep 9, 2019 | abuse@ via KZ-KAZAKTELECOM-20071220 |
| └ 92.46.188.188/30 | 4 | MIKRK_ | Pavlodar | ASSIGNED PA | Sep 9, 2019 | abuse@ via KZ-KAZAKTELECOM-20071220 |
| └ 92.46.188.192/30 | 4 | MIKRK_ | Pavlodar | ASSIGNED PA | Sep 9, 2019 | abuse@ via KZ-KAZAKTELECOM-20071220 |
| └ 92.46.188.196/30 | 4 | MIKRK_ | Pavlodar | ASSIGNED PA | Sep 9, 2019 | abuse@ via KZ-KAZAKTELECOM-20071220 |
| └ 92.46.188.200/30 | 4 | MIKRK_ | Pavlodar | ASSIGNED PA | Sep 9, 2019 | abuse@ via KZ-KAZAKTELECOM-20071220 |
| └ 92.46.188.204/30 | 4 | MIKRK_ | Pavlodar | ASSIGNED PA | Sep 9, 2019 | abuse@ via KZ-KAZAKTELECOM-20071220 |
| └ 92.46.188.208/30 | 4 | MIKRK_ | Pavlodar | ASSIGNED PA | Sep 9, 2019 | abuse@ via KZ-KAZAKTELECOM-20071220 |
| └ 92.46.188.212/30 | 4 | MIKRK_ | Pavlodar | ASSIGNED PA | Sep 9, 2019 | abuse@ via KZ-KAZAKTELECOM-20071220 |
| └ 92.46.188.216/30 | 4 | MIKRK_ | Pavlodar | ASSIGNED PA | Sep 9, 2019 | abuse@ via KZ-KAZAKTELECOM-20071220 |
| └ 92.46.188.220/30 | 4 | MIKRK_ | Pavlodar | ASSIGNED PA | Sep 9, 2019 | abuse@ via KZ-KAZAKTELECOM-20071220 |
| └ 92.46.188.224/30 | 4 | MIKRK_ | Pavlodar | ASSIGNED PA | Sep 9, 2019 | abuse@ via KZ-KAZAKTELECOM-20071220 |
| └ 92.46.188.228/30 | 4 | MIKRK_ | Pavlodar | ASSIGNED PA | Oct 23, 2019 | abuse@ via KZ-KAZAKTELECOM-20071220 |
| └ 92.46.188.232/30 | 4 | MIKRK_ | Pavlodar | ASSIGNED PA | Oct 23, 2019 | abuse@ via KZ-KAZAKTELECOM-20071220 |
| └ 92.46.188.236/30 | 4 | MIKRK_ | Pavlodar | ASSIGNED PA | Oct 23, 2019 | abuse@ via KZ-KAZAKTELECOM-20071220 |
| └ 92.46.188.240/28 | 16 | IP_ | SC Kazakhtelecom, Direction of Information Systems | ASSIGNED PA | May 23, 2019 | abuse@ via KZ-KAZAKTELECOM-20071220 |
| └ 92.46.189.0/27 | 32 | MTNMC_ | Pavlodar | ASSIGNED PA | Jul 4, 2019 | abuse@ via KZ-KAZAKTELECOM-20071220 |
| └ 92.46.189.32/30 | 4 | MIKRK_ | Pavlodar | ASSIGNED PA | Sep 13, 2019 | abuse@ via KZ-KAZAKTELECOM-20071220 |
| └ 92.46.189.36/30 | 4 | MIKRK_ | Pavlodar | ASSIGNED PA | Sep 13, 2019 | abuse@ via KZ-KAZAKTELECOM-20071220 |
| └ 92.46.189.40/30 | 4 | MIKRK_ | Pavlodar | ASSIGNED PA | Sep 13, 2019 | abuse@ via KZ-KAZAKTELECOM-20071220 |
| └ 92.46.189.44/30 | 4 | MIKRK_ | Pavlodar | ASSIGNED PA | Sep 13, 2019 | abuse@ via KZ-KAZAKTELECOM-20071220 |
| └ 92.46.189.48/30 | 4 | MIKRK_ | Pavlodar | ASSIGNED PA | Sep 13, 2019 | abuse@ via KZ-KAZAKTELECOM-20071220 |
| └ 92.46.189.52/30 | 4 | MIKRK_ | Pavlodar | ASSIGNED PA | Sep 13, 2019 | abuse@ via KZ-KAZAKTELECOM-20071220 |
| └ 92.46.189.56/30 | 4 | MIKRK_ | Pavlodar | ASSIGNED PA | Sep 13, 2019 | abuse@ via KZ-KAZAKTELECOM-20071220 |
| └ 92.46.189.60/30 | 4 | MIKRK_ | Pavlodar | ASSIGNED PA | Sep 13, 2019 | abuse@ via KZ-KAZAKTELECOM-20071220 |
| └ 92.46.189.64/30 | 4 | MIKRK_ | Pavlodar | ASSIGNED PA | Sep 13, 2019 | abuse@ via KZ-KAZAKTELECOM-20071220 |
| └ 92.46.189.68/30 | 4 | MIKRK_ | Pavlodar | ASSIGNED PA | Sep 13, 2019 | abuse@ via KZ-KAZAKTELECOM-20071220 |
| └ 92.46.189.72/30 | 4 | MIKRK_ | Pavlodar | ASSIGNED PA | Sep 13, 2019 | abuse@ via KZ-KAZAKTELECOM-20071220 |
| └ 92.46.189.76/30 | 4 | MIKRK_ | Pavlodar | ASSIGNED PA | Sep 13, 2019 | abuse@ via KZ-KAZAKTELECOM-20071220 |
| └ 92.46.189.80/30 | 4 | MIKRK_ | Pavlodar | ASSIGNED PA | Sep 13, 2019 | abuse@ via KZ-KAZAKTELECOM-20071220 |
| └ 92.46.189.84/30 | 4 | MIKRK_ | Pavlodar | ASSIGNED PA | Sep 13, 2019 | abuse@ via KZ-KAZAKTELECOM-20071220 |
| └ 92.46.189.92/30 | 4 | MIKRK_ | Pavlodar | ASSIGNED PA | Sep 13, 2019 | abuse@ via KZ-KAZAKTELECOM-20071220 |
| └ 92.46.189.96/30 | 4 | MIKRK_ | Pavlodar | ASSIGNED PA | Sep 13, 2019 | abuse@ via KZ-KAZAKTELECOM-20071220 |
| └ 92.46.189.104/30 | 4 | MIKRK_ | Pavlodar | ASSIGNED PA | Sep 13, 2019 | abuse@ via KZ-KAZAKTELECOM-20071220 |
| └ 92.46.189.108/30 | 4 | MIKRK_ | Pavlodar | ASSIGNED PA | Sep 13, 2019 | abuse@ via KZ-KAZAKTELECOM-20071220 |
| └ 92.46.189.112/30 | 4 | MIKRK_ | Pavlodar | ASSIGNED PA | Sep 13, 2019 | abuse@ via KZ-KAZAKTELECOM-20071220 |
| └ 92.46.189.116/30 | 4 | MIKRK_ | Pavlodar | ASSIGNED PA | Sep 13, 2019 | abuse@ via KZ-KAZAKTELECOM-20071220 |
| └ 92.46.189.120/30 | 4 | MIKRK_ | Pavlodar | ASSIGNED PA | Sep 13, 2019 | abuse@ via KZ-KAZAKTELECOM-20071220 |
| └ 92.46.189.124/30 | 4 | MIKRK_ | Pavlodar | ASSIGNED PA | Sep 13, 2019 | abuse@ via KZ-KAZAKTELECOM-20071220 |
| └ 92.46.189.128/30 | 4 | MIKRK_ | Pavlodar | ASSIGNED PA | Sep 13, 2019 | abuse@ via KZ-KAZAKTELECOM-20071220 |
| └ 92.46.189.132/30 | 4 | MIKRK_ | Pavlodar | ASSIGNED PA | Sep 13, 2019 | abuse@ via KZ-KAZAKTELECOM-20071220 |
| └ 92.46.189.136/30 | 4 | MIKRK_ | Pavlodar | ASSIGNED PA | Sep 13, 2019 | abuse@ via KZ-KAZAKTELECOM-20071220 |
| └ 92.46.189.140/30 | 4 | MIKRK_ | Pavlodar | ASSIGNED PA | Sep 13, 2019 | abuse@ via KZ-KAZAKTELECOM-20071220 |
| └ 92.46.189.144/30 | 4 | MIKRK_ | Pavlodar | ASSIGNED PA | Sep 13, 2019 | abuse@ via KZ-KAZAKTELECOM-20071220 |
| └ 92.46.189.148/30 | 4 | MIKRK_ | Pavlodar | ASSIGNED PA | Sep 13, 2019 | abuse@ via KZ-KAZAKTELECOM-20071220 |
| └ 92.46.189.152/30 | 4 | MIKRK_ | Pavlodar | ASSIGNED PA | Sep 13, 2019 | abuse@ via KZ-KAZAKTELECOM-20071220 |
| └ 92.46.189.156/30 | 4 | MIKRK_ | Pavlodar | ASSIGNED PA | Sep 13, 2019 | abuse@ via KZ-KAZAKTELECOM-20071220 |
| └ 92.46.189.160/30 | 4 | MIKRK_ | Pavlodar | ASSIGNED PA | Sep 13, 2019 | abuse@ via KZ-KAZAKTELECOM-20071220 |
| └ 92.46.189.164/30 | 4 | MIKRK_ | Pavlodar | ASSIGNED PA | Oct 14, 2019 | abuse@ via KZ-KAZAKTELECOM-20071220 |
| └ 92.46.189.168/30 | 4 | MIKRK_ | Pavlodar | ASSIGNED PA | Oct 14, 2019 | abuse@ via KZ-KAZAKTELECOM-20071220 |
| └ 92.46.189.172/30 | 4 | MIKRK_ | Pavlodar | ASSIGNED PA | Oct 14, 2019 | abuse@ via KZ-KAZAKTELECOM-20071220 |
| └ 92.46.189.176/30 | 4 | MIKRK_ | Pavlodar | ASSIGNED PA | Oct 14, 2019 | abuse@ via KZ-KAZAKTELECOM-20071220 |
| └ 92.46.189.180/30 | 4 | MIKRK_ | Pavlodar | ASSIGNED PA | Oct 14, 2019 | abuse@ via KZ-KAZAKTELECOM-20071220 |
| └ 92.46.189.184/30 | 4 | MIKRK_ | Pavlodar | ASSIGNED PA | Oct 14, 2019 | abuse@ via KZ-KAZAKTELECOM-20071220 |
| └ 92.46.189.188/30 | 4 | MIKRK_ | Pavlodar | ASSIGNED PA | Oct 14, 2019 | abuse@ via KZ-KAZAKTELECOM-20071220 |
| └ 92.46.189.192/30 | 4 | MIKRK_ | Pavlodar | ASSIGNED PA | Oct 22, 2019 | abuse@ via KZ-KAZAKTELECOM-20071220 |
| └ 92.46.189.196/30 | 4 | MIKRK_ | Pavlodar | ASSIGNED PA | Oct 22, 2019 | abuse@ via KZ-KAZAKTELECOM-20071220 |
| └ 92.46.189.200/30 | 4 | MIKRK_ | Pavlodar | ASSIGNED PA | Oct 22, 2019 | abuse@ via KZ-KAZAKTELECOM-20071220 |
| └ 92.46.189.204/30 | 4 | MIKRK_ | Pavlodar | ASSIGNED PA | Oct 22, 2019 | abuse@ via KZ-KAZAKTELECOM-20071220 |
| └ 92.46.189.208/30 | 4 | MIKRK_ | Pavlodar | ASSIGNED PA | Oct 22, 2019 | abuse@ via KZ-KAZAKTELECOM-20071220 |
| └ 92.46.189.212/30 | 4 | MIKRK_ | Pavlodar | ASSIGNED PA | Oct 22, 2019 | abuse@ via KZ-KAZAKTELECOM-20071220 |
| └ 92.46.189.216/30 | 4 | MIKRK_ | Pavlodar | ASSIGNED PA | Oct 22, 2019 | abuse@ via KZ-KAZAKTELECOM-20071220 |
| └ 92.46.189.220/30 | 4 | MIKRK_ | Pavlodar | ASSIGNED PA | Oct 22, 2019 | abuse@ via KZ-KAZAKTELECOM-20071220 |
| └ 92.46.189.224/27 | 32 | IP_ | LLC ?kazintersoft? | ASSIGNED PA | Sep 19, 2019 | abuse@ via KZ-KAZAKTELECOM-20071220 |
| └ 92.46.190.0/24 | 256 | IP_ | Kalken Utepov | ASSIGNED PA | Oct 15, 2018 | abuse@ via KZ-KAZAKTELECOM-20071220 |
| └ 92.46.191.0/30 | 4 | GUOTDELPREDPRINIMATELSTVA | EKIBASTUZ | ASSIGNED PA | Jun 12, 2020 | abuse@ via KZ-KAZAKTELECOM-20071220 |
| └ 92.46.191.4/30 | 4 | TOOPROMRESURSKZ | PAVLODAR | ASSIGNED PA | Dec 13, 2017 | abuse@ via KZ-KAZAKTELECOM-20071220 |
| └ 92.46.191.16/30 | 4 | GUSOSH32PAVL | Pavlodar | ASSIGNED PA | Feb 26, 2025 | abuse@ via KZ-KAZAKTELECOM-20071220 |
| └ 92.46.191.20/30 | 4 | TOOINTASTROIGROUP | unknown | ASSIGNED PA | Apr 6, 2026 | abuse@ via KZ-KAZAKTELECOM-20071220 |
| └ 92.46.191.24/30 | 4 | TOOVENTUMPRO | EKIBASTUZ | ASSIGNED PA | Aug 1, 2024 | abuse@ via KZ-KAZAKTELECOM-20071220 |
| └ 92.46.191.28/30 | 4 | TOOTEPSETI | Pavlodar | ASSIGNED PA | Apr 8, 2025 | abuse@ via KZ-KAZAKTELECOM-20071220 |
| └ 92.46.191.32/30 | 4 | GUPAVLSOSH41 | Pavlodar | ASSIGNED PA | Apr 3, 2023 | abuse@ via KZ-KAZAKTELECOM-20071220 |
| └ 92.46.191.36/30 | 4 | TOOPROMRESURSKZ | PAVLODAR | ASSIGNED PA | Dec 13, 2017 | abuse@ via KZ-KAZAKTELECOM-20071220 |
| └ 92.46.191.40/30 | 4 | GUOTDELOBRAZOVANIYA | Bayanaulskiy Rayon | ASSIGNED PA | Oct 3, 2025 | abuse@ via KZ-KAZAKTELECOM-20071220 |
| └ 92.46.191.44/30 | 4 | GUUPRINFOBSHCHESTRAZV | Pavlodar | ASSIGNED PA | Jan 6, 2026 | abuse@ via KZ-KAZAKTELECOM-20071220 |
| └ 92.46.191.48/30 | 4 | DigitALLRS | Pyatiryzhsk | ASSIGNED PA | Sep 29, 2023 | abuse@ via KZ-KAZAKTELECOM-20071220 |
| └ 92.46.191.52/30 | 4 | GUOtdekonomifin | unknown | ASSIGNED PA | Jun 23, 2026 | abuse@ via KZ-KAZAKTELECOM-20071220 |
| └ 92.46.191.56/30 | 4 | IPZHANABAEV | PAVLODAR | ASSIGNED PA | Dec 21, 2018 | abuse@ via KZ-KAZAKTELECOM-20071220 |
| └ 92.46.191.60/30 | 4 | NCERK | Pavlodar | ASSIGNED PA | Feb 25, 2025 | abuse@ via KZ-KAZAKTELECOM-20071220 |
| └ 92.46.191.68/30 | 4 | GUOTDELECONOMBAJANAUL | unknown | ASSIGNED PA | Jun 10, 2026 | abuse@ via KZ-KAZAKTELECOM-20071220 |
| └ 92.46.191.72/30 | 4 | KGUGOSARHIV | unknown | ASSIGNED PA | Apr 8, 2026 | abuse@ via KZ-KAZAKTELECOM-20071220 |
| └ 92.46.191.76/30 | 4 | DIS | unknown | ASSIGNED PA | Jun 29, 2026 | abuse@ via KZ-KAZAKTELECOM-20071220 |
| └ 92.46.191.80/30 | 4 | NCERK | Pavlodar region | ASSIGNED PA | Feb 26, 2025 | abuse@ via KZ-KAZAKTELECOM-20071220 |
| └ 92.46.191.84/30 | 4 | NCERK | Pavlodar region | ASSIGNED PA | Feb 26, 2025 | abuse@ via KZ-KAZAKTELECOM-20071220 |
| └ 92.46.191.88/30 | 4 | GENPROSAST | Pavlodar | ASSIGNED PA | Jan 15, 2020 | abuse@ via KZ-KAZAKTELECOM-20071220 |
| └ 92.46.191.92/30 | 4 | FILIALNAOPRAVITDLYAGRAZGDAN | Pavlodar | ASSIGNED PA | Jan 5, 2025 | abuse@ via KZ-KAZAKTELECOM-20071220 |
| └ 92.46.191.96/29 | 8 | PUAAESPVL | PUAAESPVL | ASSIGNED PA | Apr 4, 2012 | abuse@ via KZ-KAZAKTELECOM-20071220 |
| └ 92.46.191.104/30 | 4 | DigitALLRS | PAVLODAR | ASSIGNED PA | Mar 15, 2021 | abuse@ via KZ-KAZAKTELECOM-20071220 |
| └ 92.46.191.108/30 | 4 | FILIALNAOPRAVITDLYAGRAZGDAN | Pavlodar | ASSIGNED PA | Jan 5, 2025 | abuse@ via KZ-KAZAKTELECOM-20071220 |
| └ 92.46.191.112/30 | 4 | GUOtdekonomifin | unknown | ASSIGNED PA | Jun 23, 2026 | abuse@ via KZ-KAZAKTELECOM-20071220 |
| └ 92.46.191.116/30 | 4 | KGKPRADUGA | unknown | ASSIGNED PA | Aug 5, 2026 | abuse@ via KZ-KAZAKTELECOM-20071220 |
| └ 92.46.191.132/30 | 4 | MIKRK_ | Pavlodar | ASSIGNED PA | Oct 22, 2019 | abuse@ via KZ-KAZAKTELECOM-20071220 |
| └ 92.46.191.140/30 | 4 | TOOERGSERVICE | PAVLODAR | ASSIGNED PA | Sep 15, 2021 | abuse@ via KZ-KAZAKTELECOM-20071220 |
| └ 92.46.191.144/30 | 4 | MIKRK_ | Pavlodar | ASSIGNED PA | Oct 23, 2019 | abuse@ via KZ-KAZAKTELECOM-20071220 |
| └ 92.46.191.148/30 | 4 | BANKKASSANOVA | unknown | ASSIGNED PA | May 26, 2026 | abuse@ via KZ-KAZAKTELECOM-20071220 |
| └ 92.46.191.152/30 | 4 | KOMIRS | In Kommesk-Omir LLP | ASSIGNED PA | Aug 1, 2008 | abuse@ via KZ-KAZAKTELECOM-20071220 |
| └ 92.46.191.156/30 | 4 | AO_ | AO NSK | ASSIGNED PA | Jul 22, 2013 | abuse@ via KZ-KAZAKTELECOM-20071220 |
| └ 92.46.191.168/30 | 4 | GUAPAKBAYZSO | unknown | ASSIGNED PA | May 20, 2026 | abuse@ via KZ-KAZAKTELECOM-20071220 |
| └ 92.46.191.172/30 | 4 | GYORLSHERBRAIONA | Pavlodar | ASSIGNED PA | Jun 10, 2025 | abuse@ via KZ-KAZAKTELECOM-20071220 |
| └ 92.46.191.176/29 | 8 | IP_ | VDC | ASSIGNED PA | Sep 13, 2023 | abuse@ via KZ-KAZAKTELECOM-20071220 |
| └ 92.46.191.196/30 | 4 | ABDICOMPANY | JSC ABDI COMPANY in Pavlodar | ASSIGNED PA | Jan 16, 2009 | abuse@ via KZ-KAZAKTELECOM-20071220 |
| └ 92.46.191.204/30 | 4 | KGUSHKOLAIMSHOKIN | Pavlodar | ASSIGNED PA | Feb 25, 2025 | abuse@ via KZ-KAZAKTELECOM-20071220 |
| └ 92.46.191.212/30 | 4 | NCERK | Pavlodar region | ASSIGNED PA | Feb 26, 2025 | abuse@ via KZ-KAZAKTELECOM-20071220 |
| └ 92.46.191.216/30 | 4 | KGKPDXSH | unknown | ASSIGNED PA | Jul 20, 2026 | abuse@ via KZ-KAZAKTELECOM-20071220 |
| └ 92.46.191.220/30 | 4 | TOONIKMUN | TOONIKAMUNAI | ASSIGNED PA | Dec 4, 2012 | abuse@ via KZ-KAZAKTELECOM-20071220 |
| └ 92.46.191.224/30 | 4 | TOOPAVLODARENERGOSBYT | PAVLODAR | ASSIGNED PA | Jul 22, 2019 | abuse@ via KZ-KAZAKTELECOM-20071220 |
| └ 92.46.191.228/30 | 4 | MIKRK_ | Pavlodar | ASSIGNED PA | Oct 23, 2019 | abuse@ via KZ-KAZAKTELECOM-20071220 |
| └ 92.46.191.232/30 | 4 | KAZAHINSTRAH_ | KAZAHINSTRAH | ASSIGNED PA | Oct 24, 2008 | abuse@ via KZ-KAZAKTELECOM-20071220 |
| └ 92.46.191.236/30 | 4 | NCERK | Pavlodar region | ASSIGNED PA | Feb 26, 2025 | abuse@ via KZ-KAZAKTELECOM-20071220 |
| └ 92.46.191.240/30 | 4 | GUSOSH28 | PAVLODAR | ASSIGNED PA | Feb 1, 2016 | abuse@ via KZ-KAZAKTELECOM-20071220 |
| └ 92.46.191.244/30 | 4 | PFAOBAYANSULU | PAVLODAR | ASSIGNED PA | May 13, 2016 | abuse@ via KZ-KAZAKTELECOM-20071220 |
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
4,096 addresses
| Type | Addresses | Share | Ranges | |
|---|---|---|---|---|
| Residential | 2,488 | 61% | 24 | |
| Business | 1,607 | 39% | 314 | |
| Hosting | 1 | 0.02% | 1 |
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
- Feb 2008
- Current origin since
- Feb 2008 · 19 yr
- Origin networks
- 1
RPKI
Route origin authorizations
| ROA prefix | ASN | Max len | Anchor | Verdict |
|---|---|---|---|---|
| 92.46.176.0/20 | AS9198 | /24 | RIPE | RPKI valid |
| 92.46.0.0/15 | AS9198 | /24 | RIPE | RPKI valid |
| 92.46.0.0/15 | AS50482 | /24 | RIPE | Another network |
IRR
Route objects on the exact prefix
| Origin | Registry | Description | Maintainer | Modified |
|---|---|---|---|---|
| AS9198 | RIPE | Kazakhtelecom Data Network Administration | KNIC-MNT | Oct 8, 2008 |
IRR inside
Route objects inside
| Prefix | Origin | Registry | Description | Maintainer | Modified |
|---|---|---|---|---|---|
| 92.46.176.0/22 | AS9198 | RIPE | Megaline Pavlodav | KNIC-MNT | Feb 16, 2009 |
| 92.46.176.0/24 | AS9198 | RIPE | Kazakhtelecom Megaline Pavlodav Network | KNIC-MNT | May 14, 2008 |
| 92.46.177.0/24 | AS9198 | RIPE | Kazakhtelecom Megaline Pavlodav Network | KNIC-MNT | May 14, 2008 |
| 92.46.178.0/24 | AS9198 | RIPE | Kazakhtelecom Megaline Pavlodav Network | KNIC-MNT | May 14, 2008 |
| 92.46.179.0/24 | AS9198 | RIPE | Kazakhtelecom Megaline Pavlodav Network | KNIC-MNT | May 14, 2008 |
| 92.46.180.0/24 | AS9198 | RIPE | Kazakhtelecom Megaline Pavlodav Network | KNIC-MNT | May 14, 2008 |
| 92.46.181.0/24 | AS9198 | RIPE | Kazakhtelecom Megaline Pavlodav Network | KNIC-MNT | Oct 8, 2008 |
| 92.46.182.0/24 | AS9198 | RIPE | Kazakhtelecom Megaline Pavlodav Network | KNIC-MNT | Oct 8, 2008 |
| 92.46.183.0/24 | AS9198 | RIPE | Kazakhtelecom Megaline Pavlodav Network | KNIC-MNT | Oct 8, 2008 |
| 92.46.184.0/24 | AS9198 | RIPE | Kazakhtelecom Megaline Pavlodav Network | KNIC-MNT | Oct 8, 2008 |
| 92.46.185.0/24 | AS9198 | RIPE | Kazakhtelecom Megaline Pavlodav Network | KNIC-MNT | Oct 8, 2008 |
| 92.46.186.0/23 | AS9198 | RIPE | Kazakhtelecom Data Network Administration | KNIC-MNT | Mar 14, 2011 |
| 92.46.186.0/24 | AS9198 | RIPE | Kazakhtelecom Megaline Pavlodav Network | KNIC-MNT | Oct 8, 2008 |
| 92.46.187.0/24 | AS9198 | RIPE | Kazakhtelecom Megaline Pavlodav Network | KNIC-MNT | Oct 8, 2008 |
| 92.46.188.0/23 | AS9198 | RIPE | Kazakhtelecom Data Network Administration | KNIC-MNT | Mar 14, 2011 |
| 92.46.188.0/24 | AS9198 | RIPE | Kazakhtelecom Megaline Pavlodav Network | KNIC-MNT | Oct 8, 2008 |
| 92.46.189.0/24 | AS9198 | RIPE | Kazakhtelecom Megaline Pavlodav Network | KNIC-MNT | Oct 8, 2008 |
| 92.46.190.0/24 | AS9198 | RIPE | Kazakhtelecom Megaline Pavlodav Network | KNIC-MNT | Oct 8, 2008 |
Whois
Registration for this announcement
- Range
- 92.
46. 0. 0/ 15 - Netname
- KZ-KAZAKTELECOM-20071220
- Registrant
- JSC Kazakhtelecom
- Registrant country
- KZ
- Organization
- JSC Kazakhtelecom (ORG-KDNA1-RIPE)
- Org country
- KZ
- Type
- ALLOCATED PA
- Created
- Dec 20, 2007
- Updated
- Jun 23, 2016
- Maintainer
- RIPE-NCC-HM-MNT
- RIR
- RIPE NCC
- Country
- KZ
- Delegated
- Dec 20, 2007
- Status
- assigned
Report abuse
Abuse contact
- abuse@
telecom. kz - Name
- Kazakhtelecom Network Information Center
- Handle
- KNIC1-RIPE