MF-DV-FIX

BGP inherited
Cluster stats
Netblocks7 · 1,017 IPv4 addresses
All fragments 52 blocks across 15 clusters
Cluster ID210174651
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
7 0 netblocks since 2026-07-05
2026-07-05 peak 7 2026-07-19

IP Ranges (7)

⬇ export CSV
CIDR Org name Registry Status Confidence
78.25.127.0/25 MF-DV-FIX RIPE ASSIGNED PA ● low
78.25.127.128/25 MF-DV-FIX RIPE ASSIGNED PA ● low
85.26.246.0/25 MF-DV-FIX RIPE ASSIGNED PA ● low
85.26.246.128/25 MF-DV-FIX RIPE ASSIGNED PA ● low
85.26.247.0/25 MF-DV-FIX RIPE ASSIGNED PA ● low
85.26.247.128/25 MF-DV-FIX RIPE ASSIGNED PA ● low
178.176.235.0/24 MF-DV-FIX RIPE ASSIGNED PA ● low

Possibly related to this organisation

what's this?
Same name family
Separately-registered clusters whose names share “MF DV” — 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.
Combined view of all 15 name-family clusters →

Network trust

what's this?
RPKI hygiene: A how networks compare →
100.0% of checked blocks have valid RPKI ROA coverage (7 of 7)
Possible discrepancies (1)

These blocks are registered to MF-DV-FIX 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.

178.176.235.0/24 /24 authorized for AS31195 — PJSC MegaFon

NIC Handles

DUMY-RIPE DUMY-RIPE MEGAFONDV-RIPE-MNT