Announced routes
Every prefix a peer of the route collectors sees with origin AS64488, 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.
| 92.60.52.0/22 | No ROA | RIR databaseRIPE | 673 100% |
| 185.162.76.0/22 | No ROA | RIR databaseRIPE | 673 100% |
| 2a0b:4000::/29 | No ROA | RIR databaseRIPE | 634 100% |
| 85.248.78.0/24 | Valid | None | 671 100% |
AS-SET
AS64488'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 8 are in fix.csv.
- ROA: none3
- Route object: none1
- Route object: not announced4
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 92.60.52.0/22 | No ROA covers it. Add a ROA for AS64488, maxLength 22. |
| ROA: none | 185.162.76.0/22 | No ROA covers it. Add a ROA for AS64488, maxLength 22. |
| ROA: none | 2a0b:4000::/29 | No ROA covers it. Add a ROA for AS64488, maxLength 29. |
| Route object: none | 85.248.78.0/24 | No route object for it. Add a route object with origin AS64488 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS64488 whose prefix no peer sees AS64488 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 185.162.76.0/24 | RIPE | No ROA |
| 185.162.77.0/28 | RIPE | No ROA |
| 185.162.78.0/24 | RIPE | No ROA |
| 185.162.78.0/28 | 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.