MF-GDC-20220826

Data as of 2026-09-13
BGP inherited
This organisation
Netblocks10 · 4,094 IPv4 addresses
Also registered under this name 142 netblocks across 49 separate records
Record ID243053290
RegistryRIPE
Customerssee who runs inside this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
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 · report an issue

IP Ranges (10)

⬇ export CSV
CIDR Org name Registry Status Confidence
188.162.144.0/24 MF-GDC-20220826 RIPE ASSIGNED PA ● low
188.162.145.0/24 MF-GDC-20220826 RIPE ASSIGNED PA ● low
188.162.146.0/24 MF-GDC-20220826 RIPE ASSIGNED PA ● low
188.162.147.0/24 MF-GDC-20220826 RIPE ASSIGNED PA ● low
188.162.148.0 – 188.162.151.254 MF-GDC-20220826 RIPE ASSIGNED PA ● low
188.162.152.0 – 188.162.155.254 MF-GDC-20220826 RIPE ASSIGNED PA ● low
188.162.156.0/24 MF-GDC-20220826 RIPE ASSIGNED PA ● low
188.162.157.0/24 MF-GDC-20220826 RIPE ASSIGNED PA ● low
188.162.158.0/24 MF-GDC-20220826 RIPE ASSIGNED PA ● low
188.162.159.0/24 MF-GDC-20220826 RIPE ASSIGNED PA ● low

Footprint over time

12 weekly snapshots · JSON
10 0 netblocks since 2026-07-05
2026-07-05 peak 10 2026-09-13

Network trust

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