MF-VLG-FIX

BGP inherited
Cluster stats
Netblocks7 · 1,401 IPv4 addresses
All fragments 19 blocks across 3 clusters
Cluster ID210031263
RegistryRIPE
Customersfind customers using 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

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
31.173.139.0/24 MF-VLG-FIX RIPE ASSIGNED PA ● low
31.173.188.0/24 MF-VLG-FIX RIPE ASSIGNED PA ● low
31.173.189.0/24 MF-VLG-FIX RIPE ASSIGNED PA ● low
37.29.7.128/25 MF-VLG-FIX RIPE ASSIGNED PA ● low
37.29.97.0/24 MF-VLG-FIX RIPE ASSIGNED PA ● low
37.29.98.0/25 MF-VLG-FIX RIPE ASSIGNED PA ● low
37.29.98.128/25 MF-VLG-FIX RIPE ASSIGNED PA ● low

Possibly related to this organisation

what's this?
Same name family
Separately-registered clusters whose names share “MF VLG” — 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: A how networks compare →
100.0% of checked blocks have valid RPKI ROA coverage (7 of 7)
Possible discrepancies (4)

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

37.29.97.0/24 /24 authorized for AS31133 — PJSC MegaFon
31.173.188.0/24 /24 authorized for AS31133 — PJSC MegaFon
31.173.189.0/24 /24 authorized for AS31133 — PJSC MegaFon
31.173.139.0/24 /24 authorized for AS31133 — PJSC MegaFon

NIC Handles

DUMY-RIPE DUMY-RIPE MEGAFON-AUTO-MNT MF-VLG-MNT