MF-UGSM

BGP inherited
Cluster stats
Netblocks9 · 4,087 IPv4 addresses
All fragments 10 blocks across 2 clusters
Cluster ID209030434
RegistryRIPE
Customersfind customers using this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
Shared handles clustered on 6 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
31.173.99.0/24 MF-UGSM RIPE ASSIGNED PA ● low
31.173.121.0/24 MF-UGSM RIPE ASSIGNED PA ● low
37.29.44.0/23 MF-UGSM RIPE ASSIGNED PA ● low
37.29.46.0/24 MF-UGSM RIPE ASSIGNED PA ● low
37.29.47.0/24 MF-UGSM RIPE ASSIGNED PA ● low
78.109.122.0/24 MF-UGSM RIPE ASSIGNED PA ● low
78.109.127.0/24 MF-UGSM RIPE ASSIGNED PA ● low
83.149.32.0/22 MF-UGSM RIPE ASSIGNED PA ● low
83.149.36.0/22 MF-UGSM 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-AUTO-MNT MEGAFON-RIPE-MNT MF-UGSM-MNT