Network · data from 2026-11-12
AS17530 NNS - Nihon Network Service Co, .Ltd.
Registry name: NNS - Nihon Network Service Co, .Ltd., JP · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS17530, 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.
| 59.191.128.0/18 | Valid | Other IRR onlyRADB | 672 100% |
| 61.193.128.0/20 | Valid | Other IRR onlyRADB | 672 100% |
| 64.63.64.0/18 | Valid | Other IRR onlyJPIRR, RADB | 672 100% |
| 122.201.0.0/21 | Valid | Other IRR onlyRADB | 672 100% |
| 2401:bf00::/32 | Valid | Other IRR onlyJPIRR, RADB | 635 100% |
AS-SET
AS17530 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 5 are in fix.csv.
- Route object: RIR5
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: RIR | 59.191.128.0/18 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 61.193.128.0/20 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 64.63.64.0/18 | Route object only in JPIRR, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 122.201.0.0/21 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 2401:bf00::/32 | Route object only in JPIRR, RADB. Add it in the RIR database for the space. |
Route objects not announced
Every route object with origin AS17530 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.