Data as of Nov 7, 2026
95.57.156.0/23
63 residential-proxy exits · 30 daysJSC Kazakhtelecom
Residential-proxy exits
Proxy exits
63
12% of its addresses · 30 days
Always-on exits
1
1.6% of its exits
Spread
2 of 2
/24s with at least one exit
Providers
73
selling exits here
Oct 8, 2026 – Nov 6, 2026
Exits seen per day
3.4K observations
- Residential
- Business
/24s with the most always-on exits
| /24 | Always-on exits | Proxy exits | |
|---|---|---|---|
| 95.57.156.0/24 | 1 | 59 | |
| 95.57.157.0/24 | 0 | 4 |
Proxy providers listing exits
- 2Captcha
- 711Proxy
- 911Proxy
- Ake.net
- AnyIP
- B2Proxy
- BartProxies
- BestProxy
- BirdProxies
- BlurPath
- BottingTools
- ByteProxies
- Byteful
- CatProxies
- CliProxy
- DataImpulse
- Decodo
- EZProxies
- EnigmaProxy
- Evomi
- FastProxy
- FlashProxy
- GSocks
- Geonix
- Geonode
- GloryCloud
- GonzoProxy
- HideProxy
- IPFly
- IPPeak
- IPRoyal
- Infatica
- InfiniteProxies
- KindProxy
- Kookey
- LemonBright
- LemonLabs
- LemonPrime
- LudaxProxy
- MangoProxy
- MoMoProxy
- NSocks
- NextProxy
- NodeMaven
- NodeProxy
- NovProxy
- NovaProxy
- Novada
- ProxiesVision
- Proxio
- Proxiware
- Proxmint
- Proxy-Seller
- Proxy4U
- ProxyEmpire
- ProxyGeo
- ProxyRack
- ProxyWing
- Proxyma
- PuraRoute
- Q2IP
- RainProxy
- RapidProxy
- Shifter
- Smartproxy
- StrikeProxy
- SwiftProxy
- Thordata
- ThunderProxy
- VantageProxies
- VibeProxies
- 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,678 895 always on | JSC Kazakhtelecom |
More specific
Announcements inside
| Prefix | Origin | Type | Proxy exits | Holder | RPKI |
|---|---|---|---|---|---|
| 95.57.156.0/24 since Feb 2026 | AS9198 | Residential | 59 1 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.57.157.0/30 | 4 | MIKRK_ | unknown | ASSIGNED PA | Jun 10, 2026 | abuse@ via KZ-KAZAKTELECOM-20080923 |
| └ 95.57.157.4/30 | 4 | MIKRK_ | unknown | ASSIGNED PA | Jun 11, 2026 | abuse@ via KZ-KAZAKTELECOM-20080923 |
| └ 95.57.157.8/30 | 4 | MIKRK_ | unknown | ASSIGNED PA | Jun 11, 2026 | abuse@ via KZ-KAZAKTELECOM-20080923 |
| └ 95.57.157.12/30 | 4 | MIKRK_ | unknown | ASSIGNED PA | Jun 11, 2026 | abuse@ via KZ-KAZAKTELECOM-20080923 |
| └ 95.57.157.16/30 | 4 | MIKRK_ | unknown | ASSIGNED PA | Jun 11, 2026 | abuse@ via KZ-KAZAKTELECOM-20080923 |
| └ 95.57.157.20/30 | 4 | MIKRK_ | unknown | ASSIGNED PA | Jun 11, 2026 | abuse@ via KZ-KAZAKTELECOM-20080923 |
| └ 95.57.157.24/30 | 4 | MIKRK_ | unknown | ASSIGNED PA | Jun 11, 2026 | abuse@ via KZ-KAZAKTELECOM-20080923 |
| └ 95.57.157.28/30 | 4 | MIKRK_ | unknown | ASSIGNED PA | Jun 11, 2026 | abuse@ via KZ-KAZAKTELECOM-20080923 |
| └ 95.57.157.32/30 | 4 | MIKRK_ | unknown | ASSIGNED PA | Jun 11, 2026 | abuse@ via KZ-KAZAKTELECOM-20080923 |
| └ 95.57.157.36/30 | 4 | MIKRK_ | unknown | ASSIGNED PA | Jun 11, 2026 | abuse@ via KZ-KAZAKTELECOM-20080923 |
| └ 95.57.157.40/30 | 4 | KOST_ | unknown | ASSIGNED PA | Jun 12, 2026 | abuse@ via KZ-KAZAKTELECOM-20080923 |
| └ 95.57.157.44/30 | 4 | TOO_ | unknown | ASSIGNED PA | Jun 26, 2026 | abuse@ via KZ-KAZAKTELECOM-20080923 |
| └ 95.57.157.48/30 | 4 | MIKRK_ | unknown | ASSIGNED PA | Aug 4, 2026 | abuse@ via KZ-KAZAKTELECOM-20080923 |
| └ 95.57.157.52/30 | 4 | MIKRK_ | unknown | ASSIGNED PA | Aug 4, 2026 | abuse@ via KZ-KAZAKTELECOM-20080923 |
| └ 95.57.157.56/30 | 4 | MIKRK_ | unknown | ASSIGNED PA | Aug 4, 2026 | abuse@ via KZ-KAZAKTELECOM-20080923 |
| └ 95.57.157.60/30 | 4 | MIKRK_ | unknown | ASSIGNED PA | Aug 4, 2026 | abuse@ via KZ-KAZAKTELECOM-20080923 |
| └ 95.57.157.64/30 | 4 | MIKRK_ | unknown | ASSIGNED PA | Aug 4, 2026 | abuse@ via KZ-KAZAKTELECOM-20080923 |
| └ 95.57.157.68/30 | 4 | MIKRK_ | unknown | ASSIGNED PA | Aug 4, 2026 | abuse@ via KZ-KAZAKTELECOM-20080923 |
| └ 95.57.157.72/30 | 4 | MIKRK_ | unknown | ASSIGNED PA | Aug 4, 2026 | abuse@ via KZ-KAZAKTELECOM-20080923 |
| └ 95.57.157.76/30 | 4 | MIKRK_ | unknown | ASSIGNED PA | Aug 4, 2026 | abuse@ via KZ-KAZAKTELECOM-20080923 |
| └ 95.57.157.80/30 | 4 | MIKRK_ | unknown | ASSIGNED PA | Aug 4, 2026 | abuse@ via KZ-KAZAKTELECOM-20080923 |
| └ 95.57.157.84/30 | 4 | MIKRK_ | unknown | ASSIGNED PA | Aug 4, 2026 | abuse@ via KZ-KAZAKTELECOM-20080923 |
| └ 95.57.157.88/30 | 4 | MIKRK_ | unknown | ASSIGNED PA | Aug 4, 2026 | abuse@ via KZ-KAZAKTELECOM-20080923 |
| └ 95.57.157.92/30 | 4 | MIKRK_ | unknown | ASSIGNED PA | Aug 4, 2026 | abuse@ via KZ-KAZAKTELECOM-20080923 |
| └ 95.57.157.96/30 | 4 | MIKRK_ | unknown | ASSIGNED PA | Aug 4, 2026 | abuse@ via KZ-KAZAKTELECOM-20080923 |
| └ 95.57.157.100/30 | 4 | MIKRK_ | unknown | ASSIGNED PA | Aug 4, 2026 | abuse@ via KZ-KAZAKTELECOM-20080923 |
| └ 95.57.157.104/30 | 4 | MIKRK_ | unknown | ASSIGNED PA | Aug 4, 2026 | abuse@ via KZ-KAZAKTELECOM-20080923 |
| └ 95.57.157.108/30 | 4 | MIKRK_ | unknown | ASSIGNED PA | Aug 4, 2026 | abuse@ via KZ-KAZAKTELECOM-20080923 |
| └ 95.57.157.112/30 | 4 | MIKRK_ | unknown | ASSIGNED PA | Aug 4, 2026 | abuse@ via KZ-KAZAKTELECOM-20080923 |
| └ 95.57.157.116/30 | 4 | MIKRK_ | unknown | ASSIGNED PA | Aug 4, 2026 | abuse@ via KZ-KAZAKTELECOM-20080923 |
| └ 95.57.157.120/30 | 4 | MIKRK_ | unknown | ASSIGNED PA | Aug 4, 2026 | abuse@ via KZ-KAZAKTELECOM-20080923 |
| └ 95.57.157.124/30 | 4 | MIKRK_ | unknown | ASSIGNED PA | Aug 4, 2026 | abuse@ via KZ-KAZAKTELECOM-20080923 |
| └ 95.57.157.128/27 | 32 | KIA_ | RC Kostanai | ASSIGNED PA | Sep 27, 2025 | abuse@ via KZ-KAZAKTELECOM-20080923 |
| └ 95.57.157.160/29 | 8 | KZI | unknown | ASSIGNED PA | Aug 18, 2026 | abuse@ via KZ-KAZAKTELECOM-20080923 |
| └ 95.57.157.176/29 | 8 | KOST_ | Qostanai | ASSIGNED PA | Jan 10, 2025 | abuse@ via KZ-KAZAKTELECOM-20080923 |
| └ 95.57.157.184/29 | 8 | PRAVITELSTVO_ | Qostanai | ASSIGNED PA | Mar 6, 2025 | abuse@ via KZ-KAZAKTELECOM-20080923 |
| └ 95.57.157.192/30 | 4 | UPRAVLENIE_ | Qostanai | ASSIGNED PA | Jan 14, 2026 | abuse@ via KZ-KAZAKTELECOM-20080923 |
| └ 95.57.157.196/30 | 4 | GIMNAZIA_ | unknown | ASSIGNED PA | Jul 16, 2026 | abuse@ via KZ-KAZAKTELECOM-20080923 |
| └ 95.57.157.200/30 | 4 | KOST_ | unknown | ASSIGNED PA | Jun 10, 2026 | abuse@ via KZ-KAZAKTELECOM-20080923 |
| └ 95.57.157.204/30 | 4 | SHKOLA_ | Qostanai | ASSIGNED PA | Dec 30, 2024 | abuse@ via KZ-KAZAKTELECOM-20080923 |
| └ 95.57.157.208/30 | 4 | OTDEL_ | unknown | ASSIGNED PA | Feb 17, 2026 | abuse@ via KZ-KAZAKTELECOM-20080923 |
| └ 95.57.157.212/30 | 4 | RUDN_ | Rudnyi | ASSIGNED PA | Dec 30, 2024 | abuse@ via KZ-KAZAKTELECOM-20080923 |
| └ 95.57.157.216/30 | 4 | DEP_ | Qostanai | ASSIGNED PA | Dec 30, 2024 | abuse@ via KZ-KAZAKTELECOM-20080923 |
| └ 95.57.157.220/30 | 4 | DEP_ | Qostanai | ASSIGNED PA | Dec 30, 2024 | abuse@ via KZ-KAZAKTELECOM-20080923 |
| └ 95.57.157.224/30 | 4 | KOLLEDZH_ | Qostanai | ASSIGNED PA | Dec 31, 2024 | abuse@ via KZ-KAZAKTELECOM-20080923 |
| └ 95.57.157.228/30 | 4 | OTD_ | Qostanai | ASSIGNED PA | Jan 5, 2025 | abuse@ via KZ-KAZAKTELECOM-20080923 |
| └ 95.57.157.232/30 | 4 | GIMNAZIA_ | unknown | ASSIGNED PA | Jul 16, 2026 | abuse@ via KZ-KAZAKTELECOM-20080923 |
| └ 95.57.157.236/30 | 4 | LIS_ | Lisakovsk | ASSIGNED PA | Jan 14, 2025 | abuse@ via KZ-KAZAKTELECOM-20080923 |
| └ 95.57.157.240/30 | 4 | OTD_ | Lisakovsk | ASSIGNED PA | Jan 13, 2025 | abuse@ via KZ-KAZAKTELECOM-20080923 |
| └ 95.57.157.244/30 | 4 | SRED_ | Qostanai | ASSIGNED PA | Dec 31, 2024 | abuse@ via KZ-KAZAKTELECOM-20080923 |
| └ 95.57.157.248/30 | 4 | GKH_ | Qostanai | ASSIGNED PA | Dec 31, 2024 | abuse@ via KZ-KAZAKTELECOM-20080923 |
| └ 95.57.157.252/30 | 4 | NCNE | Kostanai. str.Chekhova 105A | ASSIGNED PA | Dec 30, 2024 | 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.
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 | |
|---|---|---|---|---|
| Residential | 264 | 52% | 2 | |
| Business | 248 | 48% | 52 |
Network & registry
Announced by
Covering announcement 95.57.128.0/19
- Prefix
- 95.57.128.0/19
- Announced by
- AS9198 JSC Kazakhtelecom
- Type
- Residential
- Proxy exits
- 1,991
- Always-on exits
- 16
- 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.57.128.0/19
Routing history
- Pattern
- Stable
- First seen
- Mar 2009
- Current origin since
- Oct 2016 · 10 yr
- Origin networks
- 1
RPKI
Route origin authorizations
| ROA prefix | ASN | Max len | Anchor | Verdict |
|---|---|---|---|---|
| 95.57.128.0/19 | AS9198 | /24 | RIPE | RPKI valid |
| 95.56.0.0/14 | AS9198 | /24 | RIPE | RPKI valid |
IRR
Route objects on 95.57.128.0/19
| Origin | Registry | Description | Maintainer | Modified |
|---|---|---|---|---|
| AS9198 | RIPE | Kazakhtelecom Data Network Administration | KNIC-MNT | Mar 6, 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