UZTELECOM-DC

Data as of 2026-09-20
BGP inherited
This organisation
Netblocks8 · 2,048 IPv4 addresses
Record ID242394536
RegistryRIPE
Customerssee who runs inside this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
Shared handles clustered on 4 shared RIR contact/maintainer handles
Registry names 1 distinct registrant name across these blocks
full provenance (JSON) → · how attribution works · report an issue

IP Ranges (8)

⬇ export CSV
CIDR Org name Registry Status Confidence
92.63.206.0/24 UZTELECOM-DC RIPE ASSIGNED PA ● low
92.63.207.0/24 UZTELECOM-DC RIPE ASSIGNED PA ● low
109.94.172.0/24 UZTELECOM-DC RIPE ASSIGNED PA ● low
109.94.173.0/24 UZTELECOM-DC RIPE ASSIGNED PA ● low
185.74.4.0/24 UZTELECOM-DC RIPE ASSIGNED PA ● low
185.74.5.0/24 UZTELECOM-DC RIPE ASSIGNED PA ● low
185.74.6.0/24 UZTELECOM-DC RIPE ASSIGNED PA ● low
185.74.7.0/24 UZTELECOM-DC RIPE ASSIGNED PA ● low

Footprint over time

13 weekly snapshots · JSON
8 +1 netblocks since 2026-07-05
2026-07-05 peak 8 2026-09-20

Network trust

what's this?
RPKI hygiene: B how networks compare →
87.5% of checked blocks have valid RPKI ROA coverage (7 of 8)
RPKI-inferred operator "Uzbektelekom" Joint Stock Company
Nearly all of this network's RPKI-covered space is cryptographically authorized for this single operator — the registered netname is likely one of its internal infrastructure labels.
No discrepancies found among checked blocks.

NIC Handles

AS8193-MNT DUMY-RIPE DUMY-RIPE UZTELECOM-MNT