Announced routes
Every prefix a peer of the route collectors sees with origin AS395054, 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.
| 168.215.110.64/27 | No ROA | None | 2 0%low visibility |
| 135.84.42.0/24 | No ROA | RIR databaseARIN, RADB | 673 100% |
AS-SET
AS395054'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: none2
- Route object: none1
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 168.215.110.64/27 | No ROA covers it. Add a ROA for AS395054, maxLength 27. |
| Route object: none | 168.215.110.64/27 | No route object for it. Add a route object with origin AS395054 in the RIR database for the space. |
| ROA: none | 135.84.42.0/24 | No ROA covers it. Add a ROA for AS395054, maxLength 24. |
Route objects not announced
Every route object with origin AS395054 is announced.
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.