MF-SIB
BGP inherited
Cluster stats
| Netblocks | 5 · 2,043 IPv4 addresses |
| All fragments | 17 blocks across 5 clusters |
| Cluster ID | 210032792 |
| Registry | RIPE |
| Customers | find customers using 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 | |
IP Ranges (5)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 37.29.80.0/22 | MF-SIB | RIPE | LIR-PARTITIONED PA | ● low |
| 37.29.80.0/24 | MF-SIB | RIPE | ASSIGNED PA | ● low |
| 37.29.81.0/24 | MF-SIB | RIPE | ASSIGNED PA | ● low |
| 37.29.82.0/24 | MF-SIB | RIPE | ASSIGNED PA | ● low |
| 37.29.83.0/24 | MF-SIB | 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
(5 of 5)
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
MEGAFON-AUTO-MNT
MEGAFON-RIPE-MNT
MF-SIB-MNT