Announced routes
Every prefix a peer of the route collectors sees with origin AS394545, 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.
| 160.19.162.0/24 | No ROA | Other IRR onlyRADB | 671 100% |
| 185.157.66.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 185.157.64.0/24 | No ROA | RIR databaseRIPE | 671 100% |
| 185.157.65.0/24 | No ROA | RIR databaseRIPE | 671 100% |
AS-SET
AS394545's PeeringDB record names no 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 10 are in fix.csv.
- ROA: none4
- Route object: RIR1
- Route object: not announced5
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 160.19.162.0/24 | No ROA covers it. Add a ROA for AS394545, maxLength 24. |
| Route object: RIR | 160.19.162.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 185.157.66.0/24 | No ROA covers it. Add a ROA for AS394545, maxLength 24. |
| ROA: none | 185.157.64.0/24 | No ROA covers it. Add a ROA for AS394545, maxLength 24. |
| ROA: none | 185.157.65.0/24 | No ROA covers it. Add a ROA for AS394545, maxLength 24. |
Route objects not announced
Route objects with origin AS394545 whose prefix no peer sees AS394545 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 160.19.163.0/24 | RADB | No ROA |
| 185.157.64.0/22 | RIPE | No ROA |
| 185.157.67.0/24 | RIPE | No ROA |
| 2001:470:20a::/48 | ARIN | Valid |
| 2a07:a540::/29 | RIPE | 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.