bgpreport

Network · data from 2026-11-12

AS18038 KNUE-AS-KR-KR - Korea National University of Education

Registry name: KNUE-AS-KR-KR - Korea National University of Education, KR · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS18038, 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.

117.17.208.0/24 No ROA None 673 100% 67
117.17.209.0/24 No ROA None 673 100% 67
210.93.96.0/21 No ROA Nonecovered by 210.93.96.0/20 673 100% 67
210.93.104.0/21 No ROA Nonecovered by 210.93.96.0/20 673 100% 67
210.110.70.0/24 No ROA Nonecovered by 210.110.70.0/23 673 100% 67
210.110.71.0/24 No ROA Nonecovered by 210.110.70.0/23 673 100% 67
117.17.200.0/21 No ROA Other IRR onlyRADB 673 100% 67
210.93.96.0/20 No ROA Other IRR onlyRADB 673 100% 67
210.110.70.0/23 No ROA Other IRR onlyRADB 673 100% 67
220.68.16.0/22 No ROA Other IRR onlyRADB 673 100% 67
220.68.20.0/24 No ROA Other IRR onlyRADB 673 100% 67
222.116.143.0/24 No ROA Other IRR onlyRADB 673 100% 67
222.116.144.0/22 No ROA Other IRR onlyRADB 673 100% 67

AS-SET

AS18038 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: none13
  • Route object: none6
  • Route object: RIR7
ChangePrefix or setDetailFull-table peers
ROA: none117.17.208.0/24No ROA covers it. Add a ROA for AS18038, maxLength 24.673 of 673
Route object: none117.17.208.0/24No route object for it. Add a route object with origin AS18038 in the RIR database for the space.673 of 673
ROA: none117.17.209.0/24No ROA covers it. Add a ROA for AS18038, maxLength 24.673 of 673
Route object: none117.17.209.0/24No route object for it. Add a route object with origin AS18038 in the RIR database for the space.673 of 673
ROA: none210.93.96.0/21No ROA covers it. Add a ROA for AS18038, maxLength 21.673 of 673
Route object: none210.93.96.0/21No route object for it. A route object for 210.93.96.0/20 with origin AS18038 covers it (filters allowing more-specifics accept it). Add a route object with origin AS18038 in the RIR database for the space.673 of 673
ROA: none210.93.104.0/21No ROA covers it. Add a ROA for AS18038, maxLength 21.673 of 673
Route object: none210.93.104.0/21No route object for it. A route object for 210.93.96.0/20 with origin AS18038 covers it (filters allowing more-specifics accept it). Add a route object with origin AS18038 in the RIR database for the space.673 of 673
ROA: none210.110.70.0/24No ROA covers it. Add a ROA for AS18038, maxLength 24.673 of 673
Route object: none210.110.70.0/24No route object for it. A route object for 210.110.70.0/23 with origin AS18038 covers it (filters allowing more-specifics accept it). Add a route object with origin AS18038 in the RIR database for the space.673 of 673
ROA: none210.110.71.0/24No ROA covers it. Add a ROA for AS18038, maxLength 24.673 of 673
Route object: none210.110.71.0/24No route object for it. A route object for 210.110.70.0/23 with origin AS18038 covers it (filters allowing more-specifics accept it). Add a route object with origin AS18038 in the RIR database for the space.673 of 673
ROA: none117.17.200.0/21No ROA covers it. Add a ROA for AS18038, maxLength 21.673 of 673
Route object: RIR117.17.200.0/21Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none210.93.96.0/20No ROA covers it. Add a ROA for AS18038, maxLength 20.673 of 673
Route object: RIR210.93.96.0/20Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none210.110.70.0/23No ROA covers it. Add a ROA for AS18038, maxLength 23.673 of 673
Route object: RIR210.110.70.0/23Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none220.68.16.0/22No ROA covers it. Add a ROA for AS18038, maxLength 22.673 of 673
Route object: RIR220.68.16.0/22Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none220.68.20.0/24No ROA covers it. Add a ROA for AS18038, maxLength 24.673 of 673
Route object: RIR220.68.20.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none222.116.143.0/24No ROA covers it. Add a ROA for AS18038, maxLength 24.673 of 673
Route object: RIR222.116.143.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none222.116.144.0/22No ROA covers it. Add a ROA for AS18038, maxLength 22.673 of 673
Route object: RIR222.116.144.0/22Route object only in RADB. Add it in the RIR database for the space.673 of 673

Route objects not announced

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