Network · data from 2026-11-12
AS16867 BANDWIDTH-CORP - Bandwidth Inc.
Registry name: BANDWIDTH-CORP - Bandwidth Inc., US · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS16867, 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.
| 216.120.128.0/24 | No ROA | RIR databaseARIN, RADB | 673 100% |
| 2620:122:2000::/40 | No ROA | RIR databaseARIN, RADB | 634 100% |
AS-SET
AS16867 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 8 are in fix.csv.
- ROA: none2
- Route object: not announced6
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 216.120.128.0/24 | No ROA covers it. Add a ROA for AS16867, maxLength 24. |
| ROA: none | 2620:122:2000::/40 | No ROA covers it. Add a ROA for AS16867, maxLength 40. |
Route objects not announced
Route objects with origin AS16867 whose prefix no peer sees AS16867 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 216.82.224.0/20 | ARIN | Invalid: origin |
| 216.82.230.0/23 | ARIN | Invalid: origin |
| 216.82.233.0/24 | ARIN, RADB | Valid |
| 216.82.234.0/23 | RADB | Valid |
| 216.82.234.0/24 | ARIN | Valid |
| 2605:7840:2000::/36 | ARIN | 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.