UTL-NET

BGP inherited
Cluster stats
Netblocks9 · 8,711 IPv4 addresses
Registered in Russia (5) · Netherlands (4)
All fragments 12 blocks across 4 clusters
Cluster ID209210429
RegistryRIPE
Customersfind customers using this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
Shared handles clustered on 5 shared RIR contact/maintainer handles
Registry names 2 distinct registrant names across these blocks
full provenance (JSON) → · how attribution works

Footprint over time

5 weekly snapshots · JSON
9 0 netblocks since 2026-07-05
2026-07-05 peak 9 2026-07-19

IP Ranges (9)

⬇ export CSV
CIDR Org name Registry Status Confidence
80.93.96.0/21 UTL-NET RIPE ASSIGNED PA ● low
80.93.104.0/21 UTL-NET RIPE ASSIGNED PA ● low
83.234.236.0/23 UTL-NET RIPE ASSIGNED PA ● low
93.88.208.0/21 UTL-NET RIPE ASSIGNED PA ● low
93.88.216.0/21 UTL-NET RIPE ASSIGNED PA ● low
159.100.94.76/30 UTL RIPE LEGACY ● low
159.100.100.76/30 UTL RIPE LEGACY ● low
212.78.200.196/30 UTL RIPE ASSIGNED PA ● low
213.34.138.244/30 UTL RIPE ASSIGNED PA ● low

Possibly related to this organisation

what's this?
Same name family
Separately-registered clusters whose names share “UTL” — often per-country or per-system registrations of the same brand, occasionally a different organisation sharing the name. Not counted in this organisation's own footprint.

Network trust

what's this?
RPKI hygiene: C how networks compare →
55.6% of checked blocks have valid RPKI ROA coverage (5 of 9)
Possible discrepancies (1)

These blocks are registered to UTL-NET but cryptographically authorized for a different, unrelated network (1 distinct holder) — often M&A history, multi-homing, or outsourced/managed hosting, occasionally worth a closer look.

83.234.236.0/23 /23 authorized for AS20485 — Joint Stock Company TransTeleCom

NIC Handles

DUMY-RIPE DUMY-RIPE TNF-MNT TRANSTELECOM-MNT UTL-MNT