Network · data from 2026-11-12
AS4997 AFS-WEST - Zayo Bandwidth
Registry name: AFS-WEST - Zayo Bandwidth, US · not in PeeringDB
26IPv4 routes
100.0% RPKI valid · 11.5% with a route object
0IPv6 routes
0RPKI invalid
0 origin · 0 maxLength
0No ROA
23 with no route object for this origin
0Low visibility
seen by under 10% of full-table peers
1Route objects not announced
registered with origin AS4997, seen from no peer
Announced routes
Every prefix a peer of the route collectors sees with origin AS4997, 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.
| 208.39.192.0/23 | Valid | None | 673 100% |
| 208.39.194.0/23 | Valid | None | 673 100% |
| 208.39.196.0/22 | Valid | None | 673 100% |
| 208.39.199.0/24 | Valid | None | 673 100% |
| 208.39.218.0/24 | Valid | None | 673 100% |
| 208.39.222.0/24 | Valid | None | 673 100% |
| 208.39.224.0/22 | Valid | None | 673 100% |
| 208.39.232.0/21 | Valid | None | 673 100% |
| 208.39.248.0/22 | Valid | None | 673 100% |
| 208.39.249.0/24 | Valid | None | 673 100% |
| 208.39.252.0/22 | Valid | None | 673 100% |
| 208.39.255.0/24 | Valid | None | 673 100% |
| 216.222.0.0/20 | Valid | None | 673 100% |
| 216.222.24.0/22 | Valid | None | 673 100% |
| 216.222.32.0/23 | Valid | None | 673 100% |
| 216.222.36.0/22 | Valid | None | 673 100% |
| 216.222.40.0/21 | Valid | None | 673 100% |
| 216.222.48.0/20 | Valid | None | 673 100% |
| 208.39.228.0/24 | Valid | None | 672 100% |
| 208.39.229.0/24 | Valid | None | 672 100% |
| 208.39.247.0/24 | Valid | None | 672 100% |
| 216.222.13.0/24 | Valid | None | 672 100% |
| 216.222.101.0/24 | Valid | None | 672 100% |
| 208.39.246.0/24 | Valid | Other IRR onlyBBOI | 673 100% |
| 216.222.90.0/23 | Valid | RIR databaseARIN | 673 100% |
| 216.222.92.0/23 | Valid | RIR databaseARIN | 673 100% |
AS-SET
AS4997 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 25 are in fix.csv.
- Route object: none23
- Route object: RIR1
- Route object: not announced1
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 208.39.192.0/23 | No route object for it. Add a route object with origin AS4997 in the RIR database for the space. |
| Route object: none | 208.39.194.0/23 | No route object for it. Add a route object with origin AS4997 in the RIR database for the space. |
| Route object: none | 208.39.196.0/22 | No route object for it. Add a route object with origin AS4997 in the RIR database for the space. |
| Route object: none | 208.39.199.0/24 | No route object for it. Add a route object with origin AS4997 in the RIR database for the space. |
| Route object: none | 208.39.218.0/24 | No route object for it. Add a route object with origin AS4997 in the RIR database for the space. |
| Route object: none | 208.39.222.0/24 | No route object for it. Add a route object with origin AS4997 in the RIR database for the space. |
| Route object: none | 208.39.224.0/22 | No route object for it. Add a route object with origin AS4997 in the RIR database for the space. |
| Route object: none | 208.39.232.0/21 | No route object for it. Add a route object with origin AS4997 in the RIR database for the space. |
| Route object: none | 208.39.248.0/22 | No route object for it. Add a route object with origin AS4997 in the RIR database for the space. |
| Route object: none | 208.39.249.0/24 | No route object for it. Add a route object with origin AS4997 in the RIR database for the space. |
| Route object: none | 208.39.252.0/22 | No route object for it. Add a route object with origin AS4997 in the RIR database for the space. |
| Route object: none | 208.39.255.0/24 | No route object for it. Add a route object with origin AS4997 in the RIR database for the space. |
| Route object: none | 216.222.0.0/20 | No route object for it. Add a route object with origin AS4997 in the RIR database for the space. |
| Route object: none | 216.222.24.0/22 | No route object for it. Add a route object with origin AS4997 in the RIR database for the space. |
| Route object: none | 216.222.32.0/23 | No route object for it. Add a route object with origin AS4997 in the RIR database for the space. |
| Route object: none | 216.222.36.0/22 | No route object for it. Add a route object with origin AS4997 in the RIR database for the space. |
| Route object: none | 216.222.40.0/21 | No route object for it. Add a route object with origin AS4997 in the RIR database for the space. |
| Route object: none | 216.222.48.0/20 | No route object for it. Add a route object with origin AS4997 in the RIR database for the space. |
| Route object: none | 208.39.228.0/24 | No route object for it. Add a route object with origin AS4997 in the RIR database for the space. |
| Route object: none | 208.39.229.0/24 | No route object for it. Add a route object with origin AS4997 in the RIR database for the space. |
| Route object: none | 208.39.247.0/24 | No route object for it. Add a route object with origin AS4997 in the RIR database for the space. |
| Route object: none | 216.222.13.0/24 | No route object for it. Add a route object with origin AS4997 in the RIR database for the space. |
| Route object: none | 216.222.101.0/24 | No route object for it. Add a route object with origin AS4997 in the RIR database for the space. |
| Route object: RIR | 208.39.246.0/24 | Route object only in BBOI. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS4997 whose prefix no peer sees AS4997 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 216.222.120.0/22 | BBOI | Invalid: origin |
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.