Mpu Communications
Cluster stats
| Netblocks | 21 |
| All fragments | 25 blocks across 2 clusters |
| Cluster ID | 191823538 |
| Registry | PEERINGDB |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | unresolved |
| Shared handles | clustered on 6 shared RIR contact/maintainer handles |
| Registry names | 3 distinct registrant names across these blocks |
| full provenance (JSON) → · how attribution works | |
IP Ranges (21)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 196.60.10.182/32 | Mpu Communications | PEERINGDB | ASSIGNED | ● high |
| 80.188.50.216/29 | MPU-NET | RIPE | ASSIGNED PA | ● low |
| 80.188.94.144/29 | MPU | RIPE | ASSIGNED PA | ● low |
| 89.249.98.52/32 | MPU | RIPE | ASSIGNED PA | ● low |
| 89.249.99.128/27 | MPU | RIPE | ASSIGNED PA | ● low |
| 89.249.100.52/32 | MPU | RIPE | ASSIGNED PA | ● low |
| 89.249.100.78/32 | MPU | RIPE | ASSIGNED PA | ● low |
| 89.249.100.100/32 | MPU | RIPE | ASSIGNED PA | ● low |
| 89.249.105.48/28 | MPU | RIPE | ASSIGNED PA | ● low |
| 89.249.106.0/27 | MPU | RIPE | ASSIGNED PA | ● low |
| 89.249.106.80/28 | MPU | RIPE | ASSIGNED PA | ● low |
| 89.249.106.112/28 | MPU | RIPE | ASSIGNED PA | ● low |
| 89.249.106.128/28 | MPU | RIPE | ASSIGNED PA | ● low |
| 89.249.107.16/28 | MPU | RIPE | ASSIGNED PA | ● low |
| 89.249.107.48/28 | MPU | RIPE | ASSIGNED PA | ● low |
| 89.249.107.80/28 | MPU | RIPE | ASSIGNED PA | ● low |
| 89.249.107.192/28 | MPU | RIPE | ASSIGNED PA | ● low |
| 89.249.108.96/28 | MPU | RIPE | ASSIGNED PA | ● low |
| 89.249.108.120/30 | MPU | RIPE | ASSIGNED PA | ● low |
| 89.249.109.0/24 | MPU | RIPE | ASSIGNED PA | ● low |
| 90.181.170.8/29 | MPU | RIPE | ASSIGNED PA | ● low |
Network trust
what's this?
RPKI hygiene: F
how networks compare →
19.0%
of checked blocks have valid RPKI ROA coverage
(4 of 21)
No discrepancies found among checked blocks.
NIC Handles
AS328912
AS5610-MTN
DUMY-RIPE
DUMY-RIPE
MNT-ROUTING
MNT-TDU_IP