Data as of Nov 16, 2026

89.218.117.4/30

No anonymizer space · no proxy exits in 30 days

JSC Kazakhtelecom

Announcement
RPKI valid
Announced by
Type
Business
Risk
0 / 100 · Low

Residential-proxy exits

Proxy exits
3
75% of its addresses · listed by providers
Always-on exits
1
33% of its exits
Providers
20
selling exits here

Proxy providers listing exits

  • 711Proxy
  • 911Proxy
  • 9HTTP
  • APROXY
  • ASHBURNPROXIES
  • BestProxy
  • FastProxy
  • GSocks
  • Geonix
  • KocerRoxy
  • LUMIPROXY
  • LemonBright
  • NSocks
  • NiuProxy
  • PROXY_CC
  • Proxies.fo
  • RainProxy
  • Shifter
  • Smartproxy
  • ZENPROXY_PREMIUM

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
89.218.0.0/16
since Jun 2007
AS9198Residential1,944
160 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.117.4/304IPATIGAEVAIPATIGAEVAASSIGNED PAFeb 27, 2014abuse@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.116.0/23

Routing history

Pattern
Stable
First seen
Mar 2008
Current origin since
Mar 2008 · 19 yr
Origin networks
1