LOCIX Route Servers
Cluster stats
| Netblocks | 10 |
| All fragments | 70 blocks across 5 clusters |
| Cluster ID | 193385605 |
| Registry | PEERINGDB |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | unresolved |
| Shared handles | clustered on 1 shared RIR contact/maintainer handle |
| Registry names | 1 distinct registrant name across these blocks |
| full provenance (JSON) → · how attribution works | |
Footprint over time
2 weekly snapshots · JSON
10
0 netblocks since 2026-07-05
2026-07-05
peak 10
2026-07-06
IP Ranges (10)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 185.1.155.253/32 | LOCIX Route Servers | PEERINGDB | ASSIGNED | ● high |
| 185.1.155.254/32 | LOCIX Route Servers | PEERINGDB | ASSIGNED | ● high |
| 185.1.166.100/32 | LOCIX Route Servers | PEERINGDB | ASSIGNED | ● high |
| 185.1.166.200/32 | LOCIX Route Servers | PEERINGDB | ASSIGNED | ● high |
| 185.1.166.254/32 | LOCIX Route Servers | PEERINGDB | ASSIGNED | ● high |
| 2001:7f8:f2:e1::be5a/128 | LOCIX Route Servers | PEERINGDB | ASSIGNED | ● high |
| 2001:7f8:f2:e1::babe:1/128 | LOCIX Route Servers | PEERINGDB | ASSIGNED | ● high |
| 2001:7f8:f2:e1::dead:1/128 | LOCIX Route Servers | PEERINGDB | ASSIGNED | ● high |
| 2a0c:b641:701:0:a5:20:2409:1/128 | LOCIX Route Servers | PEERINGDB | ASSIGNED | ● high |
| 2a0c:b641:701:0:a5:20:2409:2/128 | LOCIX Route Servers | PEERINGDB | ASSIGNED | ● high |
Network trust
what's this?
RPKI hygiene: B
how networks compare →
80.0%
of checked blocks have valid RPKI ROA coverage
(8 of 10)
No discrepancies found among checked blocks.
NIC Handles
AS202409