MF-GDC-20220705-T4117508

Data as of 2026-07-26
BGP inherited
Cluster stats
Netblocks6 · 5,120 IPv4 addresses
All fragments 142 blocks across 49 clusters
Cluster ID214501670
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 · report an issue

Footprint over time

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

IP Ranges (6)

⬇ export CSV
CIDR Org name Registry Status Confidence
83.149.24.0/21 MF-GDC-20220705-T4117508 RIPE LIR-PARTITIONED PA ● low
83.169.232.0/22 MF-GDC-20220705-T4117508 RIPE LIR-PARTITIONED PA ● low
83.169.232.0/23 MF-GDC-20220705-T4117508 RIPE ASSIGNED PA ● low
83.169.234.0/23 MF-GDC-20220705-T4117508 RIPE ASSIGNED PA ● low
85.26.176.0/22 MF-GDC-20220705-T4117508 RIPE ASSIGNED PA ● low
85.26.188.0/22 MF-GDC-20220705-T4117508 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 (6 of 6)
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