MF-KAVKAZ
Cluster stats
| Netblocks | 24 |
| All fragments | 161 blocks across 10 clusters |
| Cluster ID | 192432554 |
| 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 (24)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 37.29.112.0/20 | MF-KAVKAZ | RIPE | LIR-PARTITIONED PA | ● low |
| 85.26.180.0/22 | MF-KAVKAZ | RIPE | ASSIGNED PA | ● low |
| 85.26.184.0/22 | MF-KAVKAZ | RIPE | ASSIGNED PA | ● low |
| 109.106.192.0 – 109.106.197.255 | MF-KAVKAZ | RIPE | LIR-PARTITIONED PA | ● low |
| 109.106.198.0/24 | MF-KAVKAZ | RIPE | ASSIGNED PA | ● low |
| 178.176.192.0 – 178.176.203.255 | MF-KAVKAZ | RIPE | LIR-PARTITIONED PA | ● low |
| 178.176.204.0/24 | MF-KAVKAZ | RIPE | ASSIGNED PA | ● low |
| 178.176.205.0/24 | MF-KAVKAZ | RIPE | ASSIGNED PA | ● low |
| 178.176.206.0/24 | MF-KAVKAZ | RIPE | ASSIGNED PA | ● low |
| 178.176.207.0/24 | MF-KAVKAZ | RIPE | ASSIGNED PA | ● low |
| 178.176.211.0/24 | MF-KAVKAZ | RIPE | ASSIGNED PA | ● low |
| 178.176.212.0/24 | MF-KAVKAZ | RIPE | ASSIGNED PA | ● low |
| 178.176.213.0/24 | MF-KAVKAZ | RIPE | ASSIGNED PA | ● low |
| 178.176.214.0/24 | MF-KAVKAZ | RIPE | ASSIGNED PA | ● low |
| 178.176.215.0/24 | MF-KAVKAZ | RIPE | ASSIGNED PA | ● low |
| 178.176.216.0/24 | MF-KAVKAZ | RIPE | ASSIGNED PA | ● low |
| 178.176.217.0/24 | MF-KAVKAZ | RIPE | ASSIGNED PA | ● low |
| 178.176.218.0/24 | MF-KAVKAZ | RIPE | ASSIGNED PA | ● low |
| 178.176.219.0/24 | MF-KAVKAZ | RIPE | ASSIGNED PA | ● low |
| 178.176.220.0/24 | MF-KAVKAZ | RIPE | ASSIGNED PA | ● low |
| 178.176.221.0/24 | MF-KAVKAZ | RIPE | ASSIGNED PA | ● low |
| 178.176.222.0/24 | MF-KAVKAZ | RIPE | ASSIGNED PA | ● low |
| 178.176.223.0/24 | MF-KAVKAZ | RIPE | ASSIGNED PA | ● low |
| 2a03:d000:1000::/36 | MF-KAVKAZ | RIPE | AGGREGATED-BY-LIR | ● low |
Network trust
what's this?
RPKI hygiene: A
how networks compare →
95.8%
of checked blocks have valid RPKI ROA coverage
(23 of 24)
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-AUTO-MNT
MEGAFON-RIPE-MNT