MF-SF-Mobile-Subscribers
BGP inherited
Cluster stats
| Netblocks | 2 |
| All fragments | 17 blocks across 11 clusters |
| Cluster ID | 206118894 |
| Registry | RIPE |
| Customers | find customers using 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 | |
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 |
Possibly related to this organisation
what's this?Same name family
Separately-registered clusters whose names share “MF SF” — often
per-country or per-system registrations of the same brand, occasionally a different
organisation sharing the name. Not counted in this organisation's own footprint.
- MF-SF-FIX-20220826 4 blocks
- MF-SF-20220825-T4168189 3 blocks
- MF-SF-AS31205-MOB 1 blocks
- MF-SF-AS50928-FIX 1 blocks
- MF-SF-MOB 1 blocks
- MF-SF-GDC 1 blocks
- MF-SF-T4221511 1 blocks
- MF-SF-AS31205-MOB-TOL 1 blocks
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