bgpreport

Network · data from 2026-11-12

AS9954 kunsan-as-KR - Kunsan National University (KNU)

Registry name: kunsan-as-KR - Kunsan National University (KNU), KR · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS9954, 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.
59.2.112.0/24 No ROA Other IRR onlyRADB 673 100% 67
117.17.108.0/22 No ROA Other IRR onlyRADB 673 100% 66
117.17.112.0/23 No ROA Other IRR onlyRADB 673 100% 66
202.30.55.0/24 No ROA Other IRR onlyRADB 673 100% 66
202.31.144.0/21 No ROA Other IRR onlyRADB 673 100% 66
203.234.48.0/20 No ROA Other IRR onlyRADB 673 100% 66
211.230.220.0/23 No ROA Other IRR onlyRADB 673 100% 66
220.68.22.0/23 No ROA Other IRR onlyRADB 673 100% 66
220.68.24.0/22 No ROA Other IRR onlyRADB 673 100% 66
211.230.222.0/24 No ROA Other IRR onlyRADB 671 100% 66

AS-SET

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

  • ROA: none10
  • Route object: RIR10
ChangePrefix or setDetailFull-table peers
ROA: none59.2.112.0/24No ROA covers it. Add a ROA for AS9954, maxLength 24.673 of 673
Route object: RIR59.2.112.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none117.17.108.0/22No ROA covers it. Add a ROA for AS9954, maxLength 22.673 of 673
Route object: RIR117.17.108.0/22Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none117.17.112.0/23No ROA covers it. Add a ROA for AS9954, maxLength 23.673 of 673
Route object: RIR117.17.112.0/23Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none202.30.55.0/24No ROA covers it. Add a ROA for AS9954, maxLength 24.673 of 673
Route object: RIR202.30.55.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none202.31.144.0/21No ROA covers it. Add a ROA for AS9954, maxLength 21.673 of 673
Route object: RIR202.31.144.0/21Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none203.234.48.0/20No ROA covers it. Add a ROA for AS9954, maxLength 20.673 of 673
Route object: RIR203.234.48.0/20Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none211.230.220.0/23No ROA covers it. Add a ROA for AS9954, maxLength 23.673 of 673
Route object: RIR211.230.220.0/23Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none220.68.22.0/23No ROA covers it. Add a ROA for AS9954, maxLength 23.673 of 673
Route object: RIR220.68.22.0/23Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none220.68.24.0/22No ROA covers it. Add a ROA for AS9954, maxLength 22.673 of 673
Route object: RIR220.68.24.0/22Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none211.230.222.0/24No ROA covers it. Add a ROA for AS9954, maxLength 24.671 of 673
Route object: RIR211.230.222.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673

Route objects not announced

Every route object with origin AS9954 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.