Announced routes
Every prefix a peer of the route collectors sees with origin AS397349, 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.
| 2a10:ac40:3::/48 | No ROA | None | 16 3%low visibility |
| 23.129.208.0/24 | No ROA | RIR databaseARIN | 670 100% |
AS-SET
AS397349'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 5 are in fix.csv.
- ROA: none2
- Route object: none1
- Route object: not announced2
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 2a10:ac40:3::/48 | No ROA covers it. Add a ROA for AS397349, maxLength 48. |
| Route object: none | 2a10:ac40:3::/48 | No route object for it. Add a route object with origin AS397349 in the RIR database for the space. |
| ROA: none | 23.129.208.0/24 | No ROA covers it. Add a ROA for AS397349, maxLength 24. |
Route objects not announced
Route objects with origin AS397349 whose prefix no peer sees AS397349 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 2620:13e:a000::/40 | ARIN | No ROA |
| 2620:13e:a000::/48 | ARIN | 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.