Announced routes
Every prefix a peer of the route collectors sees with origin AS198490, 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.
| 176.108.128.0/21 | No ROA | RIR databaseRIPE | 671 100% |
AS-SET
AS198490'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 2 are in fix.csv.
- ROA: none1
- Route object: not announced1
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 176.108.128.0/21 | No ROA covers it. Add a ROA for AS198490, maxLength 21. |
Route objects not announced
Route objects with origin AS198490 whose prefix no peer sees AS198490 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 2a10:f781:10:53cc::/64 | 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.