Network · data from 2026-11-12
AS18379 CSMNAP-AS-AP - CSMNAP-ASN
Registry name: CSMNAP-AS-AP - CSMNAP-ASN, ID · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS18379, 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.123.224.0/20 | No ROA | Other IRR onlyNTTCOM, RADB, REACH | 672 100% |
| 202.123.225.0/24 | No ROA | Other IRR onlyNTTCOM, RADB | 672 100% |
| 202.123.226.0/24 | No ROA | Other IRR onlyNTTCOM, RADB | 672 100% |
| 202.123.227.0/24 | No ROA | Other IRR onlyNTTCOM, RADB | 672 100% |
| 202.123.228.0/24 | No ROA | Other IRR onlyNTTCOM, RADB | 672 100% |
| 202.123.229.0/24 | No ROA | Other IRR onlyNTTCOM, RADB | 672 100% |
| 202.123.230.0/24 | No ROA | Other IRR onlyNTTCOM, RADB | 672 100% |
| 202.123.231.0/24 | No ROA | Other IRR onlyNTTCOM, RADB | 672 100% |
| 202.123.232.0/24 | No ROA | Other IRR onlyNTTCOM, RADB | 672 100% |
| 202.123.233.0/24 | No ROA | Other IRR onlyNTTCOM, RADB | 672 100% |
| 202.123.234.0/24 | No ROA | Other IRR onlyNTTCOM, RADB | 672 100% |
| 202.123.235.0/24 | No ROA | Other IRR onlyNTTCOM, RADB | 672 100% |
| 202.123.238.0/24 | No ROA | Other IRR onlyNTTCOM | 672 100% |
| 202.123.239.0/24 | No ROA | Other IRR onlyNTTCOM, RADB | 672 100% |
AS-SET
AS18379 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 76 are in fix.csv.
- ROA: none14
- Route object: RIR14
- Route object: not announced48
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 202.123.224.0/20 | No ROA covers it. Add a ROA for AS18379, maxLength 20. |
| Route object: RIR | 202.123.224.0/20 | Route object only in NTTCOM, RADB, REACH. Add it in the RIR database for the space. |
| ROA: none | 202.123.225.0/24 | No ROA covers it. Add a ROA for AS18379, maxLength 24. |
| Route object: RIR | 202.123.225.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| ROA: none | 202.123.226.0/24 | No ROA covers it. Add a ROA for AS18379, maxLength 24. |
| Route object: RIR | 202.123.226.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| ROA: none | 202.123.227.0/24 | No ROA covers it. Add a ROA for AS18379, maxLength 24. |
| Route object: RIR | 202.123.227.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| ROA: none | 202.123.228.0/24 | No ROA covers it. Add a ROA for AS18379, maxLength 24. |
| Route object: RIR | 202.123.228.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| ROA: none | 202.123.229.0/24 | No ROA covers it. Add a ROA for AS18379, maxLength 24. |
| Route object: RIR | 202.123.229.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| ROA: none | 202.123.230.0/24 | No ROA covers it. Add a ROA for AS18379, maxLength 24. |
| Route object: RIR | 202.123.230.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| ROA: none | 202.123.231.0/24 | No ROA covers it. Add a ROA for AS18379, maxLength 24. |
| Route object: RIR | 202.123.231.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| ROA: none | 202.123.232.0/24 | No ROA covers it. Add a ROA for AS18379, maxLength 24. |
| Route object: RIR | 202.123.232.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| ROA: none | 202.123.233.0/24 | No ROA covers it. Add a ROA for AS18379, maxLength 24. |
| Route object: RIR | 202.123.233.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| ROA: none | 202.123.234.0/24 | No ROA covers it. Add a ROA for AS18379, maxLength 24. |
| Route object: RIR | 202.123.234.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| ROA: none | 202.123.235.0/24 | No ROA covers it. Add a ROA for AS18379, maxLength 24. |
| Route object: RIR | 202.123.235.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| ROA: none | 202.123.238.0/24 | No ROA covers it. Add a ROA for AS18379, maxLength 24. |
| Route object: RIR | 202.123.238.0/24 | Route object only in NTTCOM. Add it in the RIR database for the space. |
| ROA: none | 202.123.239.0/24 | No ROA covers it. Add a ROA for AS18379, maxLength 24. |
| Route object: RIR | 202.123.239.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS18379 whose prefix no peer sees AS18379 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 103.247.32.0/22 | NTTCOM, RADB | No ROA |
| 103.247.32.0/24 | NTTCOM | No ROA |
| 117.103.8.0/21 | NTTCOM, RADB | No ROA |
| 123.108.96.0/21 | NTTCOM, RADB | No ROA |
| 123.108.96.0/22 | NTTCOM | No ROA |
| 123.108.96.0/23 | NTTCOM | No ROA |
| 123.108.96.0/24 | NTTCOM | No ROA |
| 123.108.97.0/24 | NTTCOM | No ROA |
| 123.108.98.0/23 | NTTCOM | No ROA |
| 123.108.98.0/24 | NTTCOM | No ROA |
| 123.108.99.0/24 | NTTCOM | No ROA |
| 123.108.100.0/22 | NTTCOM | No ROA |
| 123.108.100.0/23 | NTTCOM | No ROA |
| 123.108.100.0/24 | NTTCOM | No ROA |
| 123.108.101.0/24 | NTTCOM | No ROA |
| 123.108.102.0/23 | NTTCOM | No ROA |
| 123.108.102.0/24 | NTTCOM | No ROA |
| 123.108.103.0/24 | NTTCOM | No ROA |
| 202.52.8.0/21 | RADB | No ROA |
| 202.67.32.0/20 | NTTCOM, RADB | No ROA |
| 202.93.224.0/20 | NTTCOM, RADB | No ROA |
| 202.93.240.0/21 | NTTCOM, RADB | No ROA |
| 202.123.224.0/21 | NTTCOM, RADB | No ROA |
| 202.123.224.0/22 | NTTCOM, RADB | No ROA |
| 202.123.224.0/23 | NTTCOM, RADB | No ROA |
| 202.123.224.0/24 | NTTCOM, RADB | No ROA |
| 202.123.226.0/23 | NTTCOM, RADB | No ROA |
| 202.123.228.0/22 | NTTCOM, RADB | No ROA |
| 202.123.228.0/23 | NTTCOM, RADB | No ROA |
| 202.123.230.0/23 | NTTCOM, RADB | No ROA |
| 202.123.232.0/21 | NTTCOM, RADB | No ROA |
| 202.123.232.0/22 | NTTCOM, RADB | No ROA |
| 202.123.232.0/23 | NTTCOM, RADB | No ROA |
| 202.123.234.0/23 | NTTCOM, RADB | No ROA |
| 202.123.236.0/22 | NTTCOM, RADB | No ROA |
| 202.123.236.0/23 | NTTCOM, RADB | No ROA |
| 202.123.236.0/24 | NTTCOM | No ROA |
| 202.123.237.0/24 | NTTCOM, RADB | No ROA |
| 202.123.238.0/23 | NTTCOM, RADB | No ROA |
| 202.127.96.0/20 | APNIC | Invalid: origin |
| 202.148.0.0/19 | NTTCOM, RADB | No ROA |
| 202.159.0.0/17 | NTTCOM, RADB | No ROA |
| 202.160.254.0/24 | NTTCOM, RADB | No ROA |
| 202.180.48.0/21 | RADB | No ROA |
| 203.201.160.0/20 | NTTCOM, RADB | No ROA |
| 210.79.208.0/20 | APNIC | Invalid: origin |
| 2400:b980::/32 | APNIC, RADB | No ROA |
| 2406:5c00::/32 | APNIC | 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.