Network · data from 2026-11-12
AS17693 NEKONET - YAMATO SYSTEM DEVELOPMENT CO., LTD.
Registry name: NEKONET - YAMATO SYSTEM DEVELOPMENT CO., LTD., JP · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS17693, 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.
| 103.2.24.0/22 | No ROA | None | 673 100% |
| 202.130.60.0/22 | No ROA | None | 673 100% |
| 219.100.32.0/22 | No ROA | Other IRR onlyRADB | 673 100% |
| 218.40.0.0/20 | No ROA | Other IRR onlyJPIRR, RADB | 672 100% |
| 2400:7b00::/32 | No ROA | Other IRR onlyRADB | 635 100% |
AS-SET
AS17693 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 16 are in fix.csv.
- ROA: none5
- Route object: none2
- Route object: RIR3
- Route object: not announced6
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 103.2.24.0/22 | No ROA covers it. Add a ROA for AS17693, maxLength 22. |
| Route object: none | 103.2.24.0/22 | No route object for it. Add a route object with origin AS17693 in the RIR database for the space. |
| ROA: none | 202.130.60.0/22 | No ROA covers it. Add a ROA for AS17693, maxLength 22. |
| Route object: none | 202.130.60.0/22 | No route object for it. Add a route object with origin AS17693 in the RIR database for the space. |
| ROA: none | 219.100.32.0/22 | No ROA covers it. Add a ROA for AS17693, maxLength 22. |
| Route object: RIR | 219.100.32.0/22 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 218.40.0.0/20 | No ROA covers it. Add a ROA for AS17693, maxLength 20. |
| Route object: RIR | 218.40.0.0/20 | Route object only in JPIRR, RADB. Add it in the RIR database for the space. |
| ROA: none | 2400:7b00::/32 | No ROA covers it. Add a ROA for AS17693, maxLength 32. |
| Route object: RIR | 2400:7b00::/32 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS17693 whose prefix no peer sees AS17693 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 218.40.13.0/24 | JPIRR, RADB | No ROA |
| 218.40.15.0/24 | JPIRR, RADB | No ROA |
| 219.100.32.0/24 | RADB | No ROA |
| 219.100.33.0/24 | RADB | No ROA |
| 219.100.34.0/24 | RADB | No ROA |
| 219.100.35.0/24 | 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.