Data as of Nov 14, 2026

80.72.184.0/21

24 residential-proxy exits · 30 days

OJSC Kyrgyztelecom

Announcement
this exact prefix
RPKI valid
Announced by
Type
Residential
Risk
0 / 100 · Low

Residential-proxy exits

Proxy exits
24
1.2% of its addresses · 30 days
Spread
2 of 8
/24s with at least one exit
Providers
54
selling exits here
Oct 15, 2026 – Nov 13, 2026

Exits seen per day

414 observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
80.72.184.0/24017
80.72.185.0/2407

Proxy providers listing exits

  • 711Proxy
  • AnyIP
  • B2Proxy
  • BottingTools
  • Byteful
  • CatProxies
  • DataImpulse
  • Decodo
  • EVOPROXY
  • EZProxies
  • EnigmaProxy
  • Evomi
  • FastProxy
  • GSocks
  • Geonode
  • GloryCloud
  • GonzoProxy
  • IPFly
  • IPPeak
  • IPRoyal
  • Infatica
  • InfiniteProxies
  • KindProxy
  • KocerRoxy
  • Kookey
  • LemonBright
  • LudaxProxy
  • MangoProxy
  • MoMoProxy
  • NextProxy
  • NiuProxy
  • NodeProxy
  • NovaProxy
  • Novada
  • Oxylabs
  • Proxiware
  • Proxy-Seller
  • Proxy302
  • Proxy4U
  • ProxyGeo
  • ProxyWing
  • PuraRoute
  • RainProxy
  • RapidProxy
  • RoamProxy
  • RolaProxy
  • SIMPLYNODE
  • SwiftProxy
  • TORCHPROXIES_PREMIUM
  • TORCHPROXIES_X
  • TalorData
  • Thordata
  • ThunderProxy
  • VitalExclusive

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
80.72.176.0/20
since Jan 2011
AS12997Residential130
4 always on
OJSC 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
80.72.176.0/204,096KG-KT-20101206OJSC Kyrgyztelecom (ORG-JK1-RIPE) · KGALLOCATED PADec 6, 2010azolotko@kt.kg
└ 80.72.184.0/24256KYRGYZTELECOM_ADSL_PPPOEunknownASSIGNED PAFeb 25, 2011azolotko@kt.kg
via KG-KT-20101206
└ 80.72.185.0/24256KYRGYZTELECOM_ADSL_PPPOEunknownASSIGNED PAFeb 25, 2011azolotko@kt.kg
via KG-KT-20101206
└ 80.72.186.0/24256KYRGYZTELECOM_ADSL_PPPOEunknownASSIGNED PAFeb 25, 2011azolotko@kt.kg
via KG-KT-20101206
└ 80.72.187.0/24256KYRGYZTELECOM_ADSL_PPPOEunknownASSIGNED PAFeb 25, 2011azolotko@kt.kg
via KG-KT-20101206
└ 80.72.188.0/24256KYRGYZTELECOM_ADSL_PPPOEunknownASSIGNED PAFeb 25, 2011azolotko@kt.kg
via KG-KT-20101206
└ 80.72.189.0/24256KYRGYZTELECOM_ADSL_PPPOEunknownASSIGNED PAFeb 25, 2011azolotko@kt.kg
via KG-KT-20101206
└ 80.72.190.0/24256KYRGYZTELECOM_ADSL_PPPOEunknownASSIGNED PAFeb 25, 2011azolotko@kt.kg
via KG-KT-20101206
└ 80.72.191.0/24256KYRGYZTELECOM_ADSL_PPPOEunknownASSIGNED PAFeb 25, 2011azolotko@kt.kg
via KG-KT-20101206

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

Summary

Routing history

Pattern
Stable
First seen
May 2005
Current origin since
Jan 2014 · 13 yr
Origin networks
2
Last change of origin
Jan 2014
Recorded history

History

Handoffs
1