Data as of Nov 7, 2026
82.200.207.0/24
2 residential-proxy exits · 30 daysJSC Kazakhtelecom
Residential-proxy exits
Proxy exits
2
0.78% of its addresses · 30 days
Providers
23
selling exits here
Oct 8, 2026 – Nov 6, 2026
Exits seen per day
227 observations
Proxy providers listing exits
- BestProxy
- BirdProxies
- ByteProxies
- Byteful
- CliProxy
- EnigmaProxy
- FlashProxy
- GSocks
- GonzoProxy
- Infatica
- MangoProxy
- NSocks
- NodeProxy
- NovProxy
- NovaProxy
- Proxiware
- Proxy-Seller
- ProxyEmpire
- Proxyma
- RainProxy
- Shifter
- Smartproxy
- VantageProxies
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.207.0/30 | 4 | ENPF | AO <NPF GNPF> | ASSIGNED PA | Jul 27, 2012 | abuse@ via KZ-KAZAKTELECOM-20030918 |
| └ 82.200.207.4/30 | 4 | ENPF | AO <NPF GNPF> | ASSIGNED PA | Jul 27, 2012 | abuse@ via KZ-KAZAKTELECOM-20030918 |
| └ 82.200.207.8/30 | 4 | ENPF | AO <NPF GNPF> | ASSIGNED PA | Jul 27, 2012 | abuse@ via KZ-KAZAKTELECOM-20030918 |
| └ 82.200.207.12/30 | 4 | DVLine | DVLine | ASSIGNED PA | Nov 5, 2019 | abuse@ via KZ-KAZAKTELECOM-20030918 |
| └ 82.200.207.16/29 | 8 | IP_ | unknown | ASSIGNED PA | Oct 7, 2026 | abuse@ via KZ-KAZAKTELECOM-20030918 |
| └ 82.200.207.24/30 | 4 | DIS | JSC Kazakhtelecom, Direction of Information System | ASSIGNED PA | Aug 10, 2012 | abuse@ via KZ-KAZAKTELECOM-20030918 |
| └ 82.200.207.28/30 | 4 | DIS | JSC Kazakhtelecom, Direction of Information System | ASSIGNED PA | Aug 10, 2012 | abuse@ via KZ-KAZAKTELECOM-20030918 |
| └ 82.200.207.32/30 | 4 | RGUMINISTERSTVOFINANSOVRK | unknown | ASSIGNED PA | Feb 27, 2026 | abuse@ via KZ-KAZAKTELECOM-20030918 |
| └ 82.200.207.36/30 | 4 | BOGATYRSOSH | Maisk | ASSIGNED PA | Jul 11, 2024 | abuse@ via KZ-KAZAKTELECOM-20030918 |
| └ 82.200.207.40/30 | 4 | AOPAVRECHP | AOPAVLODARSKIYRECHNOIPORT | ASSIGNED PA | Sep 28, 2012 | abuse@ via KZ-KAZAKTELECOM-20030918 |
| └ 82.200.207.44/30 | 4 | Otdpred | AKTOGAI | ASSIGNED PA | Apr 19, 2023 | abuse@ via KZ-KAZAKTELECOM-20030918 |
| └ 82.200.207.48/30 | 4 | GUZANSOCPRPAV | Pavlodar | ASSIGNED PA | Dec 31, 2025 | abuse@ via KZ-KAZAKTELECOM-20030918 |
| └ 82.200.207.52/30 | 4 | MIKRK_ | unknown | ASSIGNED PA | Nov 9, 2018 | abuse@ via KZ-KAZAKTELECOM-20030918 |
| └ 82.200.207.56/30 | 4 | TOOVIAMEDIS | unknown | ASSIGNED PA | Mar 20, 2026 | abuse@ via KZ-KAZAKTELECOM-20030918 |
| └ 82.200.207.60/30 | 4 | GYORSEKSHERBRAIONA | PAVLODAR | ASSIGNED PA | Sep 9, 2022 | abuse@ via KZ-KAZAKTELECOM-20030918 |
| └ 82.200.207.64/27 | 32 | MTNMC_ | ASSIGNED PA | Jun 2, 2021 | abuse@ via KZ-KAZAKTELECOM-20030918 | |
| └ 82.200.207.96/28 | 16 | IP_ | LLC ITSHEFF.KZ | ASSIGNED PA | Apr 23, 2021 | abuse@ via KZ-KAZAKTELECOM-20030918 |
| └ 82.200.207.112/29 | 8 | IP_ | LLC «nbi» | ASSIGNED PA | Oct 16, 2020 | abuse@ via KZ-KAZAKTELECOM-20030918 |
| └ 82.200.207.128/27 | 32 | PAVLODARENERGO | PAVLODARENERGO | ASSIGNED PA | Aug 24, 2015 | abuse@ via KZ-KAZAKTELECOM-20030918 |
| └ 82.200.207.160/28 | 16 | DIS | Ilya Chernushenko | ASSIGNED PA | Aug 21, 2017 | abuse@ via KZ-KAZAKTELECOM-20030918 |
| └ 82.200.207.176/28 | 16 | DIS | Kirill Rul | ASSIGNED PA | Aug 21, 2017 | abuse@ via KZ-KAZAKTELECOM-20030918 |
| └ 82.200.207.192/30 | 4 | KGUSOSH12 | EKIBASTUZ | ASSIGNED PA | Feb 24, 2025 | abuse@ via KZ-KAZAKTELECOM-20030918 |
| └ 82.200.207.196/30 | 4 | TOOUPNKPV | PAVLODAR | ASSIGNED PA | Nov 30, 2017 | abuse@ via KZ-KAZAKTELECOM-20030918 |
| └ 82.200.207.200/29 | 8 | TOORUBIKOM2 | Pavlodar | ASSIGNED PA | Apr 24, 2025 | abuse@ via KZ-KAZAKTELECOM-20030918 |
| └ 82.200.207.208/30 | 4 | Speed_ | Pavlodar | ASSIGNED PA | Sep 22, 2020 | abuse@ via KZ-KAZAKTELECOM-20030918 |
| └ 82.200.207.212/30 | 4 | RGUMINISTERSTVOFINANSOVRK | unknown | ASSIGNED PA | Feb 27, 2026 | abuse@ via KZ-KAZAKTELECOM-20030918 |
| └ 82.200.207.216/29 | 8 | DIS | Pavel Ogiy | ASSIGNED PA | Feb 8, 2013 | abuse@ via KZ-KAZAKTELECOM-20030918 |
| └ 82.200.207.224/30 | 4 | DIS | Pavlodar | ASSIGNED PA | Sep 8, 2023 | abuse@ via KZ-KAZAKTELECOM-20030918 |
| └ 82.200.207.228/30 | 4 | DIS | SC Kazakhtelecom, Information Technology Division | ASSIGNED PA | Apr 30, 2025 | abuse@ via KZ-KAZAKTELECOM-20030918 |
| └ 82.200.207.236/30 | 4 | GUOTDELZANZTOSTIPAVL | Pavlodar | ASSIGNED PA | Dec 30, 2025 | abuse@ via KZ-KAZAKTELECOM-20030918 |
| └ 82.200.207.240/29 | 8 | SMARTNET | SMARTNET | ASSIGNED PA | Feb 11, 2013 | abuse@ via KZ-KAZAKTELECOM-20030918 |
| └ 82.200.207.248/30 | 4 | RGUMINISTERSTVOFINANSOVRK | unknown | ASSIGNED PA | Mar 2, 2026 | abuse@ via KZ-KAZAKTELECOM-20030918 |
| └ 82.200.207.252/30 | 4 | RGUMINISTERSTVOFINANSOVRK | unknown | ASSIGNED PA | Mar 2, 2026 | 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 | 212 | 83% | 32 | |
| Residential | 44 | 17% | 3 |
Network & registry
Announced by
Covering announcement 82.200.204.0/22
- Prefix
- 82.200.204.0/22
- Announced by
- AS9198 JSC Kazakhtelecom
- Type
- Residential
- Proxy exits
- 9
- 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.204.0/22
Routing history
- Pattern
- Stable
- First seen
- Aug 2005
- Current origin since
- Aug 2005 · 21 yr
- Origin networks
- 1
RPKI
Route origin authorizations
| ROA prefix | ASN | Max len | Anchor | Verdict |
|---|---|---|---|---|
| 82.200.204.0/22 | AS9198 | /22 | RIPE | RPKI valid |
| 82.200.128.0/17 | AS9198 | /24 | RIPE | RPKI valid |
IRR
Route objects on 82.200.204.0/22
| Origin | Registry | Description | Maintainer | Modified |
|---|---|---|---|---|
| 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