bgpreport

Network · data from 2026-11-12

AS2504 NCA5 - Kyoto University

Registry name: NCA5 - Kyoto University, JP · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS2504, 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.
130.54.0.0/16 No ROA Other IRR onlyJPIRR 672 100% 69
133.3.0.0/16 No ROA Other IRR onlyJPIRR 672 100% 69
192.50.8.0/23 No ROA Other IRR onlyJPIRR 670 100% 69
192.50.24.0/23 Valid Other IRR onlyJPIRR 670 100% 69

AS-SET

AS2504 isn't in PeeringDB, where networks name their 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 26 are in fix.csv.

  • ROA: none3
  • Route object: RIR4
  • Route object: not announced19
ChangePrefix or setDetailFull-table peers
ROA: none130.54.0.0/16No ROA covers it. Add a ROA for AS2504, maxLength 16.672 of 673
Route object: RIR130.54.0.0/16Route object only in JPIRR. Add it in the RIR database for the space.672 of 673
ROA: none133.3.0.0/16No ROA covers it. Add a ROA for AS2504, maxLength 16.672 of 673
Route object: RIR133.3.0.0/16Route object only in JPIRR. Add it in the RIR database for the space.672 of 673
ROA: none192.50.8.0/23No ROA covers it. Add a ROA for AS2504, maxLength 23.670 of 673
Route object: RIR192.50.8.0/23Route object only in JPIRR. Add it in the RIR database for the space.670 of 673
Route object: RIR192.50.24.0/23Route object only in JPIRR. Add it in the RIR database for the space.670 of 673

Route objects not announced

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

202.19.144.0/21JPIRR, NTTCOM, RADBNo ROA
202.25.113.0/24NTTCOMNo ROA
202.26.188.0/22JPIRRNo ROA
202.209.176.0/22JPIRRInvalid: origin
202.209.200.0/23JPIRRInvalid: origin
202.209.202.0/24JPIRRInvalid: origin
202.209.212.0/22JPIRRInvalid: origin
202.223.142.0/24JPIRRNo ROA
202.223.162.0/24JPIRRNo ROA
202.223.245.0/24JPIRRNo ROA
202.231.40.0/22JPIRRInvalid: origin
202.236.120.0/24NTTCOMNo ROA
202.242.100.0/24JPIRRNo ROA
202.245.124.0/24JPIRRNo ROA
202.252.197.0/24JPIRRNo ROA
202.252.247.0/24JPIRRNo ROA
210.137.69.0/24JPIRRInvalid: origin
210.137.70.0/23JPIRRInvalid: origin
210.137.172.0/24JPIRRInvalid: origin

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.