MF-MOSCOW-BBA-POOL-178-176-16-0
Cluster stats
| Netblocks | 1 |
| All fragments | 4 blocks across 4 clusters |
| Cluster ID | 195247209 |
| Registry | RIPE |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | unresolved |
| 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 (1)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 178.176.16.0/20 | MF-MOSCOW-BBA-POOL-178-176-16-0 | RIPE | ASSIGNED PA | ● medium |
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
MEGAFON-AUTO-MNT
MEGAFON-RIPE-MNT
MF-MOSCOW-MNT