Evolix
Cluster stats
| Netblocks | 5 |
| All fragments | 21 blocks across 2 clusters |
| Cluster ID | 193383986 |
| Registry | PEERINGDB |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | unresolved |
| Shared handles | clustered on 4 shared RIR contact/maintainer handles |
| Registry names | 2 distinct registrant names across these blocks |
| full provenance (JSON) → · how attribution works | |
IP Ranges (5)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 37.49.232.15/32 | Evolix | PEERINGDB | ASSIGNED | ● high |
| 37.49.237.58/32 | Evolix | PEERINGDB | ASSIGNED | ● high |
| 2001:7f8:54::1:58/128 | Evolix | PEERINGDB | ASSIGNED | ● high |
| 2001:7f8:54:5::15/128 | Evolix | PEERINGDB | ASSIGNED | ● high |
| 2a02:2178:1000:100::/56 | EVOLIX | RIPE | ASSIGNED | ● low |
Network trust
what's this?
RPKI hygiene: A
how networks compare →
100.0%
of checked blocks have valid RPKI ROA coverage
(5 of 5)
Possible discrepancies (1)
These blocks are registered to Evolix 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.
| 2a02:2178:1000:100::/56 /56 | authorized for AS29075 — IELO-LIAZO SERVICES SAS |
NIC Handles
AS197696
DUMY-RIPE
DUMY-RIPE
IELO-MNT