Network · data from 2026-11-12
AS10000 Nagasaki Cable Media
Registry name: NCM - Nagasaki Cable Media Inc., JP · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS10000, 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.
| 61.114.96.0/20 | Valid | Other IRR onlyJPIRR, NTTCOM | 672 100% |
| 61.206.208.0/20 | Valid | Other IRR onlyJPIRR, NTTCOM, RADB | 672 100% |
| 103.29.48.0/22 | Valid | Other IRR onlyJPIRR, RADB | 672 100% |
| 111.91.240.0/20 | Valid | Other IRR onlyJPIRR, NTTCOM, RADB | 672 100% |
| 114.134.96.0/20 | Valid | Other IRR onlyJPIRR, NTTCOM | 672 100% |
| 114.134.128.0/19 | Valid | Other IRR onlyJPIRR, NTTCOM | 672 100% |
| 126.52.0.0/20 | Valid | Other IRR onlyJPIRR | 672 100% |
| 163.131.32.0/19 | Valid | Other IRR onlyJPIRR, RADB | 672 100% |
| 180.214.224.0/21 | Valid | Other IRR onlyJPIRR, NTTCOM, RADB | 672 100% |
| 202.169.64.0/20 | Valid | Other IRR onlyJPIRR, NTTCOM, RADB | 672 100% |
| 202.169.80.0/20 | Valid | Other IRR onlyJPIRR, NTTCOM, RADB | 672 100% |
| 202.228.240.0/20 | Valid | Other IRR onlyJPIRR, NTTCOM, RADB | 672 100% |
| 203.129.96.0/20 | Valid | Other IRR onlyJPIRR, NTTCOM, RADB | 672 100% |
| 203.170.32.0/20 | Valid | Other IRR onlyJPIRR, NTTCOM, RADB | 672 100% |
| 203.215.56.0/22 | Valid | Other IRR onlyJPIRR, NTTCOM, RADB | 672 100% |
| 203.217.156.0/22 | Valid | Other IRR onlyJPIRR, NTTCOM, RADB | 672 100% |
| 218.216.0.0/20 | Valid | Other IRR onlyJPIRR, NTTCOM, RADB | 672 100% |
| 219.100.0.0/22 | Valid | Other IRR onlyJPIRR, RADB | 672 100% |
| 219.109.64.0/20 | Valid | Other IRR onlyJPIRR, NTTCOM, RADB | 672 100% |
| 14.1.8.0/21 | Valid | Other IRR onlyJPIRR, RADB | 671 100% |
| 2405:ed00::/32 | Valid | Other IRR onlyJPIRR | 634 100% |
AS-SET
PeeringDB's irr_as_set for AS10000: AS-10000. 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 (AS10000 isn't in the set, or no route object for AS10000 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 | AS10000 in it | Not covered |
|---|---|---|---|---|---|
| AS-10000 | JPIRR | 2 | 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 21 are in fix.csv.
- Route object: RIR21
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: RIR | 61.114.96.0/20 | Route object only in JPIRR, NTTCOM. Add it in the RIR database for the space. |
| Route object: RIR | 61.206.208.0/20 | Route object only in JPIRR, NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 103.29.48.0/22 | Route object only in JPIRR, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 111.91.240.0/20 | Route object only in JPIRR, NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 114.134.96.0/20 | Route object only in JPIRR, NTTCOM. Add it in the RIR database for the space. |
| Route object: RIR | 114.134.128.0/19 | Route object only in JPIRR, NTTCOM. Add it in the RIR database for the space. |
| Route object: RIR | 126.52.0.0/20 | Route object only in JPIRR. Add it in the RIR database for the space. |
| Route object: RIR | 163.131.32.0/19 | Route object only in JPIRR, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 180.214.224.0/21 | Route object only in JPIRR, NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 202.169.64.0/20 | Route object only in JPIRR, NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 202.169.80.0/20 | Route object only in JPIRR, NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 202.228.240.0/20 | Route object only in JPIRR, NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 203.129.96.0/20 | Route object only in JPIRR, NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 203.170.32.0/20 | Route object only in JPIRR, NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 203.215.56.0/22 | Route object only in JPIRR, NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 203.217.156.0/22 | Route object only in JPIRR, NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 218.216.0.0/20 | Route object only in JPIRR, NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 219.100.0.0/22 | Route object only in JPIRR, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 219.109.64.0/20 | Route object only in JPIRR, NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 14.1.8.0/21 | Route object only in JPIRR, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 2405:ed00::/32 | Route object only in JPIRR. Add it in the RIR database for the space. |
Route objects not announced
Every route object with origin AS10000 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.