bgpreport

Network · data from 2026-11-12

AS7502 Advanced Software Technology & Management Research Institute of KYOTO

Registry name: IP-KYOTO - Advanced Software Technology & Management Research Institute of KYOTO, JP · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS7502, 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.
163.208.0.0/16 No ROA Other IRR onlyJPIRR, NTTCOM, RADB 673 100% 67
163.208.0.0/17 No ROA Other IRR onlyJPIRR, NTTCOM, RADB 673 100% 67
163.208.128.0/19 No ROA Other IRR onlyJPIRR, NTTCOM, RADB 673 100% 67
163.208.192.0/19 No ROA Other IRR onlyJPIRR, NTTCOM, RADB 673 100% 67
210.134.96.0/19 No ROA Other IRR onlyJPIRR, NTTCOM, RADB 672 100% 67
202.245.159.0/24 No ROA Other IRR onlyJPIRR, NTTCOM, RADB 671 100% 67
202.245.160.0/24 No ROA Other IRR onlyJPIRR, NTTCOM, RADB 671 100% 67

AS-SET

AS7502's PeeringDB record names no AS-SET.

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 23 are in fix.csv.

  • ROA: none7
  • Route object: RIR7
  • Route object: not announced9
ChangePrefix or setDetailFull-table peers
ROA: none163.208.0.0/16No ROA covers it. Add a ROA for AS7502, maxLength 16.673 of 673
Route object: RIR163.208.0.0/16Route object only in JPIRR, NTTCOM, RADB. Add it in the RIR database for the space.673 of 673
ROA: none163.208.0.0/17No ROA covers it. Add a ROA for AS7502, maxLength 17.673 of 673
Route object: RIR163.208.0.0/17Route object only in JPIRR, NTTCOM, RADB. Add it in the RIR database for the space.673 of 673
ROA: none163.208.128.0/19No ROA covers it. Add a ROA for AS7502, maxLength 19.673 of 673
Route object: RIR163.208.128.0/19Route object only in JPIRR, NTTCOM, RADB. Add it in the RIR database for the space.673 of 673
ROA: none163.208.192.0/19No ROA covers it. Add a ROA for AS7502, maxLength 19.673 of 673
Route object: RIR163.208.192.0/19Route object only in JPIRR, NTTCOM, RADB. Add it in the RIR database for the space.673 of 673
ROA: none210.134.96.0/19No ROA covers it. Add a ROA for AS7502, maxLength 19.672 of 673
Route object: RIR210.134.96.0/19Route object only in JPIRR, NTTCOM, RADB. Add it in the RIR database for the space.672 of 673
ROA: none202.245.159.0/24No ROA covers it. Add a ROA for AS7502, maxLength 24.671 of 673
Route object: RIR202.245.159.0/24Route object only in JPIRR, NTTCOM, RADB. Add it in the RIR database for the space.671 of 673
ROA: none202.245.160.0/24No ROA covers it. Add a ROA for AS7502, maxLength 24.671 of 673
Route object: RIR202.245.160.0/24Route object only in JPIRR, NTTCOM, RADB. Add it in the RIR database for the space.671 of 673

Route objects not announced

Route objects with origin AS7502 whose prefix no peer sees AS7502 announce. Many are kept on purpose (backup routes, space announced only in some places).

158.198.0.0/16RADBNo ROA
163.208.0.0/24RADBNo ROA
163.208.176.0/20NTTCOMNo ROA
163.208.224.0/20JPIRR, NTTCOMNo ROA
192.50.154.0/24NTTCOM, RADBNo ROA
192.50.200.0/24RADBNo ROA
202.250.32.0/24RADBNo ROA
210.134.96.0/20JPIRR, NTTCOMNo ROA
210.134.112.0/20JPIRR, NTTCOMNo 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.