MF-GDC-CENTER

Data as of 2026-07-26
BGP inherited
Cluster stats
Netblocks5 · 1,280 IPv4 addresses
All fragments 142 blocks across 49 clusters
Cluster ID215967467
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

IP Ranges (5)

⬇ export CSV
CIDR Org name Registry Status Confidence
178.178.80.0/22 MF-GDC-CENTER RIPE LIR-PARTITIONED PA ● low
178.178.83.0/24 MF-GDC-CENTER RIPE ASSIGNED PA ● low
188.170.58.0/24 MF-GDC-CENTER RIPE LIR-PARTITIONED PA ● low
188.170.58.0/25 MF-GDC-CENTER RIPE ASSIGNED PA ● low
188.170.58.128/25 MF-GDC-CENTER 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 (5 of 5)
Possible discrepancies (3)

These blocks are registered to MF-GDC-CENTER 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.178.80.0/22 /22 authorized for AS31133 — PJSC MegaFon
188.170.58.0/24 /24 authorized for AS31133 — PJSC MegaFon
178.178.83.0/24 /24 authorized for AS31133 — PJSC MegaFon

NIC Handles

DUMY-RIPE DUMY-RIPE GDC-TR-CoreIP MEGAFON-AUTO-MNT MEGAFON-RIPE-MNT