UDMVT-NET

BGP inherited
Cluster stats
Netblocks9 · 61,671 IPv4 addresses
Cluster ID209355514
RegistryRIPE
Customersfind customers using this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
Shared handles clustered on 3 shared RIR contact/maintainer handles
Registry names 1 distinct registrant name 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
78.85.0.0 – 78.85.15.15 UDMVT-NET RIPE ASSIGNED PA ● low
78.85.15.32 – 78.85.44.255 UDMVT-NET RIPE ASSIGNED PA ● low
78.85.45.0 – 78.85.64.255 UDMVT-NET RIPE ASSIGNED PA ● low
78.85.80.0/20 UDMVT-NET RIPE ASSIGNED PA ● low
78.85.96.0 – 78.85.159.255 UDMVT-NET RIPE ASSIGNED PA ● low
78.85.160.0/19 UDMVT-NET RIPE ASSIGNED PA ● low
78.85.192.0/19 UDMVT-NET RIPE ASSIGNED PA ● low
78.85.224.0/20 UDMVT-NET RIPE ASSIGNED PA ● low
78.85.240.0/20 UDMVT-NET RIPE ASSIGNED PA ● low

Network trust

what's this?
RPKI hygiene: A how networks compare →
100.0% of checked blocks have valid RPKI ROA coverage (9 of 9)
RPKI-inferred operator PJSC Rostelecom
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

DUMY-RIPE DUMY-RIPE MNT-PAA67