MF-SF-FIX-20220826

BGP inherited
Cluster stats
Netblocks4
All fragments 17 blocks across 11 clusters
Cluster ID205692671
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

IP Ranges (4)

⬇ export CSV
CIDR Org name Registry Status Confidence
188.170.248.0/24 MF-SF-FIX-20220826 RIPE ASSIGNED PA ● low
188.170.249.0/24 MF-SF-FIX-20220826 RIPE ASSIGNED PA ● low
188.170.250.0/24 MF-SF-FIX-20220826 RIPE ASSIGNED PA ● low
188.170.251.0/24 MF-SF-FIX-20220826 RIPE ASSIGNED PA ● low

Possibly related to this organisation

what's this?
Same name family
Separately-registered clusters whose names share “MF SF” — often per-country or per-system registrations of the same brand, occasionally a different organisation sharing the name. Not counted in this organisation's own footprint.
Combined view of all 11 name-family clusters →

Network trust

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