MF-DVF

BGP inherited
Cluster stats
Netblocks7
All fragments 50 blocks across 14 clusters
Cluster ID205595649
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

4 weekly snapshots · JSON
7 0 netblocks since 2026-07-05
2026-07-05 peak 7 2026-07-13

IP Ranges (7)

⬇ export CSV
CIDR Org name Registry Status Confidence
37.28.190.0/23 MF-DVF RIPE LIR-PARTITIONED PA ● low
37.29.43.0/24 MF-DVF RIPE LIR-PARTITIONED PA ● low
37.29.94.0/23 MF-DVF RIPE LIR-PARTITIONED PA ● low
78.25.127.0/24 MF-DVF RIPE LIR-PARTITIONED PA ● low
83.169.224.0 – 83.169.230.255 MF-DVF RIPE LIR-PARTITIONED PA ● low
188.170.228.0 – 188.170.239.255 MF-DVF RIPE LIR-PARTITIONED PA ● low
2a03:d000:7000::/36 MF-DVF RIPE ALLOCATED-BY-LIR ● low

Network trust

what's this?
RPKI hygiene: B how networks compare →
85.7% of checked blocks have valid RPKI ROA coverage (6 of 7)
RPKI-inferred operator PJSC MegaFon
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 MEGAFON-RIPE-MNT