Data as of Nov 14, 2026

89.218.207.0/24

3 residential-proxy exits · 30 days

JSC Kazakhtelecom

Announcement
RPKI valid
Announced by
Type
Business

Residential-proxy exits

Proxy exits
3
1.2% of its addresses · 30 days
Providers
9
selling exits here
Oct 15, 2026 – Nov 13, 2026

Exits seen per day

21 observations

Proxy providers listing exits

  • 911Proxy
  • CliProxy
  • Infatica
  • NodeProxy
  • Shifter
  • Smartproxy
  • Thordata
  • VantageProxies
  • ZENPROXY_PREMIUM

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
89.218.0.0/16
since Jun 2007
AS9198Residential1,932
140 always on
JSC Kazakhtelecom

Registrations in this block

The registry's network records over this block, widest first, each under its parent.

RangeAddressesNetnameHolderTypeCreatedAbuse contact
89.218.0.0/1665,536KZ-KAZAKTELECOM-20070518JSC Kazakhtelecom (ORG-KDNA1-RIPE) · KZALLOCATED PAMay 18, 2007abuse@telecom.kz
└ 89.218.207.0/304MIKRK_GCHPUst-KamenogorskASSIGNED PAOct 8, 2019abuse@telecom.kz
via KZ-KAZAKTELECOM-20070518
└ 89.218.207.4/304MIKRK_GCHPUst-KamenogorskASSIGNED PAOct 8, 2019abuse@telecom.kz
via KZ-KAZAKTELECOM-20070518
└ 89.218.207.8/304MIKRK_GCHPUst-KamenogorskASSIGNED PAOct 8, 2019abuse@telecom.kz
via KZ-KAZAKTELECOM-20070518
└ 89.218.207.12/304MIKRK_GCHPUst-KamenogorskASSIGNED PAOct 8, 2019abuse@telecom.kz
via KZ-KAZAKTELECOM-20070518
└ 89.218.207.16/304MIKRK_GCHPUst-KamenogorskASSIGNED PAOct 8, 2019abuse@telecom.kz
via KZ-KAZAKTELECOM-20070518
└ 89.218.207.20/304MIKRK_GCHPUst-KamenogorskASSIGNED PAOct 8, 2019abuse@telecom.kz
via KZ-KAZAKTELECOM-20070518
└ 89.218.207.24/304MIKRK_GCHPUst-KamenogorskASSIGNED PAOct 8, 2019abuse@telecom.kz
via KZ-KAZAKTELECOM-20070518
└ 89.218.207.28/304MIKRK_GCHPUst-KamenogorskASSIGNED PAOct 8, 2019abuse@telecom.kz
via KZ-KAZAKTELECOM-20070518
└ 89.218.207.32/304MIKRK_GCHPUst-KamenogorskASSIGNED PAOct 8, 2019abuse@telecom.kz
via KZ-KAZAKTELECOM-20070518
└ 89.218.207.36/304MIKRK_GCHPUst-KamenogorskASSIGNED PAOct 8, 2019abuse@telecom.kz
via KZ-KAZAKTELECOM-20070518
└ 89.218.207.40/304MIKRK_GCHPUst-KamenogorskASSIGNED PAOct 8, 2019abuse@telecom.kz
via KZ-KAZAKTELECOM-20070518
└ 89.218.207.44/304MIKRK_GCHPUst-KamenogorskASSIGNED PAOct 8, 2019abuse@telecom.kz
via KZ-KAZAKTELECOM-20070518
└ 89.218.207.48/304MIKRK_GCHPUst-KamenogorskASSIGNED PAOct 8, 2019abuse@telecom.kz
via KZ-KAZAKTELECOM-20070518
└ 89.218.207.52/304MIKRK_GCHPUst-KamenogorskASSIGNED PAOct 8, 2019abuse@telecom.kz
via KZ-KAZAKTELECOM-20070518
└ 89.218.207.56/304MIKRK_GCHPUst-KamenogorskASSIGNED PAOct 8, 2019abuse@telecom.kz
via KZ-KAZAKTELECOM-20070518
└ 89.218.207.60/304MIKRK_GCHPUst-KamenogorskASSIGNED PAOct 8, 2019abuse@telecom.kz
via KZ-KAZAKTELECOM-20070518
└ 89.218.207.64/304MIKRK_GCHPUst-KamenogorskASSIGNED PAOct 8, 2019abuse@telecom.kz
via KZ-KAZAKTELECOM-20070518
└ 89.218.207.68/304MIKRK_GCHPUst-KamenogorskASSIGNED PAOct 8, 2019abuse@telecom.kz
via KZ-KAZAKTELECOM-20070518
└ 89.218.207.72/304MIKRK_GCHPUst-KamenogorskASSIGNED PAOct 8, 2019abuse@telecom.kz
via KZ-KAZAKTELECOM-20070518
└ 89.218.207.76/304MIKRK_GCHPUst-KamenogorskASSIGNED PAOct 8, 2019abuse@telecom.kz
via KZ-KAZAKTELECOM-20070518
└ 89.218.207.80/304MIKRK_GCHPUst-KamenogorskASSIGNED PAOct 8, 2019abuse@telecom.kz
via KZ-KAZAKTELECOM-20070518
└ 89.218.207.84/304MIKRK_GCHPUst-KamenogorskASSIGNED PAOct 8, 2019abuse@telecom.kz
via KZ-KAZAKTELECOM-20070518
└ 89.218.207.88/304MIKRK_GCHPUst-KamenogorskASSIGNED PAOct 8, 2019abuse@telecom.kz
via KZ-KAZAKTELECOM-20070518
└ 89.218.207.92/304MIKRK_GCHPUst-KamenogorskASSIGNED PAOct 8, 2019abuse@telecom.kz
via KZ-KAZAKTELECOM-20070518
└ 89.218.207.96/304MIKRK_GCHPUst-KamenogorskASSIGNED PAOct 8, 2019abuse@telecom.kz
via KZ-KAZAKTELECOM-20070518
└ 89.218.207.100/304MIKRK_GCHPUst-KamenogorskASSIGNED PAOct 8, 2019abuse@telecom.kz
via KZ-KAZAKTELECOM-20070518
└ 89.218.207.104/304MIKRK_GCHPUst-KamenogorskASSIGNED PAOct 8, 2019abuse@telecom.kz
via KZ-KAZAKTELECOM-20070518
└ 89.218.207.108/304MIKRK_GCHPUst-KamenogorskASSIGNED PAOct 8, 2019abuse@telecom.kz
via KZ-KAZAKTELECOM-20070518
└ 89.218.207.112/304MIKRK_GCHPUst-KamenogorskASSIGNED PAOct 8, 2019abuse@telecom.kz
via KZ-KAZAKTELECOM-20070518
└ 89.218.207.116/304MIKRK_GCHPUst-KamenogorskASSIGNED PAOct 8, 2019abuse@telecom.kz
via KZ-KAZAKTELECOM-20070518
└ 89.218.207.120/304MIKRK_GCHPUst-KamenogorskASSIGNED PAOct 8, 2019abuse@telecom.kz
via KZ-KAZAKTELECOM-20070518
└ 89.218.207.124/304MIKRK_GCHPUst-KamenogorskASSIGNED PAOct 8, 2019abuse@telecom.kz
via KZ-KAZAKTELECOM-20070518
└ 89.218.207.128/304MIKRK_GCHPUst-KamenogorskASSIGNED PAOct 8, 2019abuse@telecom.kz
via KZ-KAZAKTELECOM-20070518
└ 89.218.207.132/304MIKRK_GCHPUst-KamenogorskASSIGNED PAOct 8, 2019abuse@telecom.kz
via KZ-KAZAKTELECOM-20070518
└ 89.218.207.136/304MIKRK_GCHPUst-KamenogorskASSIGNED PAOct 8, 2019abuse@telecom.kz
via KZ-KAZAKTELECOM-20070518
└ 89.218.207.140/304MIKRK_GCHPUst-KamenogorskASSIGNED PAOct 8, 2019abuse@telecom.kz
via KZ-KAZAKTELECOM-20070518
└ 89.218.207.144/304MIKRK_GCHPUst-KamenogorskASSIGNED PAOct 8, 2019abuse@telecom.kz
via KZ-KAZAKTELECOM-20070518
└ 89.218.207.148/304MIKRK_GCHPUst-KamenogorskASSIGNED PAOct 8, 2019abuse@telecom.kz
via KZ-KAZAKTELECOM-20070518
└ 89.218.207.152/304MIKRK_GCHPUst-KamenogorskASSIGNED PAOct 8, 2019abuse@telecom.kz
via KZ-KAZAKTELECOM-20070518
└ 89.218.207.156/304MIKRK_GCHPUst-KamenogorskASSIGNED PAOct 8, 2019abuse@telecom.kz
via KZ-KAZAKTELECOM-20070518
└ 89.218.207.160/304MIKRK_GCHPUst-KamenogorskASSIGNED PAOct 8, 2019abuse@telecom.kz
via KZ-KAZAKTELECOM-20070518
└ 89.218.207.164/304MIKRK_GCHPUst-KamenogorskASSIGNED PAOct 8, 2019abuse@telecom.kz
via KZ-KAZAKTELECOM-20070518
└ 89.218.207.168/304MIKRK_GCHPUst-KamenogorskASSIGNED PAOct 8, 2019abuse@telecom.kz
via KZ-KAZAKTELECOM-20070518
└ 89.218.207.172/304MIKRK_GCHPUst-KamenogorskASSIGNED PAOct 8, 2019abuse@telecom.kz
via KZ-KAZAKTELECOM-20070518
└ 89.218.207.176/304MIKRK_GCHPUst-KamenogorskASSIGNED PAOct 8, 2019abuse@telecom.kz
via KZ-KAZAKTELECOM-20070518
└ 89.218.207.180/304MIKRK_GCHPUst-KamenogorskASSIGNED PAOct 8, 2019abuse@telecom.kz
via KZ-KAZAKTELECOM-20070518
└ 89.218.207.184/304MIKRK_GCHPUst-KamenogorskASSIGNED PAOct 8, 2019abuse@telecom.kz
via KZ-KAZAKTELECOM-20070518
└ 89.218.207.188/304MIKRK_GCHPUst-KamenogorskASSIGNED PAOct 8, 2019abuse@telecom.kz
via KZ-KAZAKTELECOM-20070518
└ 89.218.207.192/304MIKRK_GCHPUst-KamenogorskASSIGNED PAOct 8, 2019abuse@telecom.kz
via KZ-KAZAKTELECOM-20070518
└ 89.218.207.196/304MIKRK_GCHPUst-KamenogorskASSIGNED PAOct 8, 2019abuse@telecom.kz
via KZ-KAZAKTELECOM-20070518
└ 89.218.207.200/304MIKRK_GCHPUst-KamenogorskASSIGNED PAOct 9, 2019abuse@telecom.kz
via KZ-KAZAKTELECOM-20070518
└ 89.218.207.204/304MIKRK_GCHPUst-KamenogorskASSIGNED PAOct 8, 2019abuse@telecom.kz
via KZ-KAZAKTELECOM-20070518
└ 89.218.207.208/304MIKRK_GCHPUst-KamenogorskASSIGNED PAOct 8, 2019abuse@telecom.kz
via KZ-KAZAKTELECOM-20070518
└ 89.218.207.212/304MIKRK_GCHPUst-KamenogorskASSIGNED PAOct 8, 2019abuse@telecom.kz
via KZ-KAZAKTELECOM-20070518
└ 89.218.207.216/304MIKRK_GCHPUst-KamenogorskASSIGNED PAOct 8, 2019abuse@telecom.kz
via KZ-KAZAKTELECOM-20070518
└ 89.218.207.220/304MIKRK_GCHPUst-KamenogorskASSIGNED PAOct 8, 2019abuse@telecom.kz
via KZ-KAZAKTELECOM-20070518
└ 89.218.207.224/304MIKRK_GCHPUst-KamenogorskASSIGNED PAOct 8, 2019abuse@telecom.kz
via KZ-KAZAKTELECOM-20070518
└ 89.218.207.228/304VRDTSemeiASSIGNED PADec 8, 2023abuse@telecom.kz
via KZ-KAZAKTELECOM-20070518
└ 89.218.207.232/304MIKRK_GCHPUst-KamenogorskASSIGNED PAOct 9, 2019abuse@telecom.kz
via KZ-KAZAKTELECOM-20070518
└ 89.218.207.236/304MIKRK_GCHPUst-KamenogorskASSIGNED PAOct 9, 2019abuse@telecom.kz
via KZ-KAZAKTELECOM-20070518
└ 89.218.207.240/304MIKRK_GCHPUst-KamenogorskASSIGNED PAOct 9, 2019abuse@telecom.kz
via KZ-KAZAKTELECOM-20070518
└ 89.218.207.244/304MIKRK_GCHPUst-KamenogorskASSIGNED PAOct 9, 2019abuse@telecom.kz
via KZ-KAZAKTELECOM-20070518
└ 89.218.207.248/304MIKRK_GCHPUst-KamenogorskASSIGNED PAOct 9, 2019abuse@telecom.kz
via KZ-KAZAKTELECOM-20070518
└ 89.218.207.252/304MIKRK_GCHPUst-KamenogorskASSIGNED PAOct 9, 2019abuse@telecom.kz
via KZ-KAZAKTELECOM-20070518

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

Routing timeline

Covering aggregate above, the prefix's own history below

89.218.204.0/22

Routing history

Pattern
Stable
First seen
May 2008
Current origin since
Nov 2023 · 3.0 yr
Origin networks
1