MF-STF-21062023
Cluster stats
| Netblocks | 18 |
| All fragments | 45 blocks across 19 clusters |
| Cluster ID | 192912634 |
| 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 (18)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 31.173.32.0/20 | MF-STF-21062023 | RIPE | SUB-ALLOCATED PA | ● low |
| 31.173.48.0/20 | MF-STF-21062023 | RIPE | SUB-ALLOCATED PA | ● low |
| 31.173.72.0/22 | MF-STF-21062023 | RIPE | SUB-ALLOCATED PA | ● low |
| 31.173.76.0/22 | MF-STF-21062023 | RIPE | SUB-ALLOCATED PA | ● low |
| 31.173.88.0/22 | MF-STF-21062023 | RIPE | SUB-ALLOCATED PA | ● low |
| 31.173.92.0/22 | MF-STF-21062023 | RIPE | SUB-ALLOCATED PA | ● low |
| 78.25.112.0/23 | MF-STF-21062023 | RIPE | SUB-ALLOCATED PA | ● low |
| 78.25.114.0/23 | MF-STF-21062023 | RIPE | SUB-ALLOCATED PA | ● low |
| 78.25.118.0/24 | MF-STF-21062023 | RIPE | SUB-ALLOCATED PA | ● low |
| 78.25.119.0/24 | MF-STF-21062023 | RIPE | SUB-ALLOCATED PA | ● low |
| 85.26.144.0/21 | MF-STF-21062023 | RIPE | SUB-ALLOCATED PA | ● low |
| 85.26.152.0/21 | MF-STF-21062023 | RIPE | SUB-ALLOCATED PA | ● low |
| 178.177.0.0/19 | MF-STF-21062023 | RIPE | SUB-ALLOCATED PA | ● low |
| 178.177.32.0/19 | MF-STF-21062023 | RIPE | SUB-ALLOCATED PA | ● low |
| 188.170.0.0/20 | MF-STF-21062023 | RIPE | SUB-ALLOCATED PA | ● low |
| 188.170.16.0/21 | MF-STF-21062023 | RIPE | SUB-ALLOCATED PA | ● low |
| 188.170.28.0/23 | MF-STF-21062023 | RIPE | SUB-ALLOCATED PA | ● low |
| 188.170.30.0/23 | MF-STF-21062023 | RIPE | SUB-ALLOCATED PA | ● low |
Network trust
what's this?
RPKI hygiene: A
how networks compare →
100.0%
of checked blocks have valid RPKI ROA coverage
(18 of 18)
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