Data as of Nov 6, 2026
178.91.188.0/24
22 residential-proxy exits · 30 daysJSC Kazakhtelecom
Residential-proxy exits
Proxy exits
22
8.6% of its addresses · 30 days
Always-on exits
3
14% of its exits
Providers
63
selling exits here
Oct 7, 2026 – Nov 5, 2026
Exits seen per day
6.6K observations
Proxy providers listing exits
- 2Captcha
- 711Proxy
- Ake.net
- B2Proxy
- BartProxies
- BestProxy
- BirdProxies
- BlurPath
- BottingTools
- ByteProxies
- Byteful
- CatProxies
- CliProxy
- DataImpulse
- Decodo
- EZProxies
- EnigmaProxy
- Evomi
- FastProxy
- FlashProxy
- Geonode
- GloryCloud
- GonzoProxy
- HideProxy
- IPFly
- IPOasis
- IPPeak
- Infatica
- InfiniteProxies
- KindProxy
- Kookey
- LemonBright
- LudaxProxy
- MangoProxy
- MoMoProxy
- NSocks
- NextProxy
- NodeMaven
- NovaProxy
- Novada
- Oxylabs
- ProxiesVision
- Proxio
- Proxiware
- Proxmint
- Proxy-Seller
- Proxy4U
- ProxyEmpire
- ProxyGeo
- ProxyRack
- Proxyma
- PuraRoute
- Q2IP
- RainProxy
- RapidProxy
- RoamProxy
- Shifter
- Smartproxy
- StrikeProxy
- TrueProxies
- VibeProxies
- VitalExclusive
- VitalProxy
Announcements
Less specific
Covering announcements
| Prefix | Origin | Type | Proxy exits | Holder | RPKI |
|---|---|---|---|---|---|
| 178.88.0.0/14 since Dec 2009 | AS9198 | Residential | 63,811 2,049 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 |
|---|---|---|---|---|---|---|
| 178.88.0.0/14 | 262,144 | KZ-KAZAKTELECOM-20091126 | JSC Kazakhtelecom (ORG-KDNA1-RIPE) · KZ | ALLOCATED PA | Nov 26, 2009 | abuse@ |
| └ 178.91.188.0/30 | 4 | KGU_ | RC Saumalkol | ASSIGNED PA | Jan 4, 2024 | abuse@ via KZ-KAZAKTELECOM-20091126 |
| └ 178.91.188.4/30 | 4 | GU_ | RC Bulaevo | ASSIGNED PA | Jul 25, 2025 | abuse@ via KZ-KAZAKTELECOM-20091126 |
| └ 178.91.188.8/30 | 4 | AO_ | unknown | ASSIGNED PA | Apr 21, 2026 | abuse@ via KZ-KAZAKTELECOM-20091126 |
| └ 178.91.188.12/30 | 4 | ZHASTARLAN | Petropavlovsk | ASSIGNED PA | Nov 6, 2025 | abuse@ via KZ-KAZAKTELECOM-20091126 |
| └ 178.91.188.16/30 | 4 | ADGS_ | unknown | ASSIGNED PA | Jan 27, 2025 | abuse@ via KZ-KAZAKTELECOM-20091126 |
| └ 178.91.188.20/30 | 4 | SREDNAYA_ | Petropavlovsk | ASSIGNED PA | Jan 14, 2025 | abuse@ via KZ-KAZAKTELECOM-20091126 |
| └ 178.91.188.48/29 | 8 | TOO_ | Petropavlovsk | ASSIGNED PA | Nov 6, 2025 | abuse@ via KZ-KAZAKTELECOM-20091126 |
| └ 178.91.188.56/30 | 4 | TOO_ | unknown | ASSIGNED PA | Jul 28, 2026 | abuse@ via KZ-KAZAKTELECOM-20091126 |
| └ 178.91.188.60/30 | 4 | GU_ | RC Saumalkol | ASSIGNED PA | Jan 27, 2024 | abuse@ via KZ-KAZAKTELECOM-20091126 |
| └ 178.91.188.64/30 | 4 | AO_ | unknown | ASSIGNED PA | Apr 15, 2026 | abuse@ via KZ-KAZAKTELECOM-20091126 |
| └ 178.91.188.68/30 | 4 | RAIONNAYA_ | RC Novoishimskoe | ASSIGNED PA | Jan 24, 2024 | abuse@ via KZ-KAZAKTELECOM-20091126 |
| └ 178.91.188.72/30 | 4 | GU_ | RC Sergeevka | ASSIGNED PA | Jan 25, 2024 | abuse@ via KZ-KAZAKTELECOM-20091126 |
| └ 178.91.188.76/30 | 4 | GU_ | RC Sergeevka | ASSIGNED PA | Jan 25, 2024 | abuse@ via KZ-KAZAKTELECOM-20091126 |
| └ 178.91.188.80/30 | 4 | TOO_ | Petropavlovsk | ASSIGNED PA | Jun 20, 2024 | abuse@ via KZ-KAZAKTELECOM-20091126 |
| └ 178.91.188.84/30 | 4 | KGU_ | Toksan bi | ASSIGNED PA | Nov 18, 2025 | abuse@ via KZ-KAZAKTELECOM-20091126 |
| └ 178.91.188.88/30 | 4 | RGU_ | Petropavlovsk | ASSIGNED PA | Jan 25, 2024 | abuse@ via KZ-KAZAKTELECOM-20091126 |
| └ 178.91.188.92/30 | 4 | KGU_ | Chistopole | ASSIGNED PA | Nov 18, 2025 | abuse@ via KZ-KAZAKTELECOM-20091126 |
| └ 178.91.188.96/30 | 4 | GU_ | Uzunkol | ASSIGNED PA | Sep 11, 2024 | abuse@ via KZ-KAZAKTELECOM-20091126 |
| └ 178.91.188.100/30 | 4 | GU_ | Zhanazhol | ASSIGNED PA | Sep 11, 2024 | abuse@ via KZ-KAZAKTELECOM-20091126 |
| └ 178.91.188.104/30 | 4 | MTNMC_ | Petropavlovsk | ASSIGNED PA | Sep 12, 2024 | abuse@ via KZ-KAZAKTELECOM-20091126 |
| └ 178.91.188.108/30 | 4 | MTNMC_ | Petropavlovsk | ASSIGNED PA | Sep 12, 2024 | abuse@ via KZ-KAZAKTELECOM-20091126 |
| └ 178.91.188.112/30 | 4 | KYZYLJARSKAYA_ | Asanova | ASSIGNED PA | Nov 19, 2025 | abuse@ via KZ-KAZAKTELECOM-20091126 |
| └ 178.91.188.116/30 | 4 | KYZYLJARSKAYA_ | RC Bishkul | ASSIGNED PA | Dec 30, 2025 | abuse@ via KZ-KAZAKTELECOM-20091126 |
| └ 178.91.188.120/30 | 4 | TOO_ | RC Novoishimskoe | ASSIGNED PA | Dec 5, 2024 | abuse@ via KZ-KAZAKTELECOM-20091126 |
| └ 178.91.188.124/30 | 4 | TOO_ | Petropavlovsk | ASSIGNED PA | Dec 6, 2024 | abuse@ via KZ-KAZAKTELECOM-20091126 |
| └ 178.91.188.128/30 | 4 | KGP_ | RC Taiynsha | ASSIGNED PA | Dec 20, 2024 | abuse@ via KZ-KAZAKTELECOM-20091126 |
| └ 178.91.188.132/30 | 4 | KGU_ | RC Taiynsha | ASSIGNED PA | Dec 20, 2024 | abuse@ via KZ-KAZAKTELECOM-20091126 |
| └ 178.91.188.136/30 | 4 | AYRTAU_ | RC Saumalkol | ASSIGNED PA | Feb 3, 2025 | abuse@ via KZ-KAZAKTELECOM-20091126 |
| └ 178.91.188.140/30 | 4 | VETERINARNAYA_ | RC Taiynsha | ASSIGNED PA | Dec 24, 2024 | abuse@ via KZ-KAZAKTELECOM-20091126 |
| └ 178.91.188.144/30 | 4 | SHKOLA_ | Petropavlovsk | ASSIGNED PA | Jan 8, 2026 | abuse@ via KZ-KAZAKTELECOM-20091126 |
| └ 178.91.188.148/30 | 4 | PETROPAVLOVSK_ | Petropavlovsk | ASSIGNED PA | Jan 6, 2025 | abuse@ via KZ-KAZAKTELECOM-20091126 |
| └ 178.91.188.152/30 | 4 | OTDEL_ | Petropavlovsk | ASSIGNED PA | Jan 8, 2026 | abuse@ via KZ-KAZAKTELECOM-20091126 |
| └ 178.91.188.156/30 | 4 | GU_ | Petropavlovsk | ASSIGNED PA | Jan 16, 2025 | abuse@ via KZ-KAZAKTELECOM-20091126 |
| └ 178.91.188.160/30 | 4 | KGU_ | RC Taiynsha | ASSIGNED PA | Jan 17, 2025 | abuse@ via KZ-KAZAKTELECOM-20091126 |
| └ 178.91.188.164/30 | 4 | SHKOLA_ | Petropavlovsk | ASSIGNED PA | Jan 8, 2026 | abuse@ via KZ-KAZAKTELECOM-20091126 |
| └ 178.91.188.168/29 | 8 | OBLASTNOY_ | Petropavlovsk | ASSIGNED PA | Jan 17, 2025 | abuse@ via KZ-KAZAKTELECOM-20091126 |
| └ 178.91.188.176/30 | 4 | KGU_ | Petropavlovsk | ASSIGNED PA | Jan 8, 2026 | abuse@ via KZ-KAZAKTELECOM-20091126 |
| └ 178.91.188.180/30 | 4 | RAIONNAYA_ | RC Novoishimskoe | ASSIGNED PA | Jan 12, 2026 | abuse@ via KZ-KAZAKTELECOM-20091126 |
| └ 178.91.188.192/27 | 32 | TelService_ | unknown | ASSIGNED PA | Sep 11, 2026 | abuse@ via KZ-KAZAKTELECOM-20091126 |
| └ 178.91.188.224/27 | 32 | TelService_ | unknown | ASSIGNED PA | Sep 30, 2026 | abuse@ via KZ-KAZAKTELECOM-20091126 |
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 | 216 | 84% | 38 | |
| Residential | 40 | 16% | 3 |
Network & registry
Announced by
Covering announcement 178.91.160.0/19
- Prefix
- 178.91.160.0/19
- Announced by
- AS9198 JSC Kazakhtelecom
- Type
- Residential
- Proxy exits
- 2,241
- Always-on exits
- 36
- RPKI
- RPKI valid
- Netname
- KZ-KAZAKTELECOM-20091126
- 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
178.91.160.0/19
Routing history
- Pattern
- Stable
- First seen
- Dec 2009
- Current origin since
- Oct 2016 · 10 yr
- Origin networks
- 1
RPKI
Route origin authorizations
| ROA prefix | ASN | Max len | Anchor | Verdict |
|---|---|---|---|---|
| 178.91.160.0/19 | AS9198 | /24 | RIPE | RPKI valid |
| 178.88.0.0/14 | AS9198 | /24 | RIPE | RPKI valid |
IRR
Route objects on 178.91.160.0/19
| Origin | Registry | Description | Maintainer | Modified |
|---|---|---|---|---|
| AS9198 | RIPE | Kazakhtelecom Data Network Administration | KNIC-MNT | Jan 26, 2010 |
Whois
Registration for this announcement
- Range
- 178.
88. 0. 0/ 14 - Netname
- KZ-KAZAKTELECOM-20091126
- Registrant
- JSC Kazakhtelecom
- Registrant country
- KZ
- Organization
- JSC Kazakhtelecom (ORG-KDNA1-RIPE)
- Org country
- KZ
- Type
- ALLOCATED PA
- Created
- Nov 26, 2009
- Updated
- Jun 23, 2016
- Maintainer
- RIPE-NCC-HM-MNT
- RIR
- RIPE NCC
- Country
- KZ
- Delegated
- Nov 26, 2009
- Status
- assigned
Report abuse
Abuse contact
- abuse@
telecom. kz - Name
- Kazakhtelecom Network Information Center
- Handle
- KNIC1-RIPE