Network · data from 2026-11-12
AS13555 EAGLE-NET-ALLIANCE - Zayo Bandwidth
Registry name: EAGLE-NET-ALLIANCE - Zayo Bandwidth, US · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS13555, things to look at first. Visibility = full-table peers that see it, of 673 (IPv4) and 636 (IPv6) on 75 collectors. Also as routes.csv.
| 67.230.192.0/20 | Valid | Other IRR onlyRADB | 673 100% |
| 97.107.64.0/20 | Valid | Other IRR onlyRADB | 673 100% |
| 199.127.132.0/22 | Valid | Other IRR onlyRADB | 673 100% |
| 199.168.84.0/22 | Valid | Other IRR onlyRADB | 673 100% |
AS-SET
AS13555 isn't in PeeringDB, where networks name their AS-SET.
Fix list
The changes that would bring RPKI, the IRR and what's announced into line. Some are deliberate (a route object kept for a backup route, say); the network decides. All 16 are in fix.csv.
- Route object: RIR4
- Route object: not announced12
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: RIR | 67.230.192.0/20 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 97.107.64.0/20 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 199.127.132.0/22 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 199.168.84.0/22 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS13555 whose prefix no peer sees AS13555 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 63.238.208.0/22 | RADB | No ROA |
| 63.238.212.0/24 | RADB | No ROA |
| 204.131.172.0/24 | RADB | No ROA |
| 205.168.64.0/22 | RADB | No ROA |
| 205.168.94.0/23 | RADB | No ROA |
| 205.168.189.0/24 | RADB | No ROA |
| 205.168.190.0/23 | RADB | No ROA |
| 205.168.208.0/23 | RADB | No ROA |
| 205.168.210.0/24 | RADB | No ROA |
| 205.168.217.0/24 | RADB | No ROA |
| 205.168.232.0/23 | RADB | No ROA |
| 205.168.242.0/24 | RADB | No ROA |
Routes: the 08:00 UTC snapshots of 2026-11-12 from 75 RIPE RIS and RouteViews collectors. RPKI: our rpki-client run before the snapshot. IRR: the day's dumps of the five RIR databases and RADB's mirrors. The LEVEL3 and IDNIC databases publish no dump and aren't read, so route objects only there count as none.