Announced routes
Every prefix a peer of the route collectors sees with origin AS41864, 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.
| 95.214.116.0/22 | No ROA | RIR databaseRIPE | 671 100% |
AS-SET
AS41864'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 | 95.214.116.0/22 | No ROA covers it. Add a ROA for AS41864, maxLength 22. |
Route objects not announced
Route objects with origin AS41864 whose prefix no peer sees AS41864 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 95.214.116.0/24 | RIPE | No ROA |
| 95.214.117.0/24 | RIPE | No ROA |
| 95.214.118.0/24 | RIPE | No ROA |
| 2a09:f780::/29 | RIPE | No ROA |
| 2a09:f780:1::/48 | 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.