MF-GDC-KF
Data as of 2026-09-13
BGP inherited
This organisation
| Netblocks | 4 · 6,146 IPv4 addresses |
| Also registered under this name | 10 netblocks across 4 separate records |
| Record ID | 240995810 |
| Registry | RIPE |
| Customers | see who runs inside 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 (4)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 188.170.168.0/21 | MF-GDC-KF | RIPE | ASSIGNED PA | ● low |
| 188.170.192.0 – 188.170.199.0 | MF-GDC-KF | RIPE | ASSIGNED PA | ● low |
| 188.170.200.0 – 188.170.207.0 | MF-GDC-KF | RIPE | ASSIGNED PA | ● low |
| 188.170.224.0/23 | MF-GDC-KF | 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
(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
GDC-TR-CoreIP
MEGAFON-AUTO-MNT
MEGAFON-RIPE-MNT