Network · data from 2026-11-12
AS9354 Community Network Center Inc. (CNCI)
Registry name: TDNC - Community Network Center Inc., JP · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS9354, 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.
| 104.92.64.0/22 | Valid | None | 1 0%low visibility |
| 27.113.224.0/20 | Valid | Other IRR onlyJPIRR, NTTCOM, RADB | 673 100% |
| 61.87.64.0/20 | Valid | Other IRR onlyJPIRR, NTTCOM, RADB | 673 100% |
| 61.87.80.0/20 | Valid | Other IRR onlyJPIRR, NTTCOM, RADB | 673 100% |
| 61.87.96.0/20 | Valid | Other IRR onlyJPIRR, NTTCOM, RADB | 673 100% |
| 61.87.112.0/20 | Valid | Other IRR onlyJPIRR, NTTCOM, RADB | 673 100% |
| 103.40.104.0/22 | Valid | Other IRR onlyJPIRR, NTTCOM, RADB | 673 100% |
| 103.131.120.0/22 | Valid | Other IRR onlyJPIRR, NTTCOM, RADB | 673 100% |
| 125.2.128.0/18 | Valid | Other IRR onlyJPIRR, NTTCOM, RADB | 673 100% |
| 125.2.192.0/20 | Valid | Other IRR onlyJPIRR, NTTCOM, RADB | 673 100% |
| 157.5.0.0/19 | Valid | Other IRR onlyJPIRR, NTTCOM, RADB | 673 100% |
| 202.157.224.0/21 | Valid | Other IRR onlyJPIRR, NTTCOM, RADB | 673 100% |
| 202.157.232.0/23 | Valid | Other IRR onlyJPIRR, NTTCOM, RADB | 673 100% |
| 202.157.234.0/23 | Valid | Other IRR onlyJPIRR, NTTCOM, RADB | 673 100% |
| 202.157.236.0/23 | Valid | Other IRR onlyJPIRR, NTTCOM, RADB | 673 100% |
| 202.157.238.0/23 | Valid | Other IRR onlyJPIRR, NTTCOM, RADB | 673 100% |
| 202.157.240.0/22 | Valid | Other IRR onlyJPIRR, NTTCOM, RADB | 673 100% |
| 202.157.244.0/22 | Valid | Other IRR onlyJPIRR, NTTCOM, RADB | 673 100% |
| 202.157.248.0/22 | Valid | Other IRR onlyJPIRR, NTTCOM, RADB | 673 100% |
| 202.157.252.0/22 | Valid | Other IRR onlyJPIRR, NTTCOM, RADB | 673 100% |
| 211.1.192.0/19 | Valid | Other IRR onlyJPIRR, NTTCOM, RADB | 673 100% |
| 211.2.64.0/18 | Valid | Other IRR onlyJPIRR, NTTCOM, RADB | 673 100% |
| 219.99.0.0/19 | Valid | Other IRR onlyJPIRR, NTTCOM, RADB | 673 100% |
| 219.100.224.0/23 | Valid | Other IRR onlyJPIRR, NTTCOM, RADB | 673 100% |
| 219.100.226.0/24 | Valid | Other IRR onlyJPIRR, NTTCOM, RADB | 673 100% |
| 219.118.128.0/19 | Valid | Other IRR onlyJPIRR, NTTCOM, RADB | 673 100% |
| 221.118.0.0/18 | Valid | Other IRR onlyJPIRR, NTTCOM, RADB | 673 100% |
| 221.118.128.0/18 | Valid | Other IRR onlyJPIRR, NTTCOM, RADB | 673 100% |
| 221.118.192.0/18 | Valid | Other IRR onlyJPIRR, NTTCOM, RADB | 673 100% |
| 222.229.96.0/19 | Valid | Other IRR onlyJPIRR, NTTCOM, RADB | 673 100% |
| 210.158.144.0/20 | Valid | Other IRR onlyJPIRR, NTTCOM, RADB | 672 100% |
| 210.251.192.0/20 | Valid | Other IRR onlyJPIRR, NTTCOM, RADB | 672 100% |
| 210.251.208.0/20 | Valid | Other IRR onlyJPIRR, NTTCOM, RADB | 672 100% |
| 223.252.64.0/20 | Valid | Other IRR onlyJPIRR, NTTCOM, RADB | 672 100% |
| 223.252.80.0/20 | Valid | Other IRR onlyJPIRR, NTTCOM, RADB | 672 100% |
| 133.149.80.0/20 | Valid | Other IRR onlyJPIRR, NTTCOM, RADB | 670 100% |
| 221.118.64.0/18 | Valid | Other IRR onlyJPIRR, NTTCOM, RADB | 670 100% |
| 2405:7000::/32 | Valid | Other IRR onlyJPIRR, NTTCOM, RADB | 631 99% |
| 2.17.16.0/22 | Valid | RIR databaseJPIRR, RIPE | 673 100% |
AS-SET
PeeringDB's irr_as_set for AS9354: AS-CNCI. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS9354 isn't in the set, or no route object for AS9354 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.
| Name | Database | ASNs | Sets | AS9354 in it | Not covered |
|---|---|---|---|---|---|
| AS-CNCI | RADB | 18 | 1 | Yes | 1 |
| JPIRR (also) | 18 | 1 | Yes | 1 | |
| NTTCOM (also) | 18 | 1 | Yes | 1 |
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 39 are in fix.csv.
- Route object: none1
- Route object: RIR37
- Route object: not announced1
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 104.92.64.0/22 | No route object for it. Add a route object with origin AS9354 in the RIR database for the space. |
| Route object: RIR | 27.113.224.0/20 | Route object only in JPIRR, NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 61.87.64.0/20 | Route object only in JPIRR, NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 61.87.80.0/20 | Route object only in JPIRR, NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 61.87.96.0/20 | Route object only in JPIRR, NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 61.87.112.0/20 | Route object only in JPIRR, NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 103.40.104.0/22 | Route object only in JPIRR, NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 103.131.120.0/22 | Route object only in JPIRR, NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 125.2.128.0/18 | Route object only in JPIRR, NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 125.2.192.0/20 | Route object only in JPIRR, NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 157.5.0.0/19 | Route object only in JPIRR, NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 202.157.224.0/21 | Route object only in JPIRR, NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 202.157.232.0/23 | Route object only in JPIRR, NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 202.157.234.0/23 | Route object only in JPIRR, NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 202.157.236.0/23 | Route object only in JPIRR, NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 202.157.238.0/23 | Route object only in JPIRR, NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 202.157.240.0/22 | Route object only in JPIRR, NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 202.157.244.0/22 | Route object only in JPIRR, NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 202.157.248.0/22 | Route object only in JPIRR, NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 202.157.252.0/22 | Route object only in JPIRR, NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 211.1.192.0/19 | Route object only in JPIRR, NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 211.2.64.0/18 | Route object only in JPIRR, NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 219.99.0.0/19 | Route object only in JPIRR, NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 219.100.224.0/23 | Route object only in JPIRR, NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 219.100.226.0/24 | Route object only in JPIRR, NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 219.118.128.0/19 | Route object only in JPIRR, NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 221.118.0.0/18 | Route object only in JPIRR, NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 221.118.128.0/18 | Route object only in JPIRR, NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 221.118.192.0/18 | Route object only in JPIRR, NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 222.229.96.0/19 | Route object only in JPIRR, NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 210.158.144.0/20 | Route object only in JPIRR, NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 210.251.192.0/20 | Route object only in JPIRR, NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 210.251.208.0/20 | Route object only in JPIRR, NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 223.252.64.0/20 | Route object only in JPIRR, NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 223.252.80.0/20 | Route object only in JPIRR, NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 133.149.80.0/20 | Route object only in JPIRR, NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 221.118.64.0/18 | Route object only in JPIRR, NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 2405:7000::/32 | Route object only in JPIRR, NTTCOM, RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS9354 whose prefix no peer sees AS9354 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 202.157.224.0/19 | JPIRR, NTTCOM, 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.