bgpreport

Network · data from 2026-11-12

AS24282 KAGOYA JAPAN

Registry name: KIR - KAGOYA JAPAN Inc., JP · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS24282, 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.
103.3.48.0/22 No ROA Other IRR onlyJPIRR, RADB 671 100% 67
124.248.144.0/20 No ROA Other IRR onlyJPIRR, RADB 671 100% 67
133.18.0.0/16 No ROA Other IRR onlyJPIRR, RADB 671 100% 67
153.127.224.0/19 No ROA Other IRR onlyJPIRR, RADB 671 100% 67
203.142.192.0/20 No ROA Other IRR onlyJPIRR, RADB 671 100% 67
203.142.208.0/21 No ROA Other IRR onlyJPIRR, RADB 671 100% 67
210.134.48.0/20 No ROA Other IRR onlyJPIRR, RADB 670 100% 67
2406:8c00::/32 No ROA Other IRR onlyJPIRR, RADB 636 100% 70

AS-SET

AS24282'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 18 are in fix.csv.

  • ROA: none8
  • Route object: RIR8
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: none103.3.48.0/22No ROA covers it. Add a ROA for AS24282, maxLength 22.671 of 673
Route object: RIR103.3.48.0/22Route object only in JPIRR, RADB. Add it in the RIR database for the space.671 of 673
ROA: none124.248.144.0/20No ROA covers it. Add a ROA for AS24282, maxLength 20.671 of 673
Route object: RIR124.248.144.0/20Route object only in JPIRR, RADB. Add it in the RIR database for the space.671 of 673
ROA: none133.18.0.0/16No ROA covers it. Add a ROA for AS24282, maxLength 16.671 of 673
Route object: RIR133.18.0.0/16Route object only in JPIRR, RADB. Add it in the RIR database for the space.671 of 673
ROA: none153.127.224.0/19No ROA covers it. Add a ROA for AS24282, maxLength 19.671 of 673
Route object: RIR153.127.224.0/19Route object only in JPIRR, RADB. Add it in the RIR database for the space.671 of 673
ROA: none203.142.192.0/20No ROA covers it. Add a ROA for AS24282, maxLength 20.671 of 673
Route object: RIR203.142.192.0/20Route object only in JPIRR, RADB. Add it in the RIR database for the space.671 of 673
ROA: none203.142.208.0/21No ROA covers it. Add a ROA for AS24282, maxLength 21.671 of 673
Route object: RIR203.142.208.0/21Route object only in JPIRR, RADB. Add it in the RIR database for the space.671 of 673
ROA: none210.134.48.0/20No ROA covers it. Add a ROA for AS24282, maxLength 20.670 of 673
Route object: RIR210.134.48.0/20Route object only in JPIRR, RADB. Add it in the RIR database for the space.670 of 673
ROA: none2406:8c00::/32No ROA covers it. Add a ROA for AS24282, maxLength 32.636 of 636
Route object: RIR2406:8c00::/32Route object only in JPIRR, RADB. Add it in the RIR database for the space.636 of 636

Route objects not announced

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

133.18.0.0/17RADBNo ROA
220.145.128.0/18JPIRR, RADBNo 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.