Data as of Nov 12, 2026
5.63.113.0/24
4 residential-proxy exits · 30 daysJSC Kazakhtelecom
Residential-proxy exits
Proxy exits
4
1.6% of its addresses · 30 days
Always-on exits
1
25% of its exits
Providers
33
selling exits here
Oct 13, 2026 – Nov 11, 2026
Exits seen per day
1.5K observations
Proxy providers listing exits
- 711Proxy
- 911Proxy
- 9Proxy
- BestProxy
- BirdProxies
- BottingTools
- ByteProxies
- Byteful
- Evomi
- FastProxy
- FlashProxy
- Geonode
- GonzoProxy
- IPROCKET_PREMIUM
- Infatica
- InfiniteProxies
- LUMIPROXY
- LemonBright
- MangoProxy
- NSocks
- NovaProxy
- Oxylabs
- Proxy-Seller
- ProxyEmpire
- ProxyRack
- Proxyma
- RainProxy
- Shifter
- Smartproxy
- Thordata
- ThunderProxy
- VantageProxies
- ZENPROXY_PREMIUM
Announcements
Less specific
Covering announcements
| Prefix | Origin | Type | Proxy exits | Holder | RPKI |
|---|---|---|---|---|---|
| 5.63.64.0/18 since Jun 2012 | AS9198 | Residential | 2,724 27 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 |
|---|---|---|---|---|---|---|
| 5.63.64.0/18 | 16,384 | KZ-KAZAKTELECOM-20120612 | JSC Kazakhtelecom (ORG-KDNA1-RIPE) · KZ | ALLOCATED PA | Jun 12, 2012 | abuse@ |
| └ 5.63.113.4/30 | 4 | TOONURMEDYA | TOONURMEDYA | ASSIGNED PA | Dec 22, 2014 | abuse@ via KZ-KAZAKTELECOM-20120612 |
| └ 5.63.113.12/30 | 4 | UPLAWYERSKZ | Astana | ASSIGNED PA | Nov 4, 2025 | abuse@ via KZ-KAZAKTELECOM-20120612 |
| └ 5.63.113.16/29 | 8 | TOO_ | Astana | ASSIGNED PA | Oct 22, 2022 | abuse@ via KZ-KAZAKTELECOM-20120612 |
| └ 5.63.113.24/30 | 4 | MEDLINECOMPANY | Astana | ASSIGNED PA | Mar 7, 2023 | abuse@ via KZ-KAZAKTELECOM-20120612 |
| └ 5.63.113.32/29 | 8 | TOONURSERVICENS | Astana | ASSIGNED PA | Sep 20, 2023 | abuse@ via KZ-KAZAKTELECOM-20120612 |
| └ 5.63.113.40/29 | 8 | TSENTRORGDORDVIZHAST | Astana | ASSIGNED PA | Dec 8, 2025 | abuse@ via KZ-KAZAKTELECOM-20120612 |
| └ 5.63.113.48/30 | 4 | SEYPHLOMBARD | Astana | ASSIGNED PA | Nov 11, 2025 | abuse@ via KZ-KAZAKTELECOM-20120612 |
| └ 5.63.113.52/30 | 4 | ASTANA_ | Astana | ASSIGNED PA | Jul 1, 2024 | abuse@ via KZ-KAZAKTELECOM-20120612 |
| └ 5.63.113.56/30 | 4 | AONIT | Astana | ASSIGNED PA | Aug 20, 2019 | abuse@ via KZ-KAZAKTELECOM-20120612 |
| └ 5.63.113.60/30 | 4 | IP_ | unknown | ASSIGNED PA | Jul 17, 2015 | abuse@ via KZ-KAZAKTELECOM-20120612 |
| └ 5.63.113.64/29 | 8 | TOOITGENERATION | TOOITGENERATION | ASSIGNED PA | Jan 9, 2015 | abuse@ via KZ-KAZAKTELECOM-20120612 |
| └ 5.63.113.72/30 | 4 | IP_ | unknown | ASSIGNED PA | Jan 9, 2015 | abuse@ via KZ-KAZAKTELECOM-20120612 |
| └ 5.63.113.76/30 | 4 | TOOAKBARYS | Astana | ASSIGNED PA | Nov 16, 2022 | abuse@ via KZ-KAZAKTELECOM-20120612 |
| └ 5.63.113.80/29 | 8 | IP_ | Ilya Kazakov | ASSIGNED PA | Mar 29, 2017 | abuse@ via KZ-KAZAKTELECOM-20120612 |
| └ 5.63.113.88/29 | 8 | TERALINETELECOM | Astana | ASSIGNED PA | Nov 19, 2025 | abuse@ via KZ-KAZAKTELECOM-20120612 |
| └ 5.63.113.96/28 | 16 | NISAST | ASTANA | ASSIGNED PA | Jul 26, 2024 | abuse@ via KZ-KAZAKTELECOM-20120612 |
| └ 5.63.113.128/30 | 4 | SHKOLA103 | g.Astana | ASSIGNED PA | Aug 27, 2024 | abuse@ via KZ-KAZAKTELECOM-20120612 |
| └ 5.63.113.132/30 | 4 | TOOGURACADEM | TOOGURACADEM | ASSIGNED PA | Jan 16, 2015 | abuse@ via KZ-KAZAKTELECOM-20120612 |
| └ 5.63.113.136/30 | 4 | TOO-OpenMediaGroup | Astana | ASSIGNED PA | Jun 3, 2024 | abuse@ via KZ-KAZAKTELECOM-20120612 |
| └ 5.63.113.140/30 | 4 | IP_ | unknown | ASSIGNED PA | Jan 19, 2015 | abuse@ via KZ-KAZAKTELECOM-20120612 |
| └ 5.63.113.144/30 | 4 | TOOCELINTR | TOOCELINTR | ASSIGNED PA | Jul 17, 2015 | abuse@ via KZ-KAZAKTELECOM-20120612 |
| └ 5.63.113.148/30 | 4 | PS8 | Astana | ASSIGNED PA | Mar 1, 2024 | abuse@ via KZ-KAZAKTELECOM-20120612 |
| └ 5.63.113.152/30 | 4 | IP_ | unknown | ASSIGNED PA | Jul 20, 2015 | abuse@ via KZ-KAZAKTELECOM-20120612 |
| └ 5.63.113.156/30 | 4 | TOONEVATOMKZ | Astana | ASSIGNED PA | Oct 11, 2023 | abuse@ via KZ-KAZAKTELECOM-20120612 |
| └ 5.63.113.160/28 | 16 | NISAST | ASTANA | ASSIGNED PA | Jul 29, 2024 | abuse@ via KZ-KAZAKTELECOM-20120612 |
| └ 5.63.113.176/30 | 4 | TOO_ | Astana | ASSIGNED PA | Nov 23, 2022 | abuse@ via KZ-KAZAKTELECOM-20120612 |
| └ 5.63.113.180/30 | 4 | GRAND_ | unknown | ASSIGNED PA | May 28, 2025 | abuse@ via KZ-KAZAKTELECOM-20120612 |
| └ 5.63.113.184/30 | 4 | AO_ | Astana | ASSIGNED PA | Jan 10, 2023 | abuse@ via KZ-KAZAKTELECOM-20120612 |
| └ 5.63.113.188/30 | 4 | VIDIVICI | Astana | ASSIGNED PA | Aug 13, 2024 | abuse@ via KZ-KAZAKTELECOM-20120612 |
| └ 5.63.113.192/28 | 16 | TOOTRISAD | TOOTRISAD | ASSIGNED PA | Dec 31, 2014 | abuse@ via KZ-KAZAKTELECOM-20120612 |
| └ 5.63.113.208/29 | 8 | IP_ | Co-location | ASSIGNED PA | Feb 20, 2024 | abuse@ via KZ-KAZAKTELECOM-20120612 |
| └ 5.63.113.216/29 | 8 | TOYOTATSUSHO | Nur-Sultan, E-1, str. 40 | ASSIGNED PA | Nov 20, 2020 | abuse@ via KZ-KAZAKTELECOM-20120612 |
| └ 5.63.113.224/30 | 4 | AITIES | Nur-Sultan, Kosmonavtov 62/a | ASSIGNED PA | Dec 31, 2020 | abuse@ via KZ-KAZAKTELECOM-20120612 |
| └ 5.63.113.228/30 | 4 | DENEVITA | Astana | ASSIGNED PA | Sep 25, 2025 | abuse@ via KZ-KAZAKTELECOM-20120612 |
| └ 5.63.113.232/30 | 4 | ALAMEDAPROPERTY | unknown | ASSIGNED PA | Jun 5, 2026 | abuse@ via KZ-KAZAKTELECOM-20120612 |
| └ 5.63.113.236/30 | 4 | ARGENTA | Astana | ASSIGNED PA | Nov 12, 2024 | abuse@ via KZ-KAZAKTELECOM-20120612 |
| └ 5.63.113.240/30 | 4 | HTEL | Astana, mas. VIP-Town, house 42 | ASSIGNED PA | Feb 21, 2025 | abuse@ via KZ-KAZAKTELECOM-20120612 |
| └ 5.63.113.244/30 | 4 | IP_ | Nur-Sultan | ASSIGNED PA | Sep 5, 2022 | abuse@ via KZ-KAZAKTELECOM-20120612 |
| └ 5.63.113.248/30 | 4 | GEM | unknown | ASSIGNED PA | Sep 25, 2019 | abuse@ via KZ-KAZAKTELECOM-20120612 |
| └ 5.63.113.252/30 | 4 | TEEZLOGISTICS | Astana | ASSIGNED PA | May 15, 2025 | abuse@ via KZ-KAZAKTELECOM-20120612 |
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 | 228 | 89% | 40 | |
| Residential | 28 | 11% | 4 |
Network & registry
Announced by
Covering announcement 5.63.112.0/20
- Prefix
- 5.63.112.0/20
- Announced by
- AS9198 JSC Kazakhtelecom
- Type
- Residential
- Proxy exits
- 602
- Always-on exits
- 9
- RPKI
- RPKI valid
- Netname
- KZ-KAZAKTELECOM-20120612
- 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
5.63.112.0/20
Routing history
- Pattern
- Stable
- First seen
- Jan 2014
- Current origin since
- Sep 2016 · 10 yr
- Origin networks
- 1
RPKI
Route origin authorizations
| ROA prefix | ASN | Max len | Anchor | Verdict |
|---|---|---|---|---|
| 5.63.112.0/20 | AS9198 | /20 | RIPE | RPKI valid |
| 5.63.64.0/18 | AS9198 | /18 | RIPE | Too specific |
Whois
Registration for this announcement
- Range
- 5.
63. 64. 0/ 18 - Netname
- KZ-KAZAKTELECOM-20120612
- Registrant
- JSC Kazakhtelecom
- Registrant country
- KZ
- Organization
- JSC Kazakhtelecom (ORG-KDNA1-RIPE)
- Org country
- KZ
- Type
- ALLOCATED PA
- Created
- Jun 12, 2012
- Updated
- Jun 23, 2016
- Maintainer
- RIPE-NCC-HM-MNT
- RIR
- RIPE NCC
- Country
- KZ
- Delegated
- Jun 12, 2012
- Status
- assigned
Report abuse
Abuse contact
- abuse@
telecom. kz - Name
- Kazakhtelecom Network Information Center
- Handle
- KNIC1-RIPE