MF-MGSM

BGP inherited
Cluster stats
Netblocks9 · 9,207 IPv4 addresses
Cluster ID209551705
RegistryRIPE
Customersfind customers using this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
Shared handles clustered on 5 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
46.232.204.0/22 MF-MGSM RIPE LIR-PARTITIONED PA ● low
78.25.75.0/24 MF-MGSM RIPE ASSIGNED PA ● low
78.25.76.0/24 MF-MGSM RIPE ASSIGNED PA ● low
78.25.77.0/24 MF-MGSM RIPE ASSIGNED PA ● low
83.149.16.0/24 MF-MGSM RIPE LIR-PARTITIONED PA ● low
83.169.192.0/21 MF-MGSM RIPE LIR-PARTITIONED PA ● low
85.26.160.0/22 MF-MGSM RIPE LIR-PARTITIONED PA ● low
85.26.168.0/21 MF-MGSM RIPE LIR-PARTITIONED PA ● low
188.162.192.0/21 MF-MGSM 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 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 GDC-TR-CoreIP MEGAFON-RIPE-MNT MF-FCURP-MNT