MF-SF-AS31205-MOB-TOL
BGP inherited
Cluster stats
| Netblocks | 1 · 511 IPv4 addresses |
| All fragments | 3 blocks across 3 clusters |
| Cluster ID | 205008164 |
| Registry | RIPE |
| Customers | find customers using 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 | |
IP Ranges (1)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 31.173.240.0/23 | MF-SF-AS31205-MOB-TOL | RIPE | ASSIGNED PA | ● medium |
Possibly related to this organisation
what's this?Same name family
Separately-registered clusters whose names share “MF SF AS31205 MOB” — 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-AS31205-MOB-PLAN 1 blocks
- MF-SF-AS31205-MOB 1 blocks
Sub-allocations under carriers
IP blocks an ISP reassigned to a similarly-named customer — decoded from the ISP's own
naming convention, not a direct registration.
- As31205 Mob Plan via PJSC MegaFon sub-allocation
- As31205 Mob via PJSC MegaFon sub-allocation
Network trust
what's this?
RPKI hygiene: A
how networks compare →
100.0%
of checked blocks have valid RPKI ROA coverage
(1 of 1)
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-RIPE-MNT