Network · data from 2026-11-12
AS23817 KOCHI-IDC - Fujitsu Limited.
Registry name: KOCHI-IDC - Fujitsu Limited., JP · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS23817, 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.
| 202.211.64.0/20 | No ROA | Other IRR onlyJPIRR, NTTCOM, RADB | 672 100% |
| 210.158.128.0/20 | No ROA | Other IRR onlyJPIRR, NTTCOM | 671 100% |
AS-SET
AS23817 isn't in PeeringDB, where networks name their 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 8 are in fix.csv.
- ROA: none2
- Route object: RIR2
- Route object: not announced4
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 202.211.64.0/20 | No ROA covers it. Add a ROA for AS23817, maxLength 20. |
| Route object: RIR | 202.211.64.0/20 | Route object only in JPIRR, NTTCOM, RADB. Add it in the RIR database for the space. |
| ROA: none | 210.158.128.0/20 | No ROA covers it. Add a ROA for AS23817, maxLength 20. |
| Route object: RIR | 210.158.128.0/20 | Route object only in JPIRR, NTTCOM. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS23817 whose prefix no peer sees AS23817 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 202.211.79.0/24 | JPIRR, RADB | No ROA |
| 202.243.187.0/24 | NTTCOM | No ROA |
| 202.254.164.0/22 | NTTCOM | No ROA |
| 210.158.137.0/24 | JPIRR, NTTCOM | 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.