Announced routes
Every prefix a peer of the route collectors sees with origin AS10653, 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.
| 216.236.240.0/20 | No ROA | Other IRR onlyALTDB, RADB, RIPE-NONAUTH | 671 100% |
AS-SET
AS10653'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 10 are in fix.csv.
- ROA: none1
- Route object: RIR1
- Route object: not announced8
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 216.236.240.0/20 | No ROA covers it. Add a ROA for AS10653, maxLength 20. |
| Route object: RIR | 216.236.240.0/20 | Route object only in ALTDB, RADB, RIPE-NONAUTH. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS10653 whose prefix no peer sees AS10653 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 65.118.154.0/24 | RADB | No ROA |
| 67.110.140.0/23 | RADB | No ROA |
| 156.21.0.0/16 | ALTDB | No ROA |
| 156.21.0.0/20 | ALTDB | No ROA |
| 199.33.144.0/24 | ALTDB, RIPE-NONAUTH | No ROA |
| 199.245.172.0/24 | ALTDB, RIPE-NONAUTH | No ROA |
| 204.107.142.0/24 | RADB | No ROA |
| 2606:a500::/32 | ALTDB | 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.