Data as of Nov 16, 2026

84.54.112.0/24

32 residential-proxy exits · 30 days

'Uzbektelekom' Joint Stock Company

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

Residential-proxy exits

Proxy exits
32
13% of its addresses · 30 days
Always-on exits
2
6.3% of its exits
Providers
69
selling exits here
Oct 17, 2026 – Nov 15, 2026

Exits seen per day

15K observations

Proxy providers listing exits

  • 2Captcha
  • 711Proxy
  • 9Proxy
  • Ake.net
  • AnyIP
  • BartProxies
  • BirdProxies
  • BlurPath
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • DataImpulse
  • Datarama
  • Decodo
  • EVOPROXY
  • EnigmaProxy
  • Evomi
  • FastProxy
  • FlashProxy
  • GSocks
  • Geonix
  • Geonode
  • GloryCloud
  • GonzoProxy
  • IPFly
  • IPPeak
  • IPRoyal
  • Infatica
  • InfiniteProxies
  • KindProxy
  • KocerRoxy
  • Kookey
  • LemonBright
  • LemonPrime
  • LightningProxies
  • MangoProxy
  • MoMoProxy
  • NSocks
  • NextProxy
  • NiuProxy
  • NodeProxy
  • NovaProxy
  • Novada
  • Oxylabs
  • PROXYSCRAPE
  • Proxiware
  • Proxmint
  • Proxy-Seller
  • Proxy4U
  • ProxyEmpire
  • ProxyGeo
  • ProxyHat
  • ProxyRack
  • ProxyWing
  • Proxying
  • Proxyma
  • PuraRoute
  • RainProxy
  • RapidProxy
  • RolaProxy
  • Shifter
  • StrikeProxy
  • SwiftProxy
  • TalorData
  • Thordata
  • ThunderProxy
  • VantageProxies
  • VitalExclusive

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
84.54.64.0/1816,384UZ-UZTELECOM-20041110"Uzbektelekom" Joint Stock Company (ORG-JC7-RIPE) · UZALLOCATED PANov 10, 2004ripe@bkm.uz
└ 84.54.112.0/24256UZTELECOMunknownASSIGNED PAJun 15, 2011ripe@bkm.uz
via UZ-UZTELECOM-20041110

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
Reactivated
First seen
Oct 2011
Current origin since
Jun 2025 · 1.4 yr
Origin networks
2
Last change of origin
Jun 2025
Recorded history

History

Handoffs
1