Data as of Nov 3, 2026
2.134.13.0/24
6 residential-proxy exits · 30 daysJSC Kazakhtelecom
Residential-proxy exits
Proxy exits
6
2.3% of its addresses · 30 days
Providers
38
selling exits here
Oct 4, 2026 – Nov 2, 2026
Exits seen per day
598 observations
Proxy providers listing exits
- 2Captcha
- BirdProxies
- BottingTools
- ByteProxies
- Byteful
- CliProxy
- Datarama
- EnigmaProxy
- Evomi
- FlashProxy
- GSocks
- Geonix
- GonzoProxy
- IPOasis
- IPPeak
- Infatica
- InfiniteProxies
- LemonBright
- LemonLabs
- MangoProxy
- NSocks
- NodeProxy
- NovaProxy
- Novada
- Proxy-Seller
- ProxyEmpire
- ProxyGeo
- ProxyWing
- Proxyma
- RainProxy
- Shifter
- Smartproxy
- Thordata
- ThunderProxy
- VantageProxies
- VibeProxies
- VitalExclusive
- VitalProxy
Announcements
Less specific
Covering announcements
| Prefix | Origin | Type | Proxy exits | Holder | RPKI |
|---|---|---|---|---|---|
| 2.132.0.0/14 since Jan 2011 | AS9198 | Residential | 63,596 2,370 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 |
|---|---|---|---|---|---|---|
| 2.132.0.0/14 | 262,144 | KZ-KAZAKTELECOM-20101223 | JSC Kazakhtelecom (ORG-KDNA1-RIPE) · KZ | ALLOCATED PA | Dec 23, 2010 | [email protected] |
| └ 2.134.13.0/30 | 4 | NCERK | Zhelezinsky | ASSIGNED PA | Feb 28, 2025 | [email protected] via KZ-KAZAKTELECOM-20101223 |
| └ 2.134.13.4/30 | 4 | GUROZSOSH | unknown | ASSIGNED PA | Mar 13, 2026 | [email protected] via KZ-KAZAKTELECOM-20101223 |
| └ 2.134.13.8/30 | 4 | GUOTDELOBRAZOVANIYA | Bayanaulskiy Rayon | ASSIGNED PA | Aug 14, 2025 | [email protected] via KZ-KAZAKTELECOM-20101223 |
| └ 2.134.13.16/30 | 4 | KGUKOMSERVIC | PAVLODAR | ASSIGNED PA | Mar 4, 2025 | [email protected] via KZ-KAZAKTELECOM-20101223 |
| └ 2.134.13.24/30 | 4 | ABAISOSH | Maisk | ASSIGNED PA | Mar 28, 2025 | [email protected] via KZ-KAZAKTELECOM-20101223 |
| └ 2.134.13.28/30 | 4 | OBLREBLCENTR | Pavlodar | ASSIGNED PA | Mar 4, 2025 | [email protected] via KZ-KAZAKTELECOM-20101223 |
| └ 2.134.13.40/30 | 4 | SHKOLA1TER | PAVLODAR | ASSIGNED PA | Mar 5, 2025 | [email protected] via KZ-KAZAKTELECOM-20101223 |
| └ 2.134.13.44/30 | 4 | GUSOSH4 | BAYANAUL | ASSIGNED PA | Mar 17, 2025 | [email protected] via KZ-KAZAKTELECOM-20101223 |
| └ 2.134.13.48/30 | 4 | SSHAINAKOL | AKSU | ASSIGNED PA | Jun 20, 2025 | [email protected] via KZ-KAZAKTELECOM-20101223 |
| └ 2.134.13.52/30 | 4 | GUSOSH2 | Pavlodar | ASSIGNED PA | Mar 6, 2025 | [email protected] via KZ-KAZAKTELECOM-20101223 |
| └ 2.134.13.56/30 | 4 | Pravitgrazhdan | unknown | ASSIGNED PA | Jun 2, 2026 | [email protected] via KZ-KAZAKTELECOM-20101223 |
| └ 2.134.13.60/30 | 4 | SOSH14 | Pavlodar | ASSIGNED PA | Mar 6, 2025 | [email protected] via KZ-KAZAKTELECOM-20101223 |
| └ 2.134.13.64/27 | 32 | GUTCIT | unknown | ASSIGNED PA | Mar 3, 2026 | [email protected] via KZ-KAZAKTELECOM-20101223 |
| └ 2.134.13.96/27 | 32 | IP_DIGITAL_ADEPT | unknown | ASSIGNED PA | Apr 1, 2026 | [email protected] via KZ-KAZAKTELECOM-20101223 |
| └ 2.134.13.128/30 | 4 | MIKRK_GCHP | unknown | ASSIGNED PA | Jun 22, 2026 | [email protected] via KZ-KAZAKTELECOM-20101223 |
| └ 2.134.13.132/30 | 4 | MIKRK_GCHP | unknown | ASSIGNED PA | Jun 22, 2026 | [email protected] via KZ-KAZAKTELECOM-20101223 |
| └ 2.134.13.136/30 | 4 | MIKRK_GCHP | unknown | ASSIGNED PA | Jun 22, 2026 | [email protected] via KZ-KAZAKTELECOM-20101223 |
| └ 2.134.13.140/30 | 4 | MIKRK_GCHP | unknown | ASSIGNED PA | Jun 22, 2026 | [email protected] via KZ-KAZAKTELECOM-20101223 |
| └ 2.134.13.144/30 | 4 | MIKRK_GCHP | unknown | ASSIGNED PA | Jun 22, 2026 | [email protected] via KZ-KAZAKTELECOM-20101223 |
| └ 2.134.13.148/30 | 4 | MIKRK_GCHP | unknown | ASSIGNED PA | Jun 22, 2026 | [email protected] via KZ-KAZAKTELECOM-20101223 |
| └ 2.134.13.152/30 | 4 | MIKRK_GCHP | unknown | ASSIGNED PA | Jun 22, 2026 | [email protected] via KZ-KAZAKTELECOM-20101223 |
| └ 2.134.13.156/30 | 4 | MIKRK_GCHP | unknown | ASSIGNED PA | Jun 22, 2026 | [email protected] via KZ-KAZAKTELECOM-20101223 |
| └ 2.134.13.160/30 | 4 | MIKRK_GCHP | unknown | ASSIGNED PA | Jun 22, 2026 | [email protected] via KZ-KAZAKTELECOM-20101223 |
| └ 2.134.13.164/30 | 4 | MIKRK_GCHP | unknown | ASSIGNED PA | Jun 22, 2026 | [email protected] via KZ-KAZAKTELECOM-20101223 |
| └ 2.134.13.168/30 | 4 | MIKRK_GCHP | unknown | ASSIGNED PA | Jun 22, 2026 | [email protected] via KZ-KAZAKTELECOM-20101223 |
| └ 2.134.13.172/30 | 4 | MIKRK_GCHP | unknown | ASSIGNED PA | Jun 22, 2026 | [email protected] via KZ-KAZAKTELECOM-20101223 |
| └ 2.134.13.176/30 | 4 | MIKRK_GCHP | unknown | ASSIGNED PA | Jun 22, 2026 | [email protected] via KZ-KAZAKTELECOM-20101223 |
| └ 2.134.13.180/30 | 4 | MIKRK_GCHP | unknown | ASSIGNED PA | Jun 22, 2026 | [email protected] via KZ-KAZAKTELECOM-20101223 |
| └ 2.134.13.184/30 | 4 | MIKRK_GCHP | unknown | ASSIGNED PA | Jun 16, 2026 | [email protected] via KZ-KAZAKTELECOM-20101223 |
| └ 2.134.13.188/30 | 4 | MIKRK_GCHP | unknown | ASSIGNED PA | Jun 16, 2026 | [email protected] via KZ-KAZAKTELECOM-20101223 |
| └ 2.134.13.192/30 | 4 | MIKRK_GCHP | unknown | ASSIGNED PA | Jun 16, 2026 | [email protected] via KZ-KAZAKTELECOM-20101223 |
| └ 2.134.13.196/30 | 4 | MIKRK_GCHP | unknown | ASSIGNED PA | Jun 16, 2026 | [email protected] via KZ-KAZAKTELECOM-20101223 |
| └ 2.134.13.200/30 | 4 | MIKRK_GCHP | unknown | ASSIGNED PA | Jun 16, 2026 | [email protected] via KZ-KAZAKTELECOM-20101223 |
| └ 2.134.13.204/30 | 4 | MIKRK_GCHP | unknown | ASSIGNED PA | Jun 16, 2026 | [email protected] via KZ-KAZAKTELECOM-20101223 |
| └ 2.134.13.208/30 | 4 | MIKRK_GCHP | unknown | ASSIGNED PA | Jun 16, 2026 | [email protected] via KZ-KAZAKTELECOM-20101223 |
| └ 2.134.13.212/30 | 4 | MIKRK_GCHP | unknown | ASSIGNED PA | Jun 16, 2026 | [email protected] via KZ-KAZAKTELECOM-20101223 |
| └ 2.134.13.216/30 | 4 | MIKRK_GCHP | unknown | ASSIGNED PA | Jun 22, 2026 | [email protected] via KZ-KAZAKTELECOM-20101223 |
| └ 2.134.13.220/30 | 4 | MIKRK_GCHP | unknown | ASSIGNED PA | Jun 22, 2026 | [email protected] via KZ-KAZAKTELECOM-20101223 |
| └ 2.134.13.224/30 | 4 | MIKRK_GCHP | unknown | ASSIGNED PA | Jun 22, 2026 | [email protected] via KZ-KAZAKTELECOM-20101223 |
| └ 2.134.13.228/30 | 4 | MIKRK_GCHP | unknown | ASSIGNED PA | Jun 22, 2026 | [email protected] via KZ-KAZAKTELECOM-20101223 |
| └ 2.134.13.232/30 | 4 | MIKRK_GCHP | unknown | ASSIGNED PA | Jun 22, 2026 | [email protected] via KZ-KAZAKTELECOM-20101223 |
| └ 2.134.13.236/30 | 4 | MIKRK_GCHP | unknown | ASSIGNED PA | Jun 22, 2026 | [email protected] via KZ-KAZAKTELECOM-20101223 |
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 | 224 | 88% | 42 | |
| Residential | 32 | 13% | 4 |
Network & registry
Announced by
Covering announcement 2.134.0.0/18
- Prefix
- 2.134.0.0/18
- Announced by
- AS9198 JSC Kazakhtelecom
- Type
- Residential
- Proxy exits
- 4,011
- Always-on exits
- 29
- RPKI
- RPKI valid
- Netname
- KZ-KAZAKTELECOM-20101223
- 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
2.134.0.0/18
Routing history
- Pattern
- Stable
- First seen
- Jan 2011
- Current origin since
- Oct 2016 · 10 yr
- Origin networks
- 1
RPKI
Route origin authorizations
| ROA prefix | ASN | Max len | Anchor | Verdict |
|---|---|---|---|---|
| 2.134.0.0/18 | AS9198 | /24 | RIPE | RPKI valid |
| 2.132.0.0/14 | AS9198 | /24 | RIPE | RPKI valid |
IRR
Route objects on 2.134.0.0/18
| Origin | Registry | Description | Maintainer | Modified |
|---|---|---|---|---|
| AS9198 | RIPE | Kazakhtelecom Data Network Administration | KNIC-MNT | Dec 6, 2011 |
Whois
Registration for this announcement
- Range
- 2.132.0.0/14
- Netname
- KZ-KAZAKTELECOM-20101223
- Registrant
- JSC Kazakhtelecom
- Registrant country
- KZ
- Organization
- JSC Kazakhtelecom (ORG-KDNA1-RIPE)
- Org country
- KZ
- Type
- ALLOCATED PA
- Created
- Dec 23, 2010
- Updated
- Jun 23, 2016
- Maintainer
- RIPE-NCC-HM-MNT
- RIR
- RIPE NCC
- Country
- KZ
- Delegated
- Dec 23, 2010
- Status
- assigned
Report abuse
Abuse contact
- [email protected]
- Name
- Kazakhtelecom Network Information Center
- Handle
- KNIC1-RIPE