MF-PF-04082022-T4134712

BGP inherited
Cluster stats
Netblocks7 · 1,785 IPv4 addresses
All fragments 138 blocks across 14 clusters
Cluster ID216053369
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

6 weekly snapshots · JSON
7 0 netblocks since 2026-07-05
2026-07-05 peak 7 2026-07-26

IP Ranges (7)

⬇ export CSV
CIDR Org name Registry Status Confidence
78.25.70.0/24 MF-PF-04082022-T4134712 RIPE LIR-PARTITIONED PA ● low
78.25.71.0/24 MF-PF-04082022-T4134712 RIPE LIR-PARTITIONED PA ● low
78.25.72.0/24 MF-PF-04082022-T4134712 RIPE LIR-PARTITIONED PA ● low
78.25.73.0/24 MF-PF-04082022-T4134712 RIPE LIR-PARTITIONED PA ● low
78.25.74.0/24 MF-PF-04082022-T4134712 RIPE LIR-PARTITIONED PA ● low
78.25.78.0/24 MF-PF-04082022-T4134712 RIPE LIR-PARTITIONED PA ● low
78.25.79.0/24 MF-PF-04082022-T4134712 RIPE LIR-PARTITIONED PA ● low

Network trust

what's this?
RPKI hygiene: A how networks compare →
100.0% of checked blocks have valid RPKI ROA coverage (7 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