Network · data from 2026-11-12
AS9597 KDDI Web Communications
Registry name: CPI-NET - KDDI Web Communications Inc., JP · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS9597, 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.
| 2402:3d00::/32 | No ROA | Other IRR onlyJPIRR, RADB | 634 100% |
| 118.82.64.0/19 | Valid | Nonecovered by 118.82.64.0/18 | 673 100% |
| 118.82.96.0/19 | Valid | Nonecovered by 118.82.64.0/18 | 673 100% |
| 122.200.192.0/19 | Valid | Nonecovered by 122.200.192.0/18 | 673 100% |
| 122.200.224.0/19 | Valid | Nonecovered by 122.200.192.0/18 | 673 100% |
| 27.34.128.0/19 | Valid | Other IRR onlyJPIRR, RADB | 673 100% |
| 27.34.160.0/21 | Valid | Other IRR onlyJPIRR, RADB | 673 100% |
| 110.50.192.0/19 | Valid | Other IRR onlyJPIRR, RADB | 673 100% |
| 115.146.0.0/18 | Valid | Other IRR onlyJPIRR, RADB | 673 100% |
| 117.20.96.0/20 | Valid | Other IRR onlyJPIRR, RADB | 673 100% |
| 118.82.64.0/18 | Valid | Other IRR onlyJPIRR, RADB | 673 100% |
| 122.200.192.0/18 | Valid | Other IRR onlyJPIRR, RADB | 673 100% |
| 158.199.128.0/17 | Valid | Other IRR onlyJPIRR, RADB | 673 100% |
| 180.222.72.0/21 | Valid | Other IRR onlyJPIRR, RADB | 673 100% |
| 180.222.80.0/20 | Valid | Other IRR onlyJPIRR, RADB | 673 100% |
| 180.235.224.0/19 | Valid | Other IRR onlyJPIRR, RADB | 673 100% |
| 194.91.0.0/16 | Valid | Other IRR onlyJPIRR, RADB | 673 100% |
| 202.74.16.0/20 | Valid | Other IRR onlyJPIRR, RADB | 673 100% |
| 202.133.112.0/20 | Valid | Other IRR onlyJPIRR, RADB | 673 100% |
| 202.164.224.0/19 | Valid | Other IRR onlyRADB | 673 100% |
| 202.164.224.0/20 | Valid | Other IRR onlyJPIRR, RADB | 673 100% |
| 202.164.240.0/20 | Valid | Other IRR onlyJPIRR, RADB | 673 100% |
| 211.9.192.0/19 | Valid | Other IRR onlyJPIRR, RADB | 673 100% |
| 103.197.12.0/22 | Valid | Other IRR onlyJPIRR, RADB | 671 100% |
| 192.50.199.0/24 | Valid | Other IRR onlyJPIRR, RADB | 671 100% |
| 219.100.168.0/22 | Valid | Other IRR onlyJPIRR, RADB | 671 100% |
| 150.60.0.0/16 | Valid | Other IRR onlyJPIRR, RADB | 670 100% |
AS-SET
PeeringDB's irr_as_set for AS9597: AS-KWC. 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 (AS9597 isn't in the set, or no route object for AS9597 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 | AS9597 in it | Not covered |
|---|---|---|---|---|---|
| AS-KWC | RADB | 1 | 1 | Yes | 0 |
| JPIRR (also) | 1 | 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 28 are in fix.csv.
- ROA: none1
- Route object: none4
- Route object: RIR23
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 2402:3d00::/32 | No ROA covers it. Add a ROA for AS9597, maxLength 32. |
| Route object: RIR | 2402:3d00::/32 | Route object only in JPIRR, RADB. Add it in the RIR database for the space. |
| Route object: none | 118.82.64.0/19 | No route object for it. A route object for 118.82.64.0/18 with origin AS9597 covers it (filters allowing more-specifics accept it). Add a route object with origin AS9597 in the RIR database for the space. |
| Route object: none | 118.82.96.0/19 | No route object for it. A route object for 118.82.64.0/18 with origin AS9597 covers it (filters allowing more-specifics accept it). Add a route object with origin AS9597 in the RIR database for the space. |
| Route object: none | 122.200.192.0/19 | No route object for it. A route object for 122.200.192.0/18 with origin AS9597 covers it (filters allowing more-specifics accept it). Add a route object with origin AS9597 in the RIR database for the space. |
| Route object: none | 122.200.224.0/19 | No route object for it. A route object for 122.200.192.0/18 with origin AS9597 covers it (filters allowing more-specifics accept it). Add a route object with origin AS9597 in the RIR database for the space. |
| Route object: RIR | 27.34.128.0/19 | Route object only in JPIRR, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 27.34.160.0/21 | Route object only in JPIRR, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 110.50.192.0/19 | Route object only in JPIRR, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 115.146.0.0/18 | Route object only in JPIRR, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 117.20.96.0/20 | Route object only in JPIRR, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 118.82.64.0/18 | Route object only in JPIRR, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 122.200.192.0/18 | Route object only in JPIRR, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 158.199.128.0/17 | Route object only in JPIRR, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 180.222.72.0/21 | Route object only in JPIRR, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 180.222.80.0/20 | Route object only in JPIRR, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 180.235.224.0/19 | Route object only in JPIRR, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 194.91.0.0/16 | Route object only in JPIRR, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 202.74.16.0/20 | Route object only in JPIRR, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 202.133.112.0/20 | Route object only in JPIRR, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 202.164.224.0/19 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 202.164.224.0/20 | Route object only in JPIRR, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 202.164.240.0/20 | Route object only in JPIRR, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 211.9.192.0/19 | Route object only in JPIRR, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 103.197.12.0/22 | Route object only in JPIRR, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 192.50.199.0/24 | Route object only in JPIRR, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 219.100.168.0/22 | Route object only in JPIRR, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 150.60.0.0/16 | Route object only in JPIRR, RADB. Add it in the RIR database for the space. |
Route objects not announced
Every route object with origin AS9597 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.