MF-MOSCOW-BBA-20220424-T4104128
Cluster stats
Netblocks6
All fragments 19 blocks across 13 clusters
Cluster ID192737938
RegistryRIPE
Customersfind customers using this network →
Evidence & provenance ?
Attribution unresolved
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

IP Ranges (6)

⬇ export CSV
CIDR Org name Registry Status Confidence
62.64.0.0/21 MF-MOSCOW-BBA-20220424-T4104128 RIPE ASSIGNED PA ● low
62.64.8.0/21 MF-MOSCOW-BBA-20220424-T4104128 RIPE ASSIGNED PA ● low
83.222.212.0/22 MF-MOSCOW-BBA-20220424-T4104128 RIPE ASSIGNED PA ● low
83.222.216.0/21 MF-MOSCOW-BBA-20220424-T4104128 RIPE ASSIGNED PA ● low
195.16.112.0/23 MF-MOSCOW-BBA-20220424-T4104128 RIPE LIR-PARTITIONED PA ● low
195.16.116.0/22 MF-MOSCOW-BBA-20220424-T4104128 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 MEGAFON-AUTO-MNT MEGAFON-RIPE-MNT MF-MOSCOW-MNT