Network · data from 2026-11-12
AS9355 National Institute of Information and Communications Technology
Registry name: NICT - National Institute of Information and Communications Technology, JP · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS9355, 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.
| 2001:df0:232::/48 | No ROA | Other IRR onlyJPIRR, RADB | 631 99% |
| 133.140.0.0/16 | Valid | Other IRR onlyJPIRR | 672 100% |
| 133.243.0.0/16 | Valid | Other IRR onlyJPIRR, RADB | 668 99% |
AS-SET
AS9355'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 4 are in fix.csv.
- ROA: none1
- Route object: RIR3
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 2001:df0:232::/48 | No ROA covers it. Add a ROA for AS9355, maxLength 48. |
| Route object: RIR | 2001:df0:232::/48 | Route object only in JPIRR, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 133.140.0.0/16 | Route object only in JPIRR. Add it in the RIR database for the space. |
| Route object: RIR | 133.243.0.0/16 | Route object only in JPIRR, RADB. Add it in the RIR database for the space. |
Route objects not announced
Every route object with origin AS9355 is announced.
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.