MF-MOSCOW
BGP inherited
Cluster stats
| Netblocks | 3 · 2,046 IPv4 addresses |
| All fragments | 37 blocks across 28 clusters |
| Cluster ID | 210163074 |
| 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 (3)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 37.28.176.0/22 | MF-MOSCOW | RIPE | ASSIGNED PA | ● low |
| 37.28.180.0/22 | MF-MOSCOW | RIPE | ASSIGNED PA | ● low |
| 2a03:d000:4000::/36 | MF-MOSCOW | RIPE | AGGREGATED-BY-LIR | ● low |
Network trust
what's this?
RPKI hygiene: A
how networks compare →
100.0%
of checked blocks have valid RPKI ROA coverage
(3 of 3)
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-MOSCOW-MNT