Announced routes
Every prefix a peer of the route collectors sees with origin AS328098, 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.
| 154.65.30.0/23 | No ROA | Nonecovered by 154.65.28.0/22 | 673 100% |
| 164.160.140.0/24 | No ROA | Other origin onlycovered by 164.160.140.0/22 | 669 99% |
| 164.160.141.0/24 | No ROA | Nonecovered by 164.160.140.0/22 | 669 99% |
| 164.160.142.0/23 | No ROA | Nonecovered by 164.160.140.0/22 | 669 99% |
| 154.65.28.0/24 | No ROA | Other IRR onlyRADB | 673 100% |
| 154.65.29.0/24 | No ROA | RIR databaseAFRINIC | 673 100% |
AS-SET
AS328098'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 15 are in fix.csv.
- ROA: none6
- Route object: none4
- Route object: RIR1
- Route object: not announced4
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 154.65.30.0/23 | No ROA covers it. Add a ROA for AS328098, maxLength 23. |
| Route object: none | 154.65.30.0/23 | No route object for it. A route object for 154.65.28.0/22 with origin AS328098 covers it (filters allowing more-specifics accept it). Add a route object with origin AS328098 in the RIR database for the space. |
| ROA: none | 164.160.140.0/24 | No ROA covers it. Add a ROA for AS328098, maxLength 24. |
| Route object: none | 164.160.140.0/24 | Route objects for it name AS16637. A route object for 164.160.140.0/22 with origin AS328098 covers it (filters allowing more-specifics accept it). Add a route object with origin AS328098 in the RIR database for the space. |
| ROA: none | 164.160.141.0/24 | No ROA covers it. Add a ROA for AS328098, maxLength 24. |
| Route object: none | 164.160.141.0/24 | No route object for it. A route object for 164.160.140.0/22 with origin AS328098 covers it (filters allowing more-specifics accept it). Add a route object with origin AS328098 in the RIR database for the space. |
| ROA: none | 164.160.142.0/23 | No ROA covers it. Add a ROA for AS328098, maxLength 23. |
| Route object: none | 164.160.142.0/23 | No route object for it. A route object for 164.160.140.0/22 with origin AS328098 covers it (filters allowing more-specifics accept it). Add a route object with origin AS328098 in the RIR database for the space. |
| ROA: none | 154.65.28.0/24 | No ROA covers it. Add a ROA for AS328098, maxLength 24. |
| Route object: RIR | 154.65.28.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 154.65.29.0/24 | No ROA covers it. Add a ROA for AS328098, maxLength 24. |
Route objects not announced
Route objects with origin AS328098 whose prefix no peer sees AS328098 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 154.65.28.0/22 | RADB | No ROA |
| 154.65.28.0/23 | RADB | No ROA |
| 164.160.140.0/22 | RADB | No ROA |
| 2c0f:f1d0::/32 | AFRINIC | 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.