Announced routes
Every prefix a peer of the route collectors sees with origin AS197904, 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.
| 44.30.134.0/24 | No ROA | Other IRR onlyRADB | 2 0%low visibility |
| 44.32.162.0/24 | No ROA | Other IRR onlyRADB | 2 0%low visibility |
AS-SET
AS197904'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 6 are in fix.csv.
- ROA: none2
- Route object: RIR2
- Route object: not announced2
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 44.30.134.0/24 | No ROA covers it. Add a ROA for AS197904, maxLength 24. |
| Route object: RIR | 44.30.134.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 44.32.162.0/24 | No ROA covers it. Add a ROA for AS197904, maxLength 24. |
| Route object: RIR | 44.32.162.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS197904 whose prefix no peer sees AS197904 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 2a06:9801:2bf::/48 | RIPE | Valid |
| 2a06:9801:720::/44 | RIPE | 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.