Announced routes
Every prefix a peer of the route collectors sees with origin AS22512, 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.
| 199.185.136.0/23 | No ROA | Other IRR onlyCANARIE, NTTCOM, RADB, RIPE-NONAUTH | 671 100% |
| 199.185.136.0/24 | No ROA | Other IRR onlyCANARIE, NTTCOM, RADB | 671 100% |
| 199.185.137.0/24 | No ROA | Other IRR onlyCANARIE, NTTCOM, RADB | 671 100% |
| 199.185.178.0/24 | No ROA | Other IRR onlyCANARIE, NTTCOM, RADB, RIPE-NONAUTH | 671 100% |
| 199.185.230.0/23 | No ROA | Other IRR onlyCANARIE, NTTCOM, RADB, RIPE-NONAUTH | 671 100% |
| 204.174.115.0/24 | No ROA | Other IRR onlyNTTCOM, RADB, RIPE-NONAUTH | 671 100% |
| 204.209.252.0/23 | No ROA | Other IRR onlyCANARIE, NTTCOM, RADB, RIPE-NONAUTH | 671 100% |
| 204.209.252.0/24 | No ROA | Other IRR onlyCANARIE, NTTCOM, RADB, RIPE-NONAUTH | 671 100% |
| 204.209.253.0/24 | No ROA | Other IRR onlyCANARIE, NTTCOM, RADB, RIPE-NONAUTH | 671 100% |
| 2620:3d:c000::/48 | Valid | Other IRR onlyCANARIE, NTTCOM, RIPE-NONAUTH | 635 100% |
AS-SET
AS22512'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 23 are in fix.csv.
- ROA: none9
- Route object: RIR10
- Route object: not announced4
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 199.185.136.0/23 | No ROA covers it. Add a ROA for AS22512, maxLength 23. |
| Route object: RIR | 199.185.136.0/23 | Route object only in CANARIE, NTTCOM, RADB, RIPE-NONAUTH. Add it in the RIR database for the space. |
| ROA: none | 199.185.136.0/24 | No ROA covers it. Add a ROA for AS22512, maxLength 24. |
| Route object: RIR | 199.185.136.0/24 | Route object only in CANARIE, NTTCOM, RADB. Add it in the RIR database for the space. |
| ROA: none | 199.185.137.0/24 | No ROA covers it. Add a ROA for AS22512, maxLength 24. |
| Route object: RIR | 199.185.137.0/24 | Route object only in CANARIE, NTTCOM, RADB. Add it in the RIR database for the space. |
| ROA: none | 199.185.178.0/24 | No ROA covers it. Add a ROA for AS22512, maxLength 24. |
| Route object: RIR | 199.185.178.0/24 | Route object only in CANARIE, NTTCOM, RADB, RIPE-NONAUTH. Add it in the RIR database for the space. |
| ROA: none | 199.185.230.0/23 | No ROA covers it. Add a ROA for AS22512, maxLength 23. |
| Route object: RIR | 199.185.230.0/23 | Route object only in CANARIE, NTTCOM, RADB, RIPE-NONAUTH. Add it in the RIR database for the space. |
| ROA: none | 204.174.115.0/24 | No ROA covers it. Add a ROA for AS22512, maxLength 24. |
| Route object: RIR | 204.174.115.0/24 | Route object only in NTTCOM, RADB, RIPE-NONAUTH. Add it in the RIR database for the space. |
| ROA: none | 204.209.252.0/23 | No ROA covers it. Add a ROA for AS22512, maxLength 23. |
| Route object: RIR | 204.209.252.0/23 | Route object only in CANARIE, NTTCOM, RADB, RIPE-NONAUTH. Add it in the RIR database for the space. |
| ROA: none | 204.209.252.0/24 | No ROA covers it. Add a ROA for AS22512, maxLength 24. |
| Route object: RIR | 204.209.252.0/24 | Route object only in CANARIE, NTTCOM, RADB, RIPE-NONAUTH. Add it in the RIR database for the space. |
| ROA: none | 204.209.253.0/24 | No ROA covers it. Add a ROA for AS22512, maxLength 24. |
| Route object: RIR | 204.209.253.0/24 | Route object only in CANARIE, NTTCOM, RADB, RIPE-NONAUTH. Add it in the RIR database for the space. |
| Route object: RIR | 2620:3d:c000::/48 | Route object only in CANARIE, NTTCOM, RIPE-NONAUTH. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS22512 whose prefix no peer sees AS22512 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 192.75.191.0/24 | RADB | No ROA |
| 198.58.2.0/24 | NTTCOM | Valid |
| 199.185.230.0/24 | CANARIE | No ROA |
| 199.185.231.0/24 | CANARIE | 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.