LAYER3 INTEL
Get started
Sign in
Data as of Nov 14, 2026

84.54.64.0/19

1,055 residential-proxy exits · 30 days

'Uzbektelekom' Joint Stock Company

Announcement
this exact prefix
RPKI valid
Announced by
AS8193
Type
Residential

Residential-proxy exits

Proxy exits
1,055
13% of its addresses · 30 days
Always-on exits
543
51% of its exits
Spread
9 of 32
/24s with at least one exit
Providers
125
selling exits here
Oct 15, 2026 – Nov 13, 2026

Exits seen per day

9.7M observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
84.54.73.0/24143211
84.54.72.0/24136191
84.54.70.0/24127202
84.54.71.0/24115169
84.54.75.0/24955
84.54.83.0/24643
84.54.82.0/24522
84.54.74.0/24223
84.54.69.0/2401

Proxy providers listing exits

  • 2Captcha
  • 711Proxy
  • 9Proxy
  • ASHBURNPROXIES
  • Ake.net
  • AnyIP
  • B2Proxy
  • BartProxies
  • BirdProxies
  • BlurPath
  • BottingTools
  • Bright Data
  • BuyingProxy
  • ByteProxies
  • Byteful
  • CatProxies
  • CliProxy
  • CoreProxy
  • DataImpulse
  • Datarama
  • Decodo
  • EVOPROXY
  • EZProxies
  • EnigmaProxy
  • Evomi
  • FastProxy
  • FlashProxy
  • FloppyData
  • GSocks
  • GeekProxy
  • Geonix
  • Geonode
  • GhostConnect
  • GloryCloud
  • GoProxies
  • GonzoProxy
  • HELODATA
  • HPROXY
  • HideProxy
  • HydraProxy
  • IPCola
  • IPFly
  • IPMUSK
  • IPOasis
  • IPPeak
  • IPROCKET_BASIC
  • IPRoyal
  • Infatica
  • InfiniteProxies
  • KindProxy
  • KocerRoxy
  • Kookey
  • LOKIPROXY
  • LemonBright
  • LemonLabs
  • LemonPrime
  • LightningProxies
  • LudaxProxy
  • MangoProxy
  • MarsProxies
  • Maskify
  • MoMoProxy
  • NSocks
  • NextProxy
  • NiuProxy
  • NodeMaven
  • NodeProxy
  • NovProxy
  • NovaProxy
  • Novada
  • Oxylabs
  • PROXYFALL
  • PROXYLANE
  • PROXYON
  • PROXYSAVER
  • PROXYSCRAPE
  • PROXYWING_BASIC
  • PSBProxy
  • PacketStream
  • PrivateByte
  • ProxiesVision
  • Proxio
  • Proxiware
  • Proxmint
  • Proxy-Cheap
  • Proxy-Seller
  • Proxy302
  • Proxy4U
  • ProxyEmpire
  • ProxyGeo
  • ProxyHat
  • ProxyRack
  • ProxyWing
  • Proxying
  • Proxyma
  • PuraRoute
  • Q2IP
  • QUANTICDATA
  • RH7Proxy
  • RainProxy
  • RapidProxy
  • ResiProxies
  • RoamProxy
  • RolaProxy
  • SIMPLYNODE
  • SPYDERPROXY_BASIC
  • SPYDERPROXY_PREMIUM
  • Shifter
  • Smartproxy
  • StrikeProxy
  • SwiftProxy
  • TORCHPROXIES_BASIC
  • TORCHPROXIES_PREMIUM
  • TORCHPROXIES_X
  • TalorData
  • Thordata
  • ThunderProxy
  • VantageProxies
  • VibeProxies
  • VitalData
  • VitalExclusive
  • VitalProxy
  • Webshare
  • ZENPROXY_LITE
  • ZENPROXY_PREMIUM

Announcements

Nesting

More-specifics by size

Sized by addresses, colored by each announcement's type. Click a tile with children to zoom in, a leaf to open it.
More specific

Announcements inside

PrefixOriginTypeProxy exitsHolderRPKI
84.54.66.0/23
since Sep 2021
AS8193Residential"Uzbektelekom" Joint Stock Company
84.54.70.0/23
since Nov 2021
AS8193Residential371
242 always on
"Uzbektelekom" Joint Stock Company
84.54.70.0/24
since Nov 2022
AS8193Residential202
127 always on
"Uzbektelekom" Joint Stock Company
84.54.71.0/24
since Nov 2022
AS8193Residential169
115 always on
"Uzbektelekom" Joint Stock Company
84.54.72.0/23
since Nov 2022
AS8193Residential402
279 always on
"Uzbektelekom" Joint Stock Company
84.54.72.0/24
since Nov 2022
AS8193Residential191
136 always on
"Uzbektelekom" Joint Stock Company
84.54.73.0/24
since Nov 2022
AS8193Residential211
143 always on
"Uzbektelekom" Joint Stock Company
84.54.86.0/23
since Sep 2021
AS8193Residential"Uzbektelekom" Joint Stock Company
84.54.86.0/24AS8193Residential"Uzbektelekom" Joint Stock Company
84.54.87.0/24AS8193Residential"Uzbektelekom" Joint Stock Company

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.64.0/24256UZTELECOMunknownASSIGNED PAOct 10, 2018ripe@bkm.uz
via UZ-UZTELECOM-20041110
└ 84.54.65.0/24256UZTELECOMunknownASSIGNED PAMay 19, 2010ripe@bkm.uz
via UZ-UZTELECOM-20041110
└ 84.54.66.0/24256UZTELECOMunknownASSIGNED PAMay 19, 2010ripe@bkm.uz
via UZ-UZTELECOM-20041110
└ 84.54.67.0/24256UZTELECOMunknownASSIGNED PAMay 19, 2010ripe@bkm.uz
via UZ-UZTELECOM-20041110
└ 84.54.68.0/24256UZTELECOMunknownASSIGNED PAOct 10, 2018ripe@bkm.uz
via UZ-UZTELECOM-20041110
└ 84.54.69.0/24256UZTELECOMunknownASSIGNED PAOct 10, 2018ripe@bkm.uz
via UZ-UZTELECOM-20041110
└ 84.54.70.0/24256UZTELECOMunknownASSIGNED PAOct 10, 2018ripe@bkm.uz
via UZ-UZTELECOM-20041110
└ 84.54.71.0/24256UZTELECOMunknownASSIGNED PAOct 10, 2018ripe@bkm.uz
via UZ-UZTELECOM-20041110
└ 84.54.72.0/24256UZTELECOMunknownASSIGNED PAOct 10, 2018ripe@bkm.uz
via UZ-UZTELECOM-20041110
└ 84.54.73.0/24256UZTELECOMunknownASSIGNED PAOct 10, 2018ripe@bkm.uz
via UZ-UZTELECOM-20041110
└ 84.54.74.0/24256UZTELECOMunknownASSIGNED PAOct 10, 2018ripe@bkm.uz
via UZ-UZTELECOM-20041110
└ 84.54.75.0/24256UZTELECOMunknownASSIGNED PAOct 10, 2018ripe@bkm.uz
via UZ-UZTELECOM-20041110
└ 84.54.76.0/221,024UZTELECOMunknownASSIGNED PAMay 19, 2010ripe@bkm.uz
via UZ-UZTELECOM-20041110
└ 84.54.80.0/23512UZTELECOMunknownASSIGNED PAOct 10, 2018ripe@bkm.uz
via UZ-UZTELECOM-20041110
└ 84.54.82.0/24256UZTELECOMunknownASSIGNED PAOct 10, 2018ripe@bkm.uz
via UZ-UZTELECOM-20041110
└ 84.54.83.0/24256UZTELECOMunknownASSIGNED PAOct 10, 2018ripe@bkm.uz
via UZ-UZTELECOM-20041110
└ 84.54.84.0/221,024UZTELECOMunknownASSIGNED PAMay 19, 2010ripe@bkm.uz
via UZ-UZTELECOM-20041110
└ 84.54.88.0/24256UZTELECOMunknownASSIGNED PAOct 10, 2018ripe@bkm.uz
via UZ-UZTELECOM-20041110
└ 84.54.89.0/24256UZTELECOMunknownASSIGNED PAOct 10, 2018ripe@bkm.uz
via UZ-UZTELECOM-20041110
└ 84.54.90.0/23512UZTELECOMunknownASSIGNED PAOct 10, 2018ripe@bkm.uz
via UZ-UZTELECOM-20041110
└ 84.54.92.0/221,024UZTELECOMunknownASSIGNED PAOct 10, 2018ripe@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

AnnouncementRouting historyRPKI & IRRWhois & abuse
Routing timeline

Who has announced this prefix

Summary

Routing history

Pattern
Stable
First seen
May 2005
Current origin since
Aug 2019 · 7.3 yr
Origin networks
2
Last change of origin
Aug 2019
Recorded history

History

Handoffs
1