Announced routes
Every prefix a peer of the route collectors sees with origin AS214255, 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.
| 86.54.46.0/23 | No ROA | RIR databaseRIPE | 666 99% |
| 185.213.121.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 213.254.186.0/23 | Valid | RIR databaseRIPE | 672 100% |
| 87.121.46.0/24 | Valid | RIR databaseRIPE | 669 99% |
AS-SET
AS214255'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: none1
- Route object: not announced5
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 86.54.46.0/23 | No ROA covers it. Add a ROA for AS214255, maxLength 23. |
Route objects not announced
Route objects with origin AS214255 whose prefix no peer sees AS214255 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 45.149.240.0/24 | RIPE | Valid |
| 93.123.116.0/24 | RIPE | Valid |
| 95.214.25.0/24 | RIPE | Valid |
| 95.214.26.0/24 | RIPE | Valid |
| 185.218.136.0/24 | 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.