Data as of Nov 17, 2026

90.156.164.0/22

9 residential-proxy exits · 30 days

'Uzbektelekom' Joint Stock Company

Announcement
this exact prefix
No RPKI
Announced by
Type
Residential
Risk
0 / 100 · Low
Recent change
New origin Oct 22, 2026
its first announcement on record

Residential-proxy exits

Proxy exits
9
0.88% of its addresses · 30 days
Spread
1 of 4
/24s with at least one exit
Providers
24
selling exits here
Oct 18, 2026 – Nov 16, 2026

Exits seen per day

110 observations

Proxy providers listing exits

  • 9HTTP
  • Byteful
  • CYBERYOZH
  • FLAMEPROXIES_PREMIUM
  • FastProxy
  • GEEKPROXY_FLEX
  • GSocks
  • IPFly
  • Infatica
  • KocerRoxy
  • LemonBright
  • NSTPROXY_LITE
  • NodeProxy
  • PROXYLANE
  • PROXYSCRAPE
  • Proxiware
  • Proxy-Seller
  • Proxy302
  • Proxyma
  • RainProxy
  • SOTAPROXY
  • Shifter
  • Thordata
  • ThunderProxy

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
90.156.160.0/212,048UZ-UZTELECOM-20061117"Uzbektelekom" Joint Stock Company (ORG-JC7-RIPE) · UZALLOCATED PANov 22, 2021ripe@bkm.uz
└ 90.156.164.0/24256UZTELECOMunknownASSIGNED PAJul 15, 2024ripe@bkm.uz
via UZ-UZTELECOM-20061117
└ 90.156.165.0/24256UZTELECOMunknownASSIGNED PAJul 15, 2024ripe@bkm.uz
via UZ-UZTELECOM-20061117
└ 90.156.166.0/24256UZTELECOMunknownASSIGNED PAJul 15, 2024ripe@bkm.uz
via UZ-UZTELECOM-20061117
└ 90.156.167.0/24256UZTELECOMunknownASSIGNED PAJul 15, 2024ripe@bkm.uz
via UZ-UZTELECOM-20061117

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
Oct 22, 2026
Current origin since
Oct 22, 2026 · under a month
Origin networks
1