bgpreport

Network · data from 2026-11-12

AS9782 WOOSONGEDU-KR - WooSong University

Registry name: WOOSONGEDU-KR - WooSong University, KR · not in PeeringDB

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

Announced routes

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

220.68.216.0/24 No ROA Nonecovered by 220.68.216.0/21 673 100% 67
220.68.217.0/24 No ROA Nonecovered by 220.68.216.0/21 673 100% 67
220.68.218.0/24 No ROA Nonecovered by 220.68.216.0/21 673 100% 67
220.68.219.0/24 No ROA Nonecovered by 220.68.216.0/21 673 100% 67
220.68.220.0/24 No ROA Nonecovered by 220.68.216.0/21 673 100% 67
220.68.221.0/24 No ROA Nonecovered by 220.68.216.0/21 673 100% 67
220.68.222.0/24 No ROA Nonecovered by 220.68.216.0/21 673 100% 67
220.68.223.0/24 No ROA Nonecovered by 220.68.216.0/21 673 100% 67
220.90.197.0/24 No ROA Nonecovered by 220.90.196.0/23 673 100% 67
59.26.6.0/24 No ROA Other IRR onlyRADB 673 100% 67
117.16.166.0/23 No ROA Other IRR onlyRADB 673 100% 67
203.230.236.0/22 No ROA Other IRR onlyRADB 673 100% 67
203.234.8.0/21 No ROA Other IRR onlyRADB 673 100% 67
220.90.177.0/24 No ROA Other IRR onlyRADB 673 100% 67
220.90.187.0/24 No ROA Other IRR onlyRADB 673 100% 67
210.93.83.0/24 No ROA Other IRR onlyRADB 672 100% 67
210.93.84.0/22 No ROA Other IRR onlyRADB 672 100% 67
210.207.190.0/23 No ROA Other IRR onlyRADB 672 100% 67
211.181.201.0/24 No ROA Other IRR onlyRADB 33 5%low visibility 26

AS-SET

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

  • ROA: none19
  • Route object: none9
  • Route object: RIR10
  • Route object: not announced22
ChangePrefix or setDetailFull-table peers
ROA: none220.68.216.0/24No ROA covers it. Add a ROA for AS9782, maxLength 24.673 of 673
Route object: none220.68.216.0/24No route object for it. A route object for 220.68.216.0/21 with origin AS9782 covers it (filters allowing more-specifics accept it). Add a route object with origin AS9782 in the RIR database for the space.673 of 673
ROA: none220.68.217.0/24No ROA covers it. Add a ROA for AS9782, maxLength 24.673 of 673
Route object: none220.68.217.0/24No route object for it. A route object for 220.68.216.0/21 with origin AS9782 covers it (filters allowing more-specifics accept it). Add a route object with origin AS9782 in the RIR database for the space.673 of 673
ROA: none220.68.218.0/24No ROA covers it. Add a ROA for AS9782, maxLength 24.673 of 673
Route object: none220.68.218.0/24No route object for it. A route object for 220.68.216.0/21 with origin AS9782 covers it (filters allowing more-specifics accept it). Add a route object with origin AS9782 in the RIR database for the space.673 of 673
ROA: none220.68.219.0/24No ROA covers it. Add a ROA for AS9782, maxLength 24.673 of 673
Route object: none220.68.219.0/24No route object for it. A route object for 220.68.216.0/21 with origin AS9782 covers it (filters allowing more-specifics accept it). Add a route object with origin AS9782 in the RIR database for the space.673 of 673
ROA: none220.68.220.0/24No ROA covers it. Add a ROA for AS9782, maxLength 24.673 of 673
Route object: none220.68.220.0/24No route object for it. A route object for 220.68.216.0/21 with origin AS9782 covers it (filters allowing more-specifics accept it). Add a route object with origin AS9782 in the RIR database for the space.673 of 673
ROA: none220.68.221.0/24No ROA covers it. Add a ROA for AS9782, maxLength 24.673 of 673
Route object: none220.68.221.0/24No route object for it. A route object for 220.68.216.0/21 with origin AS9782 covers it (filters allowing more-specifics accept it). Add a route object with origin AS9782 in the RIR database for the space.673 of 673
ROA: none220.68.222.0/24No ROA covers it. Add a ROA for AS9782, maxLength 24.673 of 673
Route object: none220.68.222.0/24No route object for it. A route object for 220.68.216.0/21 with origin AS9782 covers it (filters allowing more-specifics accept it). Add a route object with origin AS9782 in the RIR database for the space.673 of 673
ROA: none220.68.223.0/24No ROA covers it. Add a ROA for AS9782, maxLength 24.673 of 673
Route object: none220.68.223.0/24No route object for it. A route object for 220.68.216.0/21 with origin AS9782 covers it (filters allowing more-specifics accept it). Add a route object with origin AS9782 in the RIR database for the space.673 of 673
ROA: none220.90.197.0/24No ROA covers it. Add a ROA for AS9782, maxLength 24.673 of 673
Route object: none220.90.197.0/24No route object for it. A route object for 220.90.196.0/23 with origin AS9782 covers it (filters allowing more-specifics accept it). Add a route object with origin AS9782 in the RIR database for the space.673 of 673
ROA: none59.26.6.0/24No ROA covers it. Add a ROA for AS9782, maxLength 24.673 of 673
Route object: RIR59.26.6.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none117.16.166.0/23No ROA covers it. Add a ROA for AS9782, maxLength 23.673 of 673
Route object: RIR117.16.166.0/23Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none203.230.236.0/22No ROA covers it. Add a ROA for AS9782, maxLength 22.673 of 673
Route object: RIR203.230.236.0/22Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none203.234.8.0/21No ROA covers it. Add a ROA for AS9782, maxLength 21.673 of 673
Route object: RIR203.234.8.0/21Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none220.90.177.0/24No ROA covers it. Add a ROA for AS9782, maxLength 24.673 of 673
Route object: RIR220.90.177.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none220.90.187.0/24No ROA covers it. Add a ROA for AS9782, maxLength 24.673 of 673
Route object: RIR220.90.187.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none210.93.83.0/24No ROA covers it. Add a ROA for AS9782, maxLength 24.672 of 673
Route object: RIR210.93.83.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none210.93.84.0/22No ROA covers it. Add a ROA for AS9782, maxLength 22.672 of 673
Route object: RIR210.93.84.0/22Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none210.207.190.0/23No ROA covers it. Add a ROA for AS9782, maxLength 23.672 of 673
Route object: RIR210.207.190.0/23Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none211.181.201.0/24No ROA covers it. Add a ROA for AS9782, maxLength 24.33 of 673
Route object: RIR211.181.201.0/24Route object only in RADB. Add it in the RIR database for the space.33 of 673

Route objects not announced

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

59.26.4.0/23RADBNo ROA
61.81.98.0/23RADBNo ROA
117.16.166.0/24RADBNo ROA
117.16.167.0/24RADBNo ROA
117.16.168.0/23RADBNo ROA
117.16.168.0/24RADBNo ROA
117.16.169.0/24RADBNo ROA
210.119.120.0/23RADBNo ROA
210.125.5.0/24RADBNo ROA
210.125.6.0/24RADBNo ROA
220.68.216.0/21RADBNo ROA
220.90.176.0/21RADBNo ROA
220.90.178.0/24RADBNo ROA
220.90.179.0/24RADBNo ROA
220.90.180.0/24RADBNo ROA
220.90.181.0/24RADBNo ROA
220.90.182.0/24RADBNo ROA
220.90.183.0/24RADBNo ROA
220.90.184.0/23RADBNo ROA
220.90.188.0/22RADBNo ROA
220.90.192.0/22RADBNo ROA
220.90.196.0/23RADBNo 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.