Network · data from 2026-11-12
AS396191 ECHOBROADBAND - Echo Broadband, Inc
Registry name: ECHOBROADBAND - Echo Broadband, Inc, US · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS396191, 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.162.217.0/24 | Invalid: maxLength | Nonecovered by 216.162.216.0/21 | 4 1%low visibility |
| 104.254.200.0/22 | Valid | RIR databaseARIN, RADB | 673 100% |
| 172.110.56.0/22 | Valid | RIR databaseARIN, RADB | 673 100% |
| 216.162.216.0/21 | Valid | RIR databaseARIN, RADB | 673 100% |
AS-SET
AS396191 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 3 are in fix.csv.
- ROA: maxLength1
- Route object: none1
- Route object: not announced1
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: maxLength | 216.162.217.0/24 | ROA 216.162.216.0/21 AS396191 has maxLength 21; the route is a /24. Raise the maxLength, or add a ROA for 216.162.217.0/24. |
| Route object: none | 216.162.217.0/24 | No route object for it. A route object for 216.162.216.0/21 with origin AS396191 covers it (filters allowing more-specifics accept it). Add a route object with origin AS396191 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS396191 whose prefix no peer sees AS396191 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 2604:9ec0::/32 | ARIN | Valid |
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.