Data as of Nov 14, 2026

185.4.160.0/22

5 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
5
0.49% of its addresses · 30 days
Spread
1 of 4
/24s with at least one exit
Providers
39
selling exits here
Oct 15, 2026 – Nov 13, 2026

Exits seen per day

220 observations

Proxy providers listing exits

  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • EnigmaProxy
  • Evomi
  • GSocks
  • GeekProxy
  • GloryCloud
  • GonzoProxy
  • IPFly
  • IPPeak
  • Infatica
  • InfiniteProxies
  • KindProxy
  • Kookey
  • LemonBright
  • LightningProxies
  • MangoProxy
  • NodeProxy
  • NovaProxy
  • Novada
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyWing
  • Proxyma
  • RapidProxy
  • SIMPLYNODE
  • Shifter
  • StrikeProxy
  • SwiftProxy
  • TalorData
  • Thordata
  • ThunderProxy
  • VantageProxies
  • VitalData
  • 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
185.4.160.0/221,024UZ-UZTELECOM-20120926"Uzbektelekom" Joint Stock Company (ORG-JC7-RIPE) · UZALLOCATED PAJan 18, 2024ripe@bkm.uz
└ 185.4.160.0/24256BUZTON-FTTB-TASHKENT-NETInternet Service Provider BUZTON J.V.ASSIGNED PANov 23, 2012ripe@bkm.uz
via UZ-UZTELECOM-20120926
└ 185.4.161.0/24256BUZTON-FTTB-TASHKENT-NETInternet Service Provider BUZTON J.V.ASSIGNED PANov 23, 2012ripe@bkm.uz
via UZ-UZTELECOM-20120926
└ 185.4.162.0/24256BUZTON-FTTB-TASHKENT-NETInternet Service Provider BUZTON J.V.ASSIGNED PANov 23, 2012ripe@bkm.uz
via UZ-UZTELECOM-20120926
└ 185.4.163.0/24256BUZTON-FTTB-TASHKENT-NETInternet Service Provider BUZTON J.V.ASSIGNED PANov 23, 2012ripe@bkm.uz
via UZ-UZTELECOM-20120926

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
Rotating
First seen
Sep 2012
Current origin since
Feb 2024 · 2.8 yr
Origin networks
2
Last change of origin
Feb 2024
Recorded history

History

Handoffs
1