Data as of Nov 6, 2026
95.58.145.0/24
28 residential-proxy exits · 30 daysJSC Kazakhtelecom
Residential-proxy exits
Proxy exits
28
11% of its addresses · 30 days
Always-on exits
1
3.6% of its exits
Providers
43
selling exits here
Oct 7, 2026 – Nov 5, 2026
Exits seen per day
3.9K observations
Proxy providers listing exits
- 2Captcha
- 711Proxy
- AnyIP
- BartProxies
- BestProxy
- BirdProxies
- BottingTools
- ByteProxies
- Byteful
- CliProxy
- EnigmaProxy
- FastProxy
- FlashProxy
- GSocks
- Geonix
- GloryCloud
- GonzoProxy
- IPPeak
- Infatica
- Kookey
- LemonBright
- LemonLabs
- MangoProxy
- NSocks
- NiuProxy
- NodeProxy
- NovaProxy
- Novada
- Proxiware
- Proxy-Cheap
- Proxy-Seller
- ProxyEmpire
- ProxyRack
- ProxyWing
- Proxyma
- RainProxy
- Shifter
- Smartproxy
- Thordata
- ThunderProxy
- VantageProxies
- VitalExclusive
- VitalProxy
Announcements
Less specific
Covering announcements
| Prefix | Origin | Type | Proxy exits | Holder | RPKI |
|---|---|---|---|---|---|
| 95.56.0.0/14 since Oct 2008 | AS9198 | Residential | 56,752 883 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 |
|---|---|---|---|---|---|---|
| 95.56.0.0/14 | 262,144 | KZ-KAZAKTELECOM-20080923 | JSC Kazakhtelecom (ORG-KDNA1-RIPE) · KZ | ALLOCATED PA | Sep 23, 2008 | abuse@ |
| └ 95.58.145.0/30 | 4 | GU_ | RC Smirnovo | ASSIGNED PA | Jan 22, 2020 | abuse@ via KZ-KAZAKTELECOM-20080923 |
| └ 95.58.145.4/30 | 4 | GU_ | RC Smirnovo | ASSIGNED PA | Jan 22, 2020 | abuse@ via KZ-KAZAKTELECOM-20080923 |
| └ 95.58.145.8/30 | 4 | GU_ | RC Smirnovo | ASSIGNED PA | Jan 22, 2020 | abuse@ via KZ-KAZAKTELECOM-20080923 |
| └ 95.58.145.12/30 | 4 | GU_ | RC Yavlenka | ASSIGNED PA | Jan 22, 2020 | abuse@ via KZ-KAZAKTELECOM-20080923 |
| └ 95.58.145.16/30 | 4 | GU_ | RC Yavlenka | ASSIGNED PA | Jan 22, 2020 | abuse@ via KZ-KAZAKTELECOM-20080923 |
| └ 95.58.145.20/30 | 4 | GU_ | RC Presnovka | ASSIGNED PA | Jan 22, 2020 | abuse@ via KZ-KAZAKTELECOM-20080923 |
| └ 95.58.145.24/30 | 4 | GU_ | RC Presnovka | ASSIGNED PA | Jan 22, 2020 | abuse@ via KZ-KAZAKTELECOM-20080923 |
| └ 95.58.145.28/30 | 4 | GU_ | RC Mamlyutka | ASSIGNED PA | Jan 22, 2020 | abuse@ via KZ-KAZAKTELECOM-20080923 |
| └ 95.58.145.32/30 | 4 | GU_ | RC Mamlyutka | ASSIGNED PA | Jan 22, 2020 | abuse@ via KZ-KAZAKTELECOM-20080923 |
| └ 95.58.145.36/30 | 4 | GU_ | RC Mamlyutka | ASSIGNED PA | Jan 22, 2020 | abuse@ via KZ-KAZAKTELECOM-20080923 |
| └ 95.58.145.40/30 | 4 | GU_ | RC Mamlyutka | ASSIGNED PA | Jan 22, 2020 | abuse@ via KZ-KAZAKTELECOM-20080923 |
| └ 95.58.145.44/30 | 4 | TOO_ | RC Yavlenka | ASSIGNED PA | Jan 24, 2020 | abuse@ via KZ-KAZAKTELECOM-20080923 |
| └ 95.58.145.48/29 | 8 | RGU_ | Petropavlovsk | ASSIGNED PA | Jan 22, 2020 | abuse@ via KZ-KAZAKTELECOM-20080923 |
| └ 95.58.145.56/29 | 8 | TOO_ | Petropavlovsk | ASSIGNED PA | Jan 24, 2020 | abuse@ via KZ-KAZAKTELECOM-20080923 |
| └ 95.58.145.64/30 | 4 | TOO_ | RC Taiynsha | ASSIGNED PA | Nov 25, 2022 | abuse@ via KZ-KAZAKTELECOM-20080923 |
| └ 95.58.145.68/30 | 4 | AO_ | unknown | ASSIGNED PA | Mar 12, 2026 | abuse@ via KZ-KAZAKTELECOM-20080923 |
| └ 95.58.145.72/30 | 4 | GU_ | RC Saumalkol | ASSIGNED PA | Feb 17, 2020 | abuse@ via KZ-KAZAKTELECOM-20080923 |
| └ 95.58.145.76/30 | 4 | GU_ | RC Presnovka | ASSIGNED PA | Feb 19, 2020 | abuse@ via KZ-KAZAKTELECOM-20080923 |
| └ 95.58.145.80/30 | 4 | GU_ | RC Mamlyutka | ASSIGNED PA | Feb 26, 2020 | abuse@ via KZ-KAZAKTELECOM-20080923 |
| └ 95.58.145.84/30 | 4 | CENTR_ | Petropavlovsk | ASSIGNED PA | Jan 14, 2025 | abuse@ via KZ-KAZAKTELECOM-20080923 |
| └ 95.58.145.88/30 | 4 | TOO_ | unknown | ASSIGNED PA | Aug 13, 2026 | abuse@ via KZ-KAZAKTELECOM-20080923 |
| └ 95.58.145.92/30 | 4 | GU_ | unknown | ASSIGNED PA | Mar 18, 2026 | abuse@ via KZ-KAZAKTELECOM-20080923 |
| └ 95.58.145.96/30 | 4 | GU_ | RC Bulaevo | ASSIGNED PA | Feb 4, 2020 | abuse@ via KZ-KAZAKTELECOM-20080923 |
| └ 95.58.145.100/30 | 4 | GU_ | RC Bulaevo | ASSIGNED PA | Feb 4, 2020 | abuse@ via KZ-KAZAKTELECOM-20080923 |
| └ 95.58.145.104/30 | 4 | GU_ | RC Bulaevo | ASSIGNED PA | Feb 4, 2020 | abuse@ via KZ-KAZAKTELECOM-20080923 |
| └ 95.58.145.108/30 | 4 | GU_ | RC Bulaevo | ASSIGNED PA | Feb 4, 2020 | abuse@ via KZ-KAZAKTELECOM-20080923 |
| └ 95.58.145.112/30 | 4 | GU_ | unknown | ASSIGNED PA | May 6, 2026 | abuse@ via KZ-KAZAKTELECOM-20080923 |
| └ 95.58.145.116/30 | 4 | GU_ | Petropavlovsk | ASSIGNED PA | Jul 2, 2025 | abuse@ via KZ-KAZAKTELECOM-20080923 |
| └ 95.58.145.120/30 | 4 | GU_ | RC Sergeevka | ASSIGNED PA | Feb 3, 2020 | abuse@ via KZ-KAZAKTELECOM-20080923 |
| └ 95.58.145.124/30 | 4 | GU_ | RC Sergeevka | ASSIGNED PA | Feb 3, 2020 | abuse@ via KZ-KAZAKTELECOM-20080923 |
| └ 95.58.145.128/30 | 4 | KGU_ | Petropavlovsk | ASSIGNED PA | Mar 13, 2020 | abuse@ via KZ-KAZAKTELECOM-20080923 |
| └ 95.58.145.132/30 | 4 | GU_ | RC Saumalkol | ASSIGNED PA | Mar 16, 2020 | abuse@ via KZ-KAZAKTELECOM-20080923 |
| └ 95.58.145.136/30 | 4 | GU_ | unknown | ASSIGNED PA | Apr 9, 2026 | abuse@ via KZ-KAZAKTELECOM-20080923 |
| └ 95.58.145.140/30 | 4 | TOO_ | Petropavlovsk | ASSIGNED PA | Aug 25, 2025 | abuse@ via KZ-KAZAKTELECOM-20080923 |
| └ 95.58.145.144/30 | 4 | MAMLYUT_ | RC Mamlyutka | ASSIGNED PA | Mar 18, 2020 | abuse@ via KZ-KAZAKTELECOM-20080923 |
| └ 95.58.145.148/30 | 4 | APPARATAKIMA_ | RC Timiryazevo | ASSIGNED PA | May 20, 2020 | abuse@ via KZ-KAZAKTELECOM-20080923 |
| └ 95.58.145.152/30 | 4 | GU_ | RC Sergeevka | ASSIGNED PA | Jun 16, 2023 | abuse@ via KZ-KAZAKTELECOM-20080923 |
| └ 95.58.145.156/30 | 4 | AO_ | unknown | ASSIGNED PA | May 25, 2026 | abuse@ via KZ-KAZAKTELECOM-20080923 |
| └ 95.58.145.160/30 | 4 | GU_ | RC Bishkul | ASSIGNED PA | Apr 15, 2020 | abuse@ via KZ-KAZAKTELECOM-20080923 |
| └ 95.58.145.164/30 | 4 | GU_ | RC Bishkul | ASSIGNED PA | Apr 15, 2020 | abuse@ via KZ-KAZAKTELECOM-20080923 |
| └ 95.58.145.168/30 | 4 | GU_ | RC Bishkul | ASSIGNED PA | Apr 15, 2020 | abuse@ via KZ-KAZAKTELECOM-20080923 |
| └ 95.58.145.172/30 | 4 | TOO_ | Petropavlovsk | ASSIGNED PA | Apr 16, 2020 | abuse@ via KZ-KAZAKTELECOM-20080923 |
| └ 95.58.145.176/30 | 4 | TOO_ | unknown | ASSIGNED PA | Aug 25, 2026 | abuse@ via KZ-KAZAKTELECOM-20080923 |
| └ 95.58.145.180/30 | 4 | IP_ | RC Mamlyutka | ASSIGNED PA | Aug 28, 2025 | abuse@ via KZ-KAZAKTELECOM-20080923 |
| └ 95.58.145.184/30 | 4 | TOO_ | Petropavlovsk | ASSIGNED PA | Dec 5, 2022 | abuse@ via KZ-KAZAKTELECOM-20080923 |
| └ 95.58.145.188/30 | 4 | TOO_ | Petropavlovsk | ASSIGNED PA | Apr 24, 2020 | abuse@ via KZ-KAZAKTELECOM-20080923 |
| └ 95.58.145.192/30 | 4 | GU_ | RC Saumalkol | ASSIGNED PA | Mar 13, 2020 | abuse@ via KZ-KAZAKTELECOM-20080923 |
| └ 95.58.145.196/30 | 4 | AO_ | unknown | ASSIGNED PA | Mar 5, 2026 | abuse@ via KZ-KAZAKTELECOM-20080923 |
| └ 95.58.145.200/30 | 4 | KGU_ | unknown | ASSIGNED PA | Apr 14, 2026 | abuse@ via KZ-KAZAKTELECOM-20080923 |
| └ 95.58.145.204/30 | 4 | KGU_ | RC Kishkenekol | ASSIGNED PA | Jul 2, 2021 | abuse@ via KZ-KAZAKTELECOM-20080923 |
| └ 95.58.145.208/30 | 4 | CENTR_ | RC Timiryazevo | ASSIGNED PA | Oct 20, 2025 | abuse@ via KZ-KAZAKTELECOM-20080923 |
| └ 95.58.145.212/30 | 4 | KGU_ | RC Novoishimskoe | ASSIGNED PA | Oct 20, 2025 | abuse@ via KZ-KAZAKTELECOM-20080923 |
| └ 95.58.145.216/30 | 4 | TOO_ | RC Bulaevo | ASSIGNED PA | Mar 24, 2022 | abuse@ via KZ-KAZAKTELECOM-20080923 |
| └ 95.58.145.220/30 | 4 | KGU_ | RC Kishkenekol | ASSIGNED PA | Sep 1, 2022 | abuse@ via KZ-KAZAKTELECOM-20080923 |
| └ 95.58.145.224/30 | 4 | RGKP_ | Petropavlovsk | ASSIGNED PA | Dec 30, 2025 | abuse@ via KZ-KAZAKTELECOM-20080923 |
| └ 95.58.145.228/30 | 4 | GU_ | RC Smirnovo | ASSIGNED PA | Oct 13, 2023 | abuse@ via KZ-KAZAKTELECOM-20080923 |
| └ 95.58.145.232/30 | 4 | GU_ | RC Beskol | ASSIGNED PA | Aug 28, 2025 | abuse@ via KZ-KAZAKTELECOM-20080923 |
| └ 95.58.145.236/30 | 4 | GU_ | RC Novoishimskoe | ASSIGNED PA | Feb 27, 2020 | abuse@ via KZ-KAZAKTELECOM-20080923 |
| └ 95.58.145.240/30 | 4 | GU_ | RC Novoishimskoe | ASSIGNED PA | Feb 26, 2020 | abuse@ via KZ-KAZAKTELECOM-20080923 |
| └ 95.58.145.244/30 | 4 | GU_ | RC Novoishimskoe | ASSIGNED PA | Feb 26, 2020 | abuse@ via KZ-KAZAKTELECOM-20080923 |
| └ 95.58.145.248/30 | 4 | TOO_ | RC Mamlyutka | ASSIGNED PA | Apr 27, 2020 | abuse@ via KZ-KAZAKTELECOM-20080923 |
| └ 95.58.145.252/30 | 4 | GU-SKGU | Petropavlovsk | ASSIGNED PA | Feb 26, 2020 | abuse@ via KZ-KAZAKTELECOM-20080923 |
A contact marked “via” is the registry's: the record names none of its own, so the registry hands down its parent's.
Network & registry
Announced by
Covering announcement 95.58.128.0/19
- Prefix
- 95.58.128.0/19
- Announced by
- AS9198 JSC Kazakhtelecom
- Type
- Residential
- Proxy exits
- 1,726
- Always-on exits
- 54
- RPKI
- RPKI valid
- Netname
- KZ-KAZAKTELECOM-20080923
- 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
95.58.128.0/19
Routing history
- Pattern
- Stable
- First seen
- Apr 2009
- Current origin since
- Apr 2009 · 18 yr
- Origin networks
- 1
RPKI
Route origin authorizations
| ROA prefix | ASN | Max len | Anchor | Verdict |
|---|---|---|---|---|
| 95.58.128.0/19 | AS9198 | /24 | RIPE | RPKI valid |
| 95.56.0.0/14 | AS9198 | /24 | RIPE | RPKI valid |
IRR
Route objects on 95.58.128.0/19
| Origin | Registry | Description | Maintainer | Modified |
|---|---|---|---|---|
| AS9198 | RIPE | Kazakhtelecom Data Network Administration | KNIC-MNT | Apr 2, 2009 |
Whois
Registration for this announcement
- Range
- 95.
56. 0. 0/ 14 - Netname
- KZ-KAZAKTELECOM-20080923
- Registrant
- JSC Kazakhtelecom
- Registrant country
- KZ
- Organization
- JSC Kazakhtelecom (ORG-KDNA1-RIPE)
- Org country
- KZ
- Type
- ALLOCATED PA
- Created
- Sep 23, 2008
- Updated
- Jun 23, 2016
- Maintainer
- RIPE-NCC-HM-MNT
- RIR
- RIPE NCC
- Country
- KZ
- Delegated
- Sep 23, 2008
- Status
- assigned
Report abuse
Abuse contact
- abuse@
telecom. kz - Name
- Kazakhtelecom Network Information Center
- Handle
- KNIC1-RIPE