UNI-MB-VE-FE-NET
Cluster stats
| Netblocks | 4 |
| All fragments | 5 blocks across 2 clusters |
| Cluster ID | 193456985 |
| Registry | RIPE |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | unresolved |
| Shared handles | clustered on 3 shared RIR contact/maintainer handles |
| Registry names | 1 distinct registrant name across these blocks |
| full provenance (JSON) → · how attribution works | |
IP Ranges (4)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 178.172.4.64/27 | UNI-MB-VE-FE-NET | RIPE | ASSIGNED PA | ● low |
| 178.172.5.128/26 | UNI-MB-VE-FE-NET | RIPE | ASSIGNED PA | ● low |
| 194.249.165.48/29 | UNI-MB-VE-FE-NET | RIPE | ASSIGNED PA | ● low |
| 2001:1470:fc51::/48 | UNI-MB-VE-FE-NET | RIPE | ASSIGNED | ● low |
Network trust
what's this?
RPKI hygiene: A
how networks compare →
100.0%
of checked blocks have valid RPKI ROA coverage
(4 of 4)
Possible discrepancies (1)
These blocks are registered to UNI-MB-VE-FE-NET but cryptographically authorized for a different, unrelated network (1 distinct holder) — often M&A history, multi-homing, or outsourced/managed hosting, occasionally worth a closer look.
| 2001:1470:fc51::/48 /48 | authorized for AS2107 — ARNES |
NIC Handles
ARNES-MNT
DUMY-RIPE
DUMY-RIPE