Data as of Nov 16, 2026

89.126.208.0/22

12 residential-proxy exits · 30 days

'Uzbektelekom' Joint Stock Company

Announcement
this exact prefix
RPKI valid
Announced by
Type
Hosting
Risk
50 / 100 · Medium

Residential-proxy exits

Proxy exits
12
1.2% of its addresses · 30 days
Spread
3 of 4
/24s with at least one exit
Providers
9
selling exits here
Oct 17, 2026 – Nov 15, 2026

Exits seen per day

47 observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
89.126.210.0/2404
89.126.208.0/2403
89.126.209.0/2401

Proxy providers listing exits

  • 911Proxy
  • BirdProxies
  • ColaProxy
  • LudaxProxy
  • Maskify
  • Novada
  • Proxiware
  • PuraRoute
  • RapidProxy

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
89.126.208.0/204,096UZ-UZTELECOM-20060308"Uzbektelekom" Joint Stock Company (ORG-JC7-RIPE) · UZALLOCATED PAJul 10, 2025ripe@bkm.uz
└ 89.126.208.0/24256UZTELECOMunknownASSIGNED PAJul 10, 2025ripe@bkm.uz
via UZ-UZTELECOM-20060308
└ 89.126.209.0/24256UZTELECOMunknownASSIGNED PAJul 10, 2025ripe@bkm.uz
via UZ-UZTELECOM-20060308
└ 89.126.210.0/24256UZTELECOMunknownASSIGNED PAJul 10, 2025ripe@bkm.uz
via UZ-UZTELECOM-20060308
└ 89.126.211.0/24256UZTELECOMunknownASSIGNED PAJul 10, 2025ripe@bkm.uz
via UZ-UZTELECOM-20060308

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
Jul 2025
Current origin since
Jul 2025 · 1.3 yr
Origin networks
2
Last change of origin
Jul 2025
Recorded history

History

Handoffs
1