MF-SF-Mobile-Subscribers
Data as of 2026-11-01
BGP inherited
This organisation
| Netblocks | 2 |
| IPv6 | 2 prefixes (largest 2a03:d000:6500::/40) |
| Also registered under this name | 17 netblocks across 11 separate records |
| Record ID | 259509203 |
| Registry | RIPE |
| Customers | see who runs inside 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 · report an issue | |
IP Ranges (2)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 2a03:d000:6500::/40 | MF-SF-Mobile-Subscribers | RIPE | ASSIGNED | ● low |
| 2a03:d000:6600::/40 | MF-SF-Mobile-Subscribers | RIPE | ASSIGNED | ● low |
IPv6 ranges (2)
Network trust
what's this?
RPKI hygiene: C
how networks compare →
50.0%
of checked blocks have valid RPKI ROA coverage
(1 of 2)
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