Network · data from 2026-11-12
AS23783 Cable Networks Akita Co.,Ltd.
Registry name: CNA - Cable Networks Akita Co.,ltd., JP · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS23783, 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.54.204.0/22 | No ROA | Other IRR onlyJPIRR, RADB | 671 100% |
| 202.236.116.0/24 | No ROA | Other IRR onlyJPIRR, RADB | 671 100% |
| 202.240.66.0/23 | No ROA | Other IRR onlyJPIRR, RADB | 671 100% |
| 27.110.96.0/20 | Valid | Other IRR onlyJPIRR, NTTCOM, RADB | 673 100% |
| 27.110.112.0/21 | Valid | Other IRR onlyJPIRR, NTTCOM, RADB | 673 100% |
| 61.11.128.0/19 | Valid | Other IRR onlyJPIRR, NTTCOM, RADB | 673 100% |
| 61.11.160.0/20 | Valid | Other IRR onlyJPIRR, NTTCOM, RADB | 673 100% |
| 61.11.176.0/20 | Valid | Other IRR onlyJPIRR, NTTCOM, RADB | 673 100% |
| 61.11.192.0/20 | Valid | Other IRR onlyJPIRR, NTTCOM, RADB | 673 100% |
| 193.116.32.0/19 | Valid | Other IRR onlyJPIRR, NTTCOM, RADB | 673 100% |
| 193.116.32.0/20 | Valid | Other IRR onlyJPIRR, NTTCOM, RADB | 673 100% |
| 219.124.104.0/21 | Valid | Other IRR onlyJPIRR, NTTCOM, RADB | 673 100% |
| 218.185.128.0/19 | Valid | Other IRR onlyJPIRR, NTTCOM, RADB | 672 100% |
| 203.179.244.0/23 | Valid | Other IRR onlyJPIRR, NTTCOM, RADB | 671 100% |
| 203.179.248.0/23 | Valid | Other IRR onlyJPIRR, NTTCOM, RADB | 671 100% |
| 203.179.252.0/22 | Valid | Other IRR onlyJPIRR, NTTCOM, RADB | 671 100% |
| 219.124.98.0/23 | Valid | Other IRR onlyJPIRR, NTTCOM, RADB | 671 100% |
| 219.124.100.0/22 | Valid | Other IRR onlyJPIRR, NTTCOM, RADB | 671 100% |
| 210.143.122.0/23 | Valid | Other IRR onlyJPIRR, NTTCOM, RADB | 670 100% |
| 2403:5a00::/32 | Valid | Other IRR onlyJPIRR, NTTCOM, RADB | 633 100% |
| 2403:5a00:fff0::/48 | Valid | Other IRR onlyJPIRR, RADB | 633 100% |
AS-SET
PeeringDB's irr_as_set for AS23783: AS-CNA. 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 (AS23783 isn't in the set, or no route object for AS23783 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 | AS23783 in it | Not covered |
|---|---|---|---|---|---|
| AS-CNA | NTTCOM | 4 | 1 | Yes | 0 |
| JPIRR (also) | 4 | 1 | Yes | 0 |
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 40 are in fix.csv.
- ROA: none3
- Route object: RIR21
- Route object: not announced16
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 103.54.204.0/22 | No ROA covers it. Add a ROA for AS23783, maxLength 22. |
| Route object: RIR | 103.54.204.0/22 | Route object only in JPIRR, RADB. Add it in the RIR database for the space. |
| ROA: none | 202.236.116.0/24 | No ROA covers it. Add a ROA for AS23783, maxLength 24. |
| Route object: RIR | 202.236.116.0/24 | Route object only in JPIRR, RADB. Add it in the RIR database for the space. |
| ROA: none | 202.240.66.0/23 | No ROA covers it. Add a ROA for AS23783, maxLength 23. |
| Route object: RIR | 202.240.66.0/23 | Route object only in JPIRR, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 27.110.96.0/20 | Route object only in JPIRR, NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 27.110.112.0/21 | Route object only in JPIRR, NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 61.11.128.0/19 | Route object only in JPIRR, NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 61.11.160.0/20 | Route object only in JPIRR, NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 61.11.176.0/20 | Route object only in JPIRR, NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 61.11.192.0/20 | Route object only in JPIRR, NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 193.116.32.0/19 | Route object only in JPIRR, NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 193.116.32.0/20 | Route object only in JPIRR, NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 219.124.104.0/21 | Route object only in JPIRR, NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 218.185.128.0/19 | Route object only in JPIRR, NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 203.179.244.0/23 | Route object only in JPIRR, NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 203.179.248.0/23 | Route object only in JPIRR, NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 203.179.252.0/22 | Route object only in JPIRR, NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 219.124.98.0/23 | Route object only in JPIRR, NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 219.124.100.0/22 | Route object only in JPIRR, NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 210.143.122.0/23 | Route object only in JPIRR, NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 2403:5a00::/32 | Route object only in JPIRR, NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 2403:5a00:fff0::/48 | Route object only in JPIRR, RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS23783 whose prefix no peer sees AS23783 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 27.110.96.0/21 | JPIRR, NTTCOM, RADB | Valid |
| 27.110.104.0/21 | JPIRR, NTTCOM, RADB | Valid |
| 27.110.112.0/22 | JPIRR, NTTCOM, RADB | Valid |
| 27.110.116.0/22 | JPIRR, NTTCOM, RADB | Valid |
| 61.11.128.0/20 | JPIRR, NTTCOM, RADB | Valid |
| 61.11.144.0/20 | JPIRR, NTTCOM, RADB | Valid |
| 61.11.160.0/21 | JPIRR, NTTCOM, RADB | Valid |
| 61.11.168.0/21 | JPIRR, NTTCOM, RADB | Valid |
| 61.11.176.0/21 | JPIRR, NTTCOM, RADB | Valid |
| 61.11.184.0/21 | JPIRR, NTTCOM, RADB | Valid |
| 61.11.192.0/21 | JPIRR, NTTCOM, RADB | Valid |
| 61.11.200.0/21 | JPIRR, NTTCOM, RADB | Valid |
| 193.116.48.0/20 | JPIRR, NTTCOM | Valid |
| 193.116.48.0/22 | RADB | Valid |
| 218.185.128.0/20 | JPIRR, NTTCOM | Valid |
| 218.185.144.0/20 | JPIRR, NTTCOM | Valid |
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.