Data as of Nov 7, 2026
82.200.181.0/24
11 residential-proxy exits · 30 daysJSC Kazakhtelecom
Residential-proxy exits
Proxy exits
11
4.3% of its addresses · 30 days
Providers
42
selling exits here
Oct 8, 2026 – Nov 6, 2026
Exits seen per day
2.1K observations
- Residential
- Business
Proxy providers listing exits
- 2Captcha
- 9Proxy
- AnyIP
- BestProxy
- BirdProxies
- BottingTools
- ByteProxies
- Byteful
- CliProxy
- EnigmaProxy
- Evomi
- FastProxy
- FlashProxy
- Geonode
- GonzoProxy
- HydraProxy
- IPOasis
- Infatica
- InfiniteProxies
- LemonBright
- MangoProxy
- NSocks
- NiuProxy
- NodeProxy
- NovProxy
- NovaProxy
- Oxylabs
- Proxiware
- Proxy-Seller
- ProxyEmpire
- ProxyHat
- ProxyWing
- Proxyma
- RainProxy
- Shifter
- Smartproxy
- Thordata
- ThunderProxy
- VantageProxies
- 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 this block, widest first, each 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.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
256 addresses
| Type | Addresses | Share | Ranges | |
|---|---|---|---|---|
| Business | 248 | 97% | 62 | |
| Residential | 8 | 3.1% | 2 |
Network & registry
Announced by
Covering announcement 82.200.180.0/23
- Prefix
- 82.200.180.0/23
- Announced by
- AS9198 JSC Kazakhtelecom
- Type
- Residential
- Proxy exits
- 16
- RPKI
- RPKI valid
- Netname
- KZ-KAZAKTELECOM-20030918
- Registrant
- JSC Kazakhtelecom
- RIR
- RIPE NCC
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
82.200.180.0/23
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 82.200.180.0/23
| Origin | Registry | Description | Maintainer | Modified |
|---|---|---|---|---|
| AS9198 | RIPE | Kazakhtelecom Data Network Administration | KNIC-MNT | Jun 10, 2009 |
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