Announced routes
Every prefix a peer of the route collectors sees with origin AS31459, 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.
| 132.185.224.0/20 | No ROA | RIR databaseRIPE | 358 53% |
| 193.41.0.0/23 | No ROA | RIR databaseRIPE | 358 53% |
| 192.190.44.0/24 | No ROA | RIR databaseRIPE | 357 53% |
| 193.130.40.0/23 | No ROA | RIR databaseRIPE | 357 53% |
AS-SET
AS31459'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: none4
- Route object: not announced1
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 132.185.224.0/20 | No ROA covers it. Add a ROA for AS31459, maxLength 20. |
| ROA: none | 193.41.0.0/23 | No ROA covers it. Add a ROA for AS31459, maxLength 23. |
| ROA: none | 192.190.44.0/24 | No ROA covers it. Add a ROA for AS31459, maxLength 24. |
| ROA: none | 193.130.40.0/23 | No ROA covers it. Add a ROA for AS31459, maxLength 23. |
Route objects not announced
Route objects with origin AS31459 whose prefix no peer sees AS31459 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 2001:41c0:8000::/33 | 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.