Data as of Nov 7, 2026
82.200.180.0/23
16 residential-proxy exits · 30 daysJSC Kazakhtelecom
Residential-proxy exits
Proxy exits
16
3.1% of its addresses · 30 days
Spread
2 of 2
/24s with at least one exit
Providers
47
selling exits here
Oct 8, 2026 – Nov 6, 2026
Exits seen per day
3.0K observations
- Residential
- Business
/24s with the most always-on exits
| /24 | Always-on exits | Proxy exits | |
|---|---|---|---|
| 82.200.181.0/24 | 0 | 11 | |
| 82.200.180.0/24 | 0 | 5 |
Proxy providers listing exits
- 2Captcha
- 9Proxy
- AnyIP
- BestProxy
- BirdProxies
- BottingTools
- ByteProxies
- Byteful
- CliProxy
- EnigmaProxy
- Evomi
- FastProxy
- FlashProxy
- GSocks
- Geonix
- Geonode
- GonzoProxy
- HydraProxy
- IPOasis
- Infatica
- InfiniteProxies
- LemonBright
- LemonLabs
- MangoProxy
- NSocks
- NiuProxy
- NodeMaven
- NodeProxy
- NovProxy
- NovaProxy
- Oxylabs
- Proxiware
- Proxy-Seller
- ProxyEmpire
- ProxyHat
- ProxyWing
- Proxyma
- RainProxy
- Shifter
- Smartproxy
- Thordata
- ThunderProxy
- VantageProxies
- VibeProxies
- VitalData
- VitalExclusive
- VitalProxy
Announcements
Less specific
Covering announcements
| Prefix | Origin | Type | Proxy exits | Holder | RPKI |
|---|---|---|---|---|---|
| 82.200.128.0/17 since May 2005 | AS9198 | Residential | 752 40 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 |
|---|---|---|---|---|---|---|
| 82.200.128.0/17 | 32,768 | KZ-KAZAKTELECOM-20030918 | JSC Kazakhtelecom (ORG-KDNA1-RIPE) · KZ | ALLOCATED PA | Sep 18, 2003 | abuse@ |
| └ 82.200.180.0/30 | 4 | ATAMEKEN_ | TOO «atameken Agro Timiryazevo 2» | ASSIGNED PA | Jul 25, 2017 | abuse@ via KZ-KAZAKTELECOM-20030918 |
| └ 82.200.180.4/30 | 4 | TOO_ | TOO «too Atameken Agro 2» | ASSIGNED PA | Jul 25, 2017 | abuse@ via KZ-KAZAKTELECOM-20030918 |
| └ 82.200.180.8/30 | 4 | TOO_ | TOO «too PSH» | ASSIGNED PA | Jul 25, 2017 | abuse@ via KZ-KAZAKTELECOM-20030918 |
| └ 82.200.180.12/30 | 4 | TOO_ | TOO «too Atameken Agroblag 2» | ASSIGNED PA | Jul 27, 2017 | abuse@ via KZ-KAZAKTELECOM-20030918 |
| └ 82.200.180.16/30 | 4 | TOO_ | TOO «too Atameken Agroblag 2» | ASSIGNED PA | Jul 27, 2017 | abuse@ via KZ-KAZAKTELECOM-20030918 |
| └ 82.200.180.20/30 | 4 | GU_ | unknown | ASSIGNED PA | May 8, 2026 | abuse@ via KZ-KAZAKTELECOM-20030918 |
| └ 82.200.180.24/30 | 4 | KGKP_ | KGKP «KGKP DOM Kultury 2» | ASSIGNED PA | Aug 10, 2017 | abuse@ via KZ-KAZAKTELECOM-20030918 |
| └ 82.200.180.28/30 | 4 | GU_ | unknown | ASSIGNED PA | Mar 27, 2026 | abuse@ via KZ-KAZAKTELECOM-20030918 |
| └ 82.200.180.32/30 | 4 | AKIMAT_ | GU «akimat Suhorabovskogoso Schalakyn» | ASSIGNED PA | Aug 10, 2017 | abuse@ via KZ-KAZAKTELECOM-20030918 |
| └ 82.200.180.36/30 | 4 | AKIMAT_ | GU «akimat Novopokrovskogoso Schalakyn» | ASSIGNED PA | Aug 10, 2017 | abuse@ via KZ-KAZAKTELECOM-20030918 |
| └ 82.200.180.40/30 | 4 | TOO_ | unknown | ASSIGNED PA | Aug 10, 2026 | abuse@ via KZ-KAZAKTELECOM-20030918 |
| └ 82.200.180.44/30 | 4 | KGU_ | KGU «kgu Spezbaza Apparatakimasko 2» | ASSIGNED PA | Aug 18, 2017 | abuse@ via KZ-KAZAKTELECOM-20030918 |
| └ 82.200.180.48/30 | 4 | TOO_ | Petropavlovsk | ASSIGNED PA | Aug 18, 2021 | abuse@ via KZ-KAZAKTELECOM-20030918 |
| └ 82.200.180.52/30 | 4 | KGU_ | RC Taiynsha | ASSIGNED PA | Aug 23, 2021 | abuse@ via KZ-KAZAKTELECOM-20030918 |
| └ 82.200.180.56/30 | 4 | AO_ | AO <sirimbet> | ASSIGNED PA | May 5, 2016 | abuse@ via KZ-KAZAKTELECOM-20030918 |
| └ 82.200.180.60/30 | 4 | GU_ | GU <apparat Akima Petropavlovska> | ASSIGNED PA | Jul 25, 2016 | abuse@ via KZ-KAZAKTELECOM-20030918 |
| └ 82.200.180.64/30 | 4 | KGU_ | KGU «kgu Spezbaza Apparatakimasko 3» | ASSIGNED PA | Aug 18, 2017 | abuse@ via KZ-KAZAKTELECOM-20030918 |
| └ 82.200.180.68/30 | 4 | GU_ | KGU «GU Otdobrazovan Jambylskogo 38» | ASSIGNED PA | Aug 17, 2018 | abuse@ via KZ-KAZAKTELECOM-20030918 |
| └ 82.200.180.72/29 | 8 | TOO_ | TOO «too Ureland» | ASSIGNED PA | Aug 18, 2017 | abuse@ via KZ-KAZAKTELECOM-20030918 |
| └ 82.200.180.80/30 | 4 | KGU_ | RC Bulaevo | ASSIGNED PA | Sep 22, 2020 | abuse@ via KZ-KAZAKTELECOM-20030918 |
| └ 82.200.180.84/30 | 4 | TOO_ | RC Mamlyutka | ASSIGNED PA | May 22, 2025 | abuse@ via KZ-KAZAKTELECOM-20030918 |
| └ 82.200.180.88/30 | 4 | TOO_ | Petropavlovsk | ASSIGNED PA | May 23, 2025 | abuse@ via KZ-KAZAKTELECOM-20030918 |
| └ 82.200.180.92/30 | 4 | SHKOLA_ | unknown | ASSIGNED PA | Apr 21, 2026 | abuse@ via KZ-KAZAKTELECOM-20030918 |
| └ 82.200.180.96/30 | 4 | GU_ | unknown | ASSIGNED PA | May 8, 2026 | abuse@ via KZ-KAZAKTELECOM-20030918 |
| └ 82.200.180.100/30 | 4 | GU_ | KGU «GU Otdobrazovan Jambylskogo 14» | ASSIGNED PA | Sep 11, 2017 | abuse@ via KZ-KAZAKTELECOM-20030918 |
| └ 82.200.180.104/30 | 4 | GU_ | KGU «GU Otdobrazovan Jambylskogo 15» | ASSIGNED PA | Sep 11, 2017 | abuse@ via KZ-KAZAKTELECOM-20030918 |
| └ 82.200.180.108/30 | 4 | GU_ | KGU «GU Otdobrazovan Jambylskogo 16» | ASSIGNED PA | Sep 11, 2017 | abuse@ via KZ-KAZAKTELECOM-20030918 |
| └ 82.200.180.112/30 | 4 | GU_ | KGU «GU Otdobrazovan Jambylskogo 17» | ASSIGNED PA | Sep 11, 2017 | abuse@ via KZ-KAZAKTELECOM-20030918 |
| └ 82.200.180.116/30 | 4 | GU_ | unknown | ASSIGNED PA | Mar 20, 2026 | abuse@ via KZ-KAZAKTELECOM-20030918 |
| └ 82.200.180.120/30 | 4 | GU_ | KGU «GU Otdobrazovan Jambylskogo 19» | ASSIGNED PA | Sep 11, 2017 | abuse@ via KZ-KAZAKTELECOM-20030918 |
| └ 82.200.180.124/30 | 4 | RGP_ | Petropavlovsk | ASSIGNED PA | Oct 28, 2020 | abuse@ via KZ-KAZAKTELECOM-20030918 |
| └ 82.200.180.128/30 | 4 | TOO_ | RC Saumalkol | ASSIGNED PA | Nov 30, 2020 | abuse@ via KZ-KAZAKTELECOM-20030918 |
| └ 82.200.180.132/30 | 4 | GU_ | RC Saumalkol | ASSIGNED PA | Jun 3, 2024 | abuse@ via KZ-KAZAKTELECOM-20030918 |
| └ 82.200.180.144/30 | 4 | KGU_ | RC Kishkenekol | ASSIGNED PA | Jun 5, 2024 | abuse@ via KZ-KAZAKTELECOM-20030918 |
| └ 82.200.180.152/30 | 4 | NARKOLOG_ | KGKP «narkolog Organizaziya Jambylskogo» | ASSIGNED PA | Oct 9, 2017 | abuse@ via KZ-KAZAKTELECOM-20030918 |
| └ 82.200.180.156/30 | 4 | NARKOLOG_ | KGKP «narkolog Organizaziya Jambylskogo 2» | ASSIGNED PA | Oct 9, 2017 | abuse@ via KZ-KAZAKTELECOM-20030918 |
| └ 82.200.180.160/30 | 4 | KGU_ | RC Novoishimskoe | ASSIGNED PA | Apr 13, 2023 | abuse@ via KZ-KAZAKTELECOM-20030918 |
| └ 82.200.180.164/30 | 4 | TOO_ | RC Saumalkol | ASSIGNED PA | Apr 15, 2025 | abuse@ via KZ-KAZAKTELECOM-20030918 |
| └ 82.200.180.168/30 | 4 | SHKOLA_ | unknown | ASSIGNED PA | Apr 20, 2026 | abuse@ via KZ-KAZAKTELECOM-20030918 |
| └ 82.200.180.172/30 | 4 | GU_ | unknown | ASSIGNED PA | Jul 21, 2026 | abuse@ via KZ-KAZAKTELECOM-20030918 |
| └ 82.200.180.176/30 | 4 | RGP_ | Petropavlovsk | ASSIGNED PA | Feb 8, 2023 | abuse@ via KZ-KAZAKTELECOM-20030918 |
| └ 82.200.180.192/30 | 4 | TOO_ | RC Yavlenka | ASSIGNED PA | Aug 7, 2024 | abuse@ via KZ-KAZAKTELECOM-20030918 |
| └ 82.200.180.196/30 | 4 | TOO_ | Petropavlovsk | ASSIGNED PA | Apr 5, 2023 | abuse@ via KZ-KAZAKTELECOM-20030918 |
| └ 82.200.180.200/30 | 4 | TOO_ | TOO «too Asyl Grain» | ASSIGNED PA | Jul 31, 2018 | abuse@ via KZ-KAZAKTELECOM-20030918 |
| └ 82.200.180.204/30 | 4 | OTD_ | GU Otdel ekonomiki I budjetnogo planirovaniya Mendykarinskogo rayona | ASSIGNED PA | Jan 20, 2018 | abuse@ via KZ-KAZAKTELECOM-20030918 |
| └ 82.200.180.208/30 | 4 | TOO_ | Petropavlovsk | ASSIGNED PA | Apr 26, 2023 | abuse@ via KZ-KAZAKTELECOM-20030918 |
| └ 82.200.180.212/30 | 4 | EAST_ | TOO «east Management Company» | ASSIGNED PA | Oct 18, 2017 | abuse@ via KZ-KAZAKTELECOM-20030918 |
| └ 82.200.180.216/29 | 8 | IP_ | Oleg Kim | ASSIGNED PA | Oct 29, 2018 | abuse@ via KZ-KAZAKTELECOM-20030918 |
| └ 82.200.180.224/30 | 4 | RGP_ | unknown | ASSIGNED PA | Mar 20, 2026 | abuse@ via KZ-KAZAKTELECOM-20030918 |
| └ 82.200.180.228/30 | 4 | DETSKIY_ | GKKP <detskiy SAD <rosinka> | ASSIGNED PA | Oct 10, 2016 | abuse@ via KZ-KAZAKTELECOM-20030918 |
| └ 82.200.180.232/30 | 4 | TOO_ | RC Bulaevo | ASSIGNED PA | Feb 10, 2022 | abuse@ via KZ-KAZAKTELECOM-20030918 |
| └ 82.200.180.236/30 | 4 | PETROPAVLOVSK_ | Petropavlovsk | ASSIGNED PA | Jun 3, 2019 | abuse@ via KZ-KAZAKTELECOM-20030918 |
| └ 82.200.180.240/30 | 4 | GU_ | RC Timiryazevo | ASSIGNED PA | Apr 1, 2024 | abuse@ via KZ-KAZAKTELECOM-20030918 |
| └ 82.200.180.244/30 | 4 | GU_ | RC Kishkenekol | ASSIGNED PA | Apr 4, 2024 | abuse@ via KZ-KAZAKTELECOM-20030918 |
| └ 82.200.181.0/30 | 4 | KGU_ | KGU «kgu Shoptykolskaya Shkolainternat» | ASSIGNED PA | Jan 9, 2018 | abuse@ via KZ-KAZAKTELECOM-20030918 |
| └ 82.200.181.4/30 | 4 | KGU_ | KGU «kgu Lomonosovskaya Shkolainternat» | ASSIGNED PA | Jan 9, 2018 | abuse@ via KZ-KAZAKTELECOM-20030918 |
| └ 82.200.181.8/30 | 4 | KGU_ | KGU «kgu Apparatakima Lomonosovskogo» | ASSIGNED PA | Jan 9, 2018 | abuse@ via KZ-KAZAKTELECOM-20030918 |
| └ 82.200.181.12/30 | 4 | GU_ | KGU «GU Otdobrazovan Jambylskogo 35» | ASSIGNED PA | Aug 23, 2018 | abuse@ via KZ-KAZAKTELECOM-20030918 |
| └ 82.200.181.16/30 | 4 | GU_ | KGU «GU Otdobrazovan Jambylskogo 36» | ASSIGNED PA | Aug 23, 2018 | abuse@ via KZ-KAZAKTELECOM-20030918 |
| └ 82.200.181.20/30 | 4 | KORREKCIONNAYA_ | Petropavlovsk | ASSIGNED PA | Nov 10, 2024 | abuse@ via KZ-KAZAKTELECOM-20030918 |
| └ 82.200.181.24/30 | 4 | KGU_ | KGU «kgu Apparatakima Jambylskogo» | ASSIGNED PA | Aug 25, 2018 | abuse@ via KZ-KAZAKTELECOM-20030918 |
| └ 82.200.181.28/30 | 4 | TOO_ | RC Smirnovo | ASSIGNED PA | Jul 15, 2024 | abuse@ via KZ-KAZAKTELECOM-20030918 |
| └ 82.200.181.32/30 | 4 | TOO_ | TOO «too Agrokom Madeniet» | ASSIGNED PA | Feb 27, 2018 | abuse@ via KZ-KAZAKTELECOM-20030918 |
| └ 82.200.181.36/30 | 4 | GU_ | KGU «GU Centrzanyatosti Taiynshinsk» | ASSIGNED PA | Feb 27, 2018 | abuse@ via KZ-KAZAKTELECOM-20030918 |
| └ 82.200.181.40/30 | 4 | TOO_ | unknown | ASSIGNED PA | Jul 25, 2018 | abuse@ via KZ-KAZAKTELECOM-20030918 |
| └ 82.200.181.44/30 | 4 | TOO_ | unknown | ASSIGNED PA | May 3, 2016 | abuse@ via KZ-KAZAKTELECOM-20030918 |
| └ 82.200.181.48/30 | 4 | IP_ | IP «IP Semenova Elena» | ASSIGNED PA | Jan 26, 2018 | abuse@ via KZ-KAZAKTELECOM-20030918 |
| └ 82.200.181.52/30 | 4 | KYZYLJARSKAYA_ | KGP «kyzyljarskaya Raionnaya Bolnica» | ASSIGNED PA | Jan 30, 2018 | abuse@ via KZ-KAZAKTELECOM-20030918 |
| └ 82.200.181.56/30 | 4 | KGU_ | Petropavlovsk | ASSIGNED PA | Mar 31, 2023 | abuse@ via KZ-KAZAKTELECOM-20030918 |
| └ 82.200.181.60/30 | 4 | DETSKII_ | GKKP «detskii SAD Baldauren» | ASSIGNED PA | Feb 16, 2018 | abuse@ via KZ-KAZAKTELECOM-20030918 |
| └ 82.200.181.64/30 | 4 | DETSKII_ | KGKP «detskii SAD Solnyshko» | ASSIGNED PA | Feb 16, 2018 | abuse@ via KZ-KAZAKTELECOM-20030918 |
| └ 82.200.181.68/30 | 4 | VETERINAR_ | GKP «veterinar Stanziya Kicschkenekol 3» | ASSIGNED PA | Feb 16, 2018 | abuse@ via KZ-KAZAKTELECOM-20030918 |
| └ 82.200.181.72/30 | 4 | VETERINAR_ | GKP «veterinar Stanziya Kicschkenekol 4» | ASSIGNED PA | Feb 16, 2018 | abuse@ via KZ-KAZAKTELECOM-20030918 |
| └ 82.200.181.76/30 | 4 | GU_ | Petropavlovsk | ASSIGNED PA | Jan 8, 2026 | abuse@ via KZ-KAZAKTELECOM-20030918 |
| └ 82.200.181.84/30 | 4 | KGU_ | KGU «kgu Bibliotechnaya Sistema» | ASSIGNED PA | Feb 16, 2018 | abuse@ via KZ-KAZAKTELECOM-20030918 |
| └ 82.200.181.88/30 | 4 | UALIHANOVSKII_ | KGU «ualihanovskii Selhoz Kolledzh» | ASSIGNED PA | Feb 16, 2018 | abuse@ via KZ-KAZAKTELECOM-20030918 |
| └ 82.200.181.92/30 | 4 | KGU_ | unknown | ASSIGNED PA | Feb 19, 2026 | abuse@ via KZ-KAZAKTELECOM-20030918 |
| └ 82.200.181.96/30 | 4 | UALIHANOVSKII_ | KGU «ualihanovskii Selhoz Kolledzh 3» | ASSIGNED PA | Feb 16, 2018 | abuse@ via KZ-KAZAKTELECOM-20030918 |
| └ 82.200.181.100/30 | 4 | GU_ | KGU «GU Otdobrazovan Jambylskogo 39» | ASSIGNED PA | Aug 17, 2018 | abuse@ via KZ-KAZAKTELECOM-20030918 |
| └ 82.200.181.104/30 | 4 | TOO_ | RC Taiynsha | ASSIGNED PA | Nov 8, 2022 | abuse@ via KZ-KAZAKTELECOM-20030918 |
| └ 82.200.181.112/30 | 4 | UALIHANOVSKAYA_ | KGP «ualihanovskaya Raion BOLNICA3» | ASSIGNED PA | Feb 20, 2018 | abuse@ via KZ-KAZAKTELECOM-20030918 |
| └ 82.200.181.116/30 | 4 | RAIONNAYA_ | RC Novoishimskoe | ASSIGNED PA | Jun 13, 2019 | abuse@ via KZ-KAZAKTELECOM-20030918 |
| └ 82.200.181.120/30 | 4 | TOO_ | RC Novoishimskoe | ASSIGNED PA | Apr 14, 2021 | abuse@ via KZ-KAZAKTELECOM-20030918 |
| └ 82.200.181.124/30 | 4 | GU_ | unknown | ASSIGNED PA | Apr 7, 2026 | abuse@ via KZ-KAZAKTELECOM-20030918 |
| └ 82.200.181.128/30 | 4 | AO_ | Petropavlovsk | ASSIGNED PA | Oct 8, 2024 | abuse@ via KZ-KAZAKTELECOM-20030918 |
| └ 82.200.181.132/30 | 4 | NCERK | Saumalkol Ayyr | ASSIGNED PA | Feb 27, 2025 | abuse@ via KZ-KAZAKTELECOM-20030918 |
| └ 82.200.181.136/30 | 4 | KGU_ | RC Taiynsha | ASSIGNED PA | Nov 27, 2023 | abuse@ via KZ-KAZAKTELECOM-20030918 |
| └ 82.200.181.140/30 | 4 | GU_ | RC Presnovka | ASSIGNED PA | Dec 9, 2022 | abuse@ via KZ-KAZAKTELECOM-20030918 |
| └ 82.200.181.144/30 | 4 | TOO_ | RC Presnovka | ASSIGNED PA | Nov 20, 2020 | abuse@ via KZ-KAZAKTELECOM-20030918 |
| └ 82.200.181.148/30 | 4 | GU_ | RC Sergeevka | ASSIGNED PA | Nov 6, 2020 | abuse@ via KZ-KAZAKTELECOM-20030918 |
| └ 82.200.181.152/30 | 4 | GU_ | RC Mamlyutka | ASSIGNED PA | Nov 4, 2020 | abuse@ via KZ-KAZAKTELECOM-20030918 |
| └ 82.200.181.156/30 | 4 | OBLASTNAYA_ | Petropavlovsk | ASSIGNED PA | Oct 23, 2020 | abuse@ via KZ-KAZAKTELECOM-20030918 |
| └ 82.200.181.160/30 | 4 | RGP_ | RC Sergeevka | ASSIGNED PA | Apr 10, 2025 | abuse@ via KZ-KAZAKTELECOM-20030918 |
| └ 82.200.181.164/30 | 4 | KGU_ | unknown | ASSIGNED PA | Mar 11, 2026 | abuse@ via KZ-KAZAKTELECOM-20030918 |
| └ 82.200.181.168/30 | 4 | GU_ | GU «GU Otdelobraz Ualihanovskogo 25» | ASSIGNED PA | Feb 20, 2018 | abuse@ via KZ-KAZAKTELECOM-20030918 |
| └ 82.200.181.172/30 | 4 | GU_ | GU «GU Otdelobraz Ualihanovskogo 26» | ASSIGNED PA | Feb 20, 2018 | abuse@ via KZ-KAZAKTELECOM-20030918 |
| └ 82.200.181.176/30 | 4 | HOMECREDIT | Bulaevo | ASSIGNED PA | Oct 8, 2024 | abuse@ via KZ-KAZAKTELECOM-20030918 |
| └ 82.200.181.180/30 | 4 | VETERINARNAYA_ | GKP «veterinarnaya Stanciya Taiynshinskogo» | ASSIGNED PA | Feb 26, 2018 | abuse@ via KZ-KAZAKTELECOM-20030918 |
| └ 82.200.181.184/30 | 4 | VETERINARNAYA_ | GKP «veterinarnaya Stanciya Taiynshinskogo 2» | ASSIGNED PA | Feb 26, 2018 | abuse@ via KZ-KAZAKTELECOM-20030918 |
| └ 82.200.181.188/30 | 4 | VETERINARNAYA_ | GKP «veterinarnaya Stanciya Taiynshinskogo 3» | ASSIGNED PA | Feb 26, 2018 | abuse@ via KZ-KAZAKTELECOM-20030918 |
| └ 82.200.181.192/30 | 4 | VETERINARNAYA_ | GKP «veterinarnaya Stanciya Taiynshinskogo 4» | ASSIGNED PA | Feb 26, 2018 | abuse@ via KZ-KAZAKTELECOM-20030918 |
| └ 82.200.181.196/30 | 4 | GU_ | RC Novoishimskoe | ASSIGNED PA | Mar 14, 2025 | abuse@ via KZ-KAZAKTELECOM-20030918 |
| └ 82.200.181.200/30 | 4 | KGU_ | RC Talshik | ASSIGNED PA | Oct 29, 2021 | abuse@ via KZ-KAZAKTELECOM-20030918 |
| └ 82.200.181.204/30 | 4 | VETERINARNAYA_ | GKP «veterinarnaya Stanciya Taiynshinskogo 7» | ASSIGNED PA | Feb 26, 2018 | abuse@ via KZ-KAZAKTELECOM-20030918 |
| └ 82.200.181.208/30 | 4 | KGU_ | Petropavlovsk | ASSIGNED PA | Jan 5, 2026 | abuse@ via KZ-KAZAKTELECOM-20030918 |
| └ 82.200.181.212/30 | 4 | VETERINARNAYA_ | GKP «veterinarnaya Stanciya Taiynshinskogo 9» | ASSIGNED PA | Feb 26, 2018 | abuse@ via KZ-KAZAKTELECOM-20030918 |
| └ 82.200.181.216/30 | 4 | VETERINARNAYA_ | GKP «veterinarnaya Stanciya Taiynshinskogo 10» | ASSIGNED PA | Feb 26, 2018 | abuse@ via KZ-KAZAKTELECOM-20030918 |
| └ 82.200.181.220/30 | 4 | VETERINARNAYA_ | GKP «veterinarnaya Stanciya Taiynshinskogo 11» | ASSIGNED PA | Feb 26, 2018 | abuse@ via KZ-KAZAKTELECOM-20030918 |
| └ 82.200.181.224/30 | 4 | VETERINARNAYA_ | GKP «veterinarnaya Stanciya Taiynshinskogo 12» | ASSIGNED PA | Feb 26, 2018 | abuse@ via KZ-KAZAKTELECOM-20030918 |
| └ 82.200.181.228/30 | 4 | VETERINARNAYA_ | GKP «veterinarnaya Stanciya Taiynshinskogo 13» | ASSIGNED PA | Feb 26, 2018 | abuse@ via KZ-KAZAKTELECOM-20030918 |
| └ 82.200.181.232/30 | 4 | KGU_ | unknown | ASSIGNED PA | Sep 15, 2026 | abuse@ via KZ-KAZAKTELECOM-20030918 |
| └ 82.200.181.236/30 | 4 | VETERINARNAYA_ | GKP «veterinarnaya Stanciya Taiynshinskogo 15» | ASSIGNED PA | Feb 26, 2018 | abuse@ via KZ-KAZAKTELECOM-20030918 |
| └ 82.200.181.240/30 | 4 | VETERINARNAYA_ | GKP «veterinarnaya Stanciya Taiynshinskogo 16» | ASSIGNED PA | Feb 26, 2018 | abuse@ via KZ-KAZAKTELECOM-20030918 |
| └ 82.200.181.244/30 | 4 | TOO_ | Petropavlovsk | ASSIGNED PA | Sep 25, 2024 | abuse@ via KZ-KAZAKTELECOM-20030918 |
| └ 82.200.181.248/30 | 4 | LENINGRADSKII_ | KGU «leningradskii Selhoz Kolledzh» | ASSIGNED PA | Feb 26, 2018 | abuse@ via KZ-KAZAKTELECOM-20030918 |
| └ 82.200.181.252/30 | 4 | LENINGRADSKII_ | KGU «leningradskii Selhoz Kolledzh 2» | ASSIGNED PA | Feb 26, 2018 | abuse@ via KZ-KAZAKTELECOM-20030918 |
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
512 addresses
| Type | Addresses | Share | Ranges | |
|---|---|---|---|---|
| Business | 472 | 92% | 116 | |
| Residential | 40 | 7.8% | 6 |
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
- Jun 2009
- Current origin since
- Jun 2009 · 17 yr
- Origin networks
- 1
RPKI
Route origin authorizations
| ROA prefix | ASN | Max len | Anchor | Verdict |
|---|---|---|---|---|
| 82.200.180.0/23 | AS9198 | /23 | RIPE | RPKI valid |
| 82.200.128.0/17 | 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 10, 2009 |
IRR inside
Route objects inside
| Prefix | Origin | Registry | Description | Maintainer | Modified |
|---|---|---|---|---|---|
| 82.200.180.0/24 | AS9198 | RIPE | Kazakhtelecom Data Network Administration | KNIC-MNT | Oct 8, 2008 |
| 82.200.181.0/24 | AS9198 | RIPE | Kazakhtelecom Data Network Administration | KNIC-MNT | Oct 8, 2008 |
Whois
Registration for this announcement
- Range
- 82.
200. 128. 0/ 17 - Netname
- KZ-KAZAKTELECOM-20030918
- Registrant
- JSC Kazakhtelecom
- Registrant country
- KZ
- Organization
- JSC Kazakhtelecom (ORG-KDNA1-RIPE)
- Org country
- KZ
- Type
- ALLOCATED PA
- Created
- Sep 18, 2003
- Updated
- Jun 23, 2016
- Maintainer
- RIPE-NCC-HM-MNT
- RIR
- RIPE NCC
- Country
- KZ
- Delegated
- Sep 18, 2003
- Status
- assigned
Report abuse
Abuse contact
- abuse@
telecom. kz - Name
- Kazakhtelecom Network Information Center
- Handle
- KNIC1-RIPE