Announced routes
Every prefix a peer of the route collectors sees with origin AS216471, 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.
| 38.255.7.0/24 | No ROA | RIR databaseARIN | 672 100% |
| 193.36.94.0/24 | Valid | None | 672 100% |
| 185.179.91.0/24 | Valid | RIR databaseRADB, RIPE | 672 100% |
| 2a13:aa40::/29 | Valid | RIR databaseRIPE | 602 95% |
AS-SET
AS216471'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 3 are in fix.csv.
- ROA: none1
- Route object: none1
- Route object: not announced1
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 38.255.7.0/24 | No ROA covers it. Add a ROA for AS216471, maxLength 24. |
| Route object: none | 193.36.94.0/24 | No route object for it. Add a route object with origin AS216471 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS216471 whose prefix no peer sees AS216471 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 38.210.122.0/24 | 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.