Announced routes
Every prefix a peer of the route collectors sees with origin AS397760, 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.
| 134.195.232.0/22 | No ROA | None | 669 99% |
| 134.195.232.0/24 | No ROA | RIR databaseARIN | 669 99% |
AS-SET
AS397760'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 7 are in fix.csv.
- ROA: none2
- Route object: none1
- Route object: not announced4
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 134.195.232.0/22 | No ROA covers it. Add a ROA for AS397760, maxLength 22. |
| Route object: none | 134.195.232.0/22 | No route object for it. Add a route object with origin AS397760 in the RIR database for the space. |
| ROA: none | 134.195.232.0/24 | No ROA covers it. Add a ROA for AS397760, maxLength 24. |
Route objects not announced
Route objects with origin AS397760 whose prefix no peer sees AS397760 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 134.195.233.0/24 | ARIN | No ROA |
| 134.195.234.0/24 | ARIN | No ROA |
| 134.195.235.0/24 | ARIN | No ROA |
| 209.251.134.0/24 | ARIN | Invalid: origin |
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.