MF-MC-19072022
Cluster stats
Netblocks12
All fragments 55 blocks across 18 clusters
Cluster ID192743967
RegistryRIPE
Customersfind customers using this network →
Evidence & provenance ?
Attribution unresolved
Shared handles clustered on 4 shared RIR contact/maintainer handles
Registry names 1 distinct registrant name across these blocks
full provenance (JSON) → · how attribution works

IP Ranges (12)

⬇ export CSV
CIDR Org name Registry Status Confidence
31.173.147.0/25 MF-MC-19072022 RIPE ASSIGNED PA ● low
31.173.147.128/25 MF-MC-19072022 RIPE ASSIGNED PA ● low
31.173.157.0/24 MF-MC-19072022 RIPE ASSIGNED PA ● low
31.173.174.0/24 MF-MC-19072022 RIPE ASSIGNED PA ● low
31.173.175.0/24 MF-MC-19072022 RIPE ASSIGNED PA ● low
37.29.6.0/24 MF-MC-19072022 RIPE ASSIGNED PA ● low
85.26.170.192/28 MF-MC-19072022 RIPE ASSIGNED PA ● low
85.26.173.128/27 MF-MC-19072022 RIPE ASSIGNED PA ● low
178.176.142.0/24 MF-MC-19072022 RIPE ASSIGNED PA ● low
178.176.143.0/24 MF-MC-19072022 RIPE ASSIGNED PA ● low
178.176.145.0/24 MF-MC-19072022 RIPE ASSIGNED PA ● low
178.176.152.0/23 MF-MC-19072022 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 (12 of 12)
Possible discrepancies (8)

These blocks are registered to MF-MC-19072022 but cryptographically authorized for a different, unrelated network (1 distinct holder) — often M&A history, multi-homing, or outsourced/managed hosting, occasionally worth a closer look.

178.176.152.0/23 /23 authorized for AS31133 — PJSC MegaFon
178.176.142.0/24 /24 authorized for AS31133 — PJSC MegaFon
178.176.143.0/24 /24 authorized for AS31133 — PJSC MegaFon
178.176.145.0/24 /24 authorized for AS31133 — PJSC MegaFon
37.29.6.0/24 /24 authorized for AS31133 — PJSC MegaFon
31.173.157.0/24 /24 authorized for AS31133 — PJSC MegaFon
31.173.174.0/24 /24 authorized for AS31133 — PJSC MegaFon
31.173.175.0/24 /24 authorized for AS31133 — PJSC MegaFon

NIC Handles

DUMY-RIPE DUMY-RIPE MEGAFON-AUTO-MNT MF-FCURP-MNT