Announced routes
Every prefix a peer of the route collectors sees with origin AS45768, 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.
| 203.33.180.0/24 | Valid | Other IRR onlyNTTCOM | 672 100% |
| 203.33.181.0/24 | Valid | Other IRR onlyNTTCOM | 672 100% |
| 27.111.64.0/21 | Valid | RIR databaseAPNIC, NTTCOM | 672 100% |
| 113.29.208.0/21 | Valid | RIR databaseAPNIC, NTTCOM | 672 100% |
| 180.95.0.0/24 | Valid | RIR databaseAPNIC, NTTCOM | 672 100% |
| 180.95.64.0/19 | Valid | RIR databaseAPNIC, NTTCOM | 672 100% |
| 180.95.96.0/20 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 672 100% |
| 180.95.112.0/21 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 672 100% |
| 202.129.252.0/24 | Valid | RIR databaseAPNIC, NTTCOM | 672 100% |
| 202.134.51.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 672 100% |
| 203.34.155.0/24 | Valid | RIR databaseAPNIC, NTTCOM | 672 100% |
AS-SET
AS45768'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 25 are in fix.csv.
- Route object: RIR2
- Route object: not announced23
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: RIR | 203.33.180.0/24 | Route object only in NTTCOM. Add it in the RIR database for the space. |
| Route object: RIR | 203.33.181.0/24 | Route object only in NTTCOM. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS45768 whose prefix no peer sees AS45768 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 27.111.64.0/22 | APNIC | Valid |
| 27.111.64.0/23 | APNIC | Valid |
| 27.111.64.0/24 | APNIC | Valid |
| 27.111.65.0/24 | APNIC | Valid |
| 27.111.66.0/23 | APNIC | Valid |
| 27.111.66.0/24 | APNIC | Valid |
| 27.111.67.0/24 | APNIC | Valid |
| 27.111.68.0/22 | APNIC | Valid |
| 27.111.68.0/23 | APNIC | Valid |
| 27.111.68.0/24 | APNIC | Valid |
| 27.111.69.0/24 | APNIC | Valid |
| 27.111.70.0/23 | APNIC | Valid |
| 27.111.70.0/24 | APNIC | Valid |
| 27.111.71.0/24 | APNIC | Valid |
| 203.63.206.0/23 | RADB | No ROA |
| 210.8.54.0/23 | RADB | No ROA |
| 210.8.110.0/23 | RADB | No ROA |
| 210.8.154.0/23 | RADB | No ROA |
| 210.8.166.192/29 | RADB | No ROA |
| 210.8.166.192/30 | RADB | No ROA |
| 210.8.166.196/30 | RADB | No ROA |
| 210.9.204.0/23 | RADB | No ROA |
| 210.10.112.16/28 | RADB | 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.