bgpreport

Network · data from 2026-11-12

AS9597 KDDI Web Communications

Registry name: CPI-NET - KDDI Web Communications Inc., JP · PeeringDB

26IPv4 routes 100.0% RPKI valid · 84.6% with a route object
1IPv6 routes 0.0% RPKI valid · 100.0% with a route object
0RPKI invalid 0 origin · 0 maxLength
1No ROA 4 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
0Route objects not announced registered with origin AS9597, seen from no peer

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% 70
118.82.64.0/19 Valid Nonecovered by 118.82.64.0/18 673 100% 67
118.82.96.0/19 Valid Nonecovered by 118.82.64.0/18 673 100% 67
122.200.192.0/19 Valid Nonecovered by 122.200.192.0/18 673 100% 67
122.200.224.0/19 Valid Nonecovered by 122.200.192.0/18 673 100% 67
27.34.128.0/19 Valid Other IRR onlyJPIRR, RADB 673 100% 67
27.34.160.0/21 Valid Other IRR onlyJPIRR, RADB 673 100% 67
110.50.192.0/19 Valid Other IRR onlyJPIRR, RADB 673 100% 67
115.146.0.0/18 Valid Other IRR onlyJPIRR, RADB 673 100% 67
117.20.96.0/20 Valid Other IRR onlyJPIRR, RADB 673 100% 67
118.82.64.0/18 Valid Other IRR onlyJPIRR, RADB 673 100% 67
122.200.192.0/18 Valid Other IRR onlyJPIRR, RADB 673 100% 67
158.199.128.0/17 Valid Other IRR onlyJPIRR, RADB 673 100% 67
180.222.72.0/21 Valid Other IRR onlyJPIRR, RADB 673 100% 67
180.222.80.0/20 Valid Other IRR onlyJPIRR, RADB 673 100% 67
180.235.224.0/19 Valid Other IRR onlyJPIRR, RADB 673 100% 67
194.91.0.0/16 Valid Other IRR onlyJPIRR, RADB 673 100% 67
202.74.16.0/20 Valid Other IRR onlyJPIRR, RADB 673 100% 67
202.133.112.0/20 Valid Other IRR onlyJPIRR, RADB 673 100% 67
202.164.224.0/19 Valid Other IRR onlyRADB 673 100% 67
202.164.224.0/20 Valid Other IRR onlyJPIRR, RADB 673 100% 67
202.164.240.0/20 Valid Other IRR onlyJPIRR, RADB 673 100% 67
211.9.192.0/19 Valid Other IRR onlyJPIRR, RADB 673 100% 67
103.197.12.0/22 Valid Other IRR onlyJPIRR, RADB 671 100% 67
192.50.199.0/24 Valid Other IRR onlyJPIRR, RADB 671 100% 67
219.100.168.0/22 Valid Other IRR onlyJPIRR, RADB 671 100% 67
150.60.0.0/16 Valid Other IRR onlyJPIRR, RADB 670 100% 67

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.

NameDatabaseASNsSets Route objectsAS9597 in itNot covered
AS-KWC RADB 1123 Yes 0
JPIRR (also) 1123 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
ChangePrefix or setDetailFull-table peers
ROA: none2402:3d00::/32No ROA covers it. Add a ROA for AS9597, maxLength 32.634 of 636
Route object: RIR2402:3d00::/32Route object only in JPIRR, RADB. Add it in the RIR database for the space.634 of 636
Route object: none118.82.64.0/19No 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.673 of 673
Route object: none118.82.96.0/19No 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.673 of 673
Route object: none122.200.192.0/19No 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.673 of 673
Route object: none122.200.224.0/19No 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.673 of 673
Route object: RIR27.34.128.0/19Route object only in JPIRR, RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR27.34.160.0/21Route object only in JPIRR, RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR110.50.192.0/19Route object only in JPIRR, RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR115.146.0.0/18Route object only in JPIRR, RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR117.20.96.0/20Route object only in JPIRR, RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR118.82.64.0/18Route object only in JPIRR, RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR122.200.192.0/18Route object only in JPIRR, RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR158.199.128.0/17Route object only in JPIRR, RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR180.222.72.0/21Route object only in JPIRR, RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR180.222.80.0/20Route object only in JPIRR, RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR180.235.224.0/19Route object only in JPIRR, RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR194.91.0.0/16Route object only in JPIRR, RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR202.74.16.0/20Route object only in JPIRR, RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR202.133.112.0/20Route object only in JPIRR, RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR202.164.224.0/19Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR202.164.224.0/20Route object only in JPIRR, RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR202.164.240.0/20Route object only in JPIRR, RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR211.9.192.0/19Route object only in JPIRR, RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR103.197.12.0/22Route object only in JPIRR, RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR192.50.199.0/24Route object only in JPIRR, RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR219.100.168.0/22Route object only in JPIRR, RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR150.60.0.0/16Route object only in JPIRR, RADB. Add it in the RIR database for the space.670 of 673

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.