IX-Denver Route Servers
Data as of 2026-07-26
BGP inherited
Cluster stats
| Netblocks | 4 |
| IPv6 | 2 prefixes (largest 2001:504:58::5/128) |
| All fragments | 8 blocks across 3 clusters |
| Cluster ID | 214584604 |
| Registry | PEERINGDB |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | BGP parent (inherited) |
| 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 · report an issue | |
Footprint over time
5 weekly snapshots · JSON
8
0 netblocks since 2026-07-05
2026-07-05
peak 8
2026-07-19
IP Ranges (4)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 206.53.175.5/32 | IX-Denver Route Servers | PEERINGDB | ASSIGNED | ● high |
| 206.53.175.7/32 | IX-Denver Route Servers | PEERINGDB | ASSIGNED | ● high |
| 2001:504:58::5/128 | IX-Denver Route Servers | PEERINGDB | ASSIGNED | ● high |
| 2001:504:58::7/128 | IX-Denver Route Servers | PEERINGDB | ASSIGNED | ● high |
IPv6 ranges (2)
Network trust
what's this?
RPKI hygiene: A
how networks compare →
100.0%
of checked blocks have valid RPKI ROA coverage
(4 of 4)
No discrepancies found among checked blocks.
NIC Handles
AS394594