Data as of Nov 11, 2026

89.218.58.136/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
17
100% of its addresses · listed by providers
Always-on exits
1
5.9% of its exits
Providers
45
selling exits here

Proxy providers listing exits

  • 2Captcha
  • 711Proxy
  • 911Proxy
  • 9Proxy
  • ASHBURNPROXIES
  • AnyIP
  • BestProxy
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • EnigmaProxy
  • Evomi
  • FastProxy
  • FlashProxy
  • GSocks
  • Geonode
  • GonzoProxy
  • IPOasis
  • IPPeak
  • Infatica
  • InfiniteProxies
  • LemonBright
  • LemonPrime
  • MangoProxy
  • NSocks
  • NodeProxy
  • NovaProxy
  • Novada
  • Oxylabs
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyWing
  • Proxyma
  • RainProxy
  • Shifter
  • Smartproxy
  • Thordata
  • ThunderProxy
  • VantageProxies
  • VitalExclusive
  • VitalProxy
  • ZENPROXY_PREMIUM

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
89.218.0.0/16
since Jun 2007
AS9198Residential1,856
93 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.58.136/304IP_BESTWESTERNNur-SultanASSIGNED PAMay 3, 2022abuse@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.58.0/24

Routing history

Pattern
Stable
First seen
May 2026
Current origin since
May 2026 · 6 mo
Origin networks
1