Data as of Nov 12, 2026

89.237.192.0/18

569 residential-proxy exits · 30 days

OJSC Kyrgyztelecom

Announcement
this exact prefix
RPKI valid
Announced by
Type
Residential

Residential-proxy exits

Proxy exits
569
3.5% of its addresses · 30 days
Always-on exits
515
91% of its exits
Spread
12 of 64
/24s with at least one exit
Providers
70
selling exits here
Oct 13, 2026 – Nov 11, 2026

Exits seen per day

440K observations

/24s with the most always-on exits

Proxy providers listing exits

  • 711Proxy
  • 9Proxy
  • Ake.net
  • AnyIP
  • B2Proxy
  • BirdProxies
  • BlurPath
  • BottingTools
  • Bright Data
  • ByteProxies
  • Byteful
  • CatProxies
  • CliProxy
  • DataImpulse
  • Decodo
  • EVOPROXY
  • EnigmaProxy
  • Evomi
  • FastProxy
  • FlashProxy
  • GSocks
  • Geonode
  • GloryCloud
  • GoProxies
  • GonzoProxy
  • IPPeak
  • IPRoyal
  • Infatica
  • InfiniteProxies
  • JoyProxy
  • KindProxy
  • Kookey
  • LemonBright
  • LudaxProxy
  • MangoProxy
  • Maskify
  • MoMoProxy
  • NextProxy
  • NiuProxy
  • NodeProxy
  • NovaProxy
  • Novada
  • Oxylabs
  • PacketStream
  • Proxiware
  • Proxmint
  • Proxy-Seller
  • Proxy302
  • Proxy4U
  • ProxyEmpire
  • ProxyGeo
  • ProxyRack
  • ProxyWing
  • Proxyma
  • Q2IP
  • RH7Proxy
  • RainProxy
  • RapidProxy
  • Shifter
  • StrikeProxy
  • SwiftProxy
  • TORCHPROXIES_BASIC
  • TORCHPROXIES_PREMIUM
  • TORCHPROXIES_X
  • Thordata
  • ThunderProxy
  • VitalExclusive
  • Webshare
  • YumiProxy
  • ZENPROXY_LITE

Announcements

More specific

Announcements inside

PrefixOriginTypeProxy exitsHolderRPKI
89.237.192.0/19
since Nov 2008
AS12997Residential570
515 always on
OJSC Kyrgyztelecom
89.237.224.0/19
since Nov 2008
AS12997ResidentialOJSC Kyrgyztelecom

Registrations in this block

The registry's network records over the announcement: those covering it, widest first, then every record inside it, under its parent.

RangeAddressesNetnameHolderTypeCreatedAbuse contact
89.237.192.0/1816,384KG-KT-20060713OJSC Kyrgyztelecom (ORG-JK1-RIPE) · KGALLOCATED PAJul 13, 2006azolotko@kt.kg
└ 89.237.192.0/212,048KYRGYZTELEKOM-PPPOE-OSHunknownASSIGNED PAAug 7, 2014azolotko@kt.kg
via KG-KT-20060713
└ 89.237.200.0/212,048KYRGYZTELEKOM-PPPOE-OSHunknownASSIGNED PAMar 18, 2015azolotko@kt.kg
via KG-KT-20060713
└ 89.237.208.0/212,048KYRGYZTELEKOM-PPPOE-OSHunknownASSIGNED PAMar 18, 2015azolotko@kt.kg
via KG-KT-20060713
└ 89.237.216.0/212,048KYRGYZTELEKOM-PPPOE-OSHunknownASSIGNED PAMar 18, 2015azolotko@kt.kg
via KG-KT-20060713
└ 89.237.224.0/212,048KYRGYZTELEKOM-PPPOE-OSHunknownASSIGNED PAMar 18, 2015azolotko@kt.kg
via KG-KT-20060713
└ 89.237.232.0/212,048KYRGYZTELEKOM-PPPOE-OSHunknownASSIGNED PAMar 18, 2015azolotko@kt.kg
via KG-KT-20060713
└ 89.237.240.0/212,048KYRGYZTELEKOM-PPPOE-OSHunknownASSIGNED PAMar 18, 2015azolotko@kt.kg
via KG-KT-20060713
└ 89.237.248.0/212,048KYRGYZTELEKOM-PPPOE-OSHunknownASSIGNED PAMar 18, 2015azolotko@kt.kg
via KG-KT-20060713

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

Who has announced this prefix

Summary

Routing history

Pattern
Stable
First seen
Jul 2006
Current origin since
Jul 2006 · 20 yr
Origin networks
1