bgpreport

Network · data from 2026-11-12

AS9708 pknu-as-KR - Pukyong National University

Registry name: pknu-as-KR - Pukyong National University, KR · not in PeeringDB

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

Announced routes

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

112.162.4.0/24 No ROA Nonecovered by 112.162.4.0/22 673 100% 67
112.162.5.0/24 No ROA Nonecovered by 112.162.4.0/22 673 100% 67
112.162.6.0/24 No ROA Nonecovered by 112.162.4.0/22 673 100% 67
112.162.7.0/24 No ROA Nonecovered by 112.162.4.0/22 673 100% 67
124.139.234.0/24 No ROA Nonecovered by 124.139.234.0/23 673 100% 67
218.146.144.0/24 No ROA Nonecovered by 218.146.144.0/23 673 100% 67
218.146.145.0/24 No ROA Nonecovered by 218.146.144.0/23 673 100% 67
203.250.124.0/28 No ROA Nonecovered by 203.250.120.0/21 13 2%low visibility 13
58.103.160.0/21 No ROA Other IRR onlyRADB 673 100% 67
58.103.168.0/23 No ROA Other IRR onlyRADB 673 100% 67
121.174.50.0/24 No ROA Other IRR onlyRADB 673 100% 67
121.174.96.0/24 No ROA Other IRR onlyRADB 673 100% 67
175.214.180.0/22 No ROA Other IRR onlyRADB 673 100% 67
203.247.166.0/24 No ROA Other IRR onlyNTTCOM, RADB 673 100% 67
203.250.120.0/21 No ROA Other IRR onlyNTTCOM, RADB 673 100% 67
210.98.32.0/21 No ROA Other IRR onlyRADB 673 100% 67
210.107.208.0/22 No ROA Other IRR onlyNTTCOM, RADB 673 100% 67
210.110.136.0/23 No ROA Other IRR onlyNTTCOM, RADB 673 100% 67
210.110.138.0/24 No ROA Other IRR onlyNTTCOM, RADB 673 100% 67
210.119.0.0/20 No ROA Other IRR onlyRADB 673 100% 67
210.119.16.0/22 No ROA Other IRR onlyRADB 673 100% 67
210.119.22.0/24 No ROA Other IRR onlyRADB 673 100% 67
210.125.108.0/22 No ROA Other IRR onlyNTTCOM, RADB 673 100% 67
210.125.112.0/20 No ROA Other IRR onlyNTTCOM, RADB 673 100% 67
218.146.146.0/24 No ROA Other IRR onlyRADB 673 100% 67
220.66.243.0/24 No ROA Other IRR onlyNTTCOM, RADB 673 100% 67
220.92.62.0/23 No ROA Other IRR onlyNTTCOM, RADB 673 100% 67
220.92.64.0/23 No ROA Other IRR onlyNTTCOM, RADB 673 100% 67
14.44.112.0/20 No ROA Other IRR onlyRADB 672 100% 67

AS-SET

AS9708 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 92 are in fix.csv.

  • ROA: none29
  • Route object: none8
  • Route object: RIR21
  • Route object: not announced34
ChangePrefix or setDetailFull-table peers
ROA: none112.162.4.0/24No ROA covers it. Add a ROA for AS9708, maxLength 24.673 of 673
Route object: none112.162.4.0/24No route object for it. A route object for 112.162.4.0/22 with origin AS9708 covers it (filters allowing more-specifics accept it). Add a route object with origin AS9708 in the RIR database for the space.673 of 673
ROA: none112.162.5.0/24No ROA covers it. Add a ROA for AS9708, maxLength 24.673 of 673
Route object: none112.162.5.0/24No route object for it. A route object for 112.162.4.0/22 with origin AS9708 covers it (filters allowing more-specifics accept it). Add a route object with origin AS9708 in the RIR database for the space.673 of 673
ROA: none112.162.6.0/24No ROA covers it. Add a ROA for AS9708, maxLength 24.673 of 673
Route object: none112.162.6.0/24No route object for it. A route object for 112.162.4.0/22 with origin AS9708 covers it (filters allowing more-specifics accept it). Add a route object with origin AS9708 in the RIR database for the space.673 of 673
ROA: none112.162.7.0/24No ROA covers it. Add a ROA for AS9708, maxLength 24.673 of 673
Route object: none112.162.7.0/24No route object for it. A route object for 112.162.4.0/22 with origin AS9708 covers it (filters allowing more-specifics accept it). Add a route object with origin AS9708 in the RIR database for the space.673 of 673
ROA: none124.139.234.0/24No ROA covers it. Add a ROA for AS9708, maxLength 24.673 of 673
Route object: none124.139.234.0/24No route object for it. A route object for 124.139.234.0/23 with origin AS9708 covers it (filters allowing more-specifics accept it). Add a route object with origin AS9708 in the RIR database for the space.673 of 673
ROA: none218.146.144.0/24No ROA covers it. Add a ROA for AS9708, maxLength 24.673 of 673
Route object: none218.146.144.0/24No route object for it. A route object for 218.146.144.0/23 with origin AS9708 covers it (filters allowing more-specifics accept it). Add a route object with origin AS9708 in the RIR database for the space.673 of 673
ROA: none218.146.145.0/24No ROA covers it. Add a ROA for AS9708, maxLength 24.673 of 673
Route object: none218.146.145.0/24No route object for it. A route object for 218.146.144.0/23 with origin AS9708 covers it (filters allowing more-specifics accept it). Add a route object with origin AS9708 in the RIR database for the space.673 of 673
ROA: none203.250.124.0/28No ROA covers it. Add a ROA for AS9708, maxLength 28.13 of 673
Route object: none203.250.124.0/28No route object for it. A route object for 203.250.120.0/21 with origin AS9708 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS9708 in the RIR database for the space.13 of 673
ROA: none58.103.160.0/21No ROA covers it. Add a ROA for AS9708, maxLength 21.673 of 673
Route object: RIR58.103.160.0/21Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none58.103.168.0/23No ROA covers it. Add a ROA for AS9708, maxLength 23.673 of 673
Route object: RIR58.103.168.0/23Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none121.174.50.0/24No ROA covers it. Add a ROA for AS9708, maxLength 24.673 of 673
Route object: RIR121.174.50.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none121.174.96.0/24No ROA covers it. Add a ROA for AS9708, maxLength 24.673 of 673
Route object: RIR121.174.96.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none175.214.180.0/22No ROA covers it. Add a ROA for AS9708, maxLength 22.673 of 673
Route object: RIR175.214.180.0/22Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none203.247.166.0/24No ROA covers it. Add a ROA for AS9708, maxLength 24.673 of 673
Route object: RIR203.247.166.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.673 of 673
ROA: none203.250.120.0/21No ROA covers it. Add a ROA for AS9708, maxLength 21.673 of 673
Route object: RIR203.250.120.0/21Route object only in NTTCOM, RADB. Add it in the RIR database for the space.673 of 673
ROA: none210.98.32.0/21No ROA covers it. Add a ROA for AS9708, maxLength 21.673 of 673
Route object: RIR210.98.32.0/21Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none210.107.208.0/22No ROA covers it. Add a ROA for AS9708, maxLength 22.673 of 673
Route object: RIR210.107.208.0/22Route object only in NTTCOM, RADB. Add it in the RIR database for the space.673 of 673
ROA: none210.110.136.0/23No ROA covers it. Add a ROA for AS9708, maxLength 23.673 of 673
Route object: RIR210.110.136.0/23Route object only in NTTCOM, RADB. Add it in the RIR database for the space.673 of 673
ROA: none210.110.138.0/24No ROA covers it. Add a ROA for AS9708, maxLength 24.673 of 673
Route object: RIR210.110.138.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.673 of 673
ROA: none210.119.0.0/20No ROA covers it. Add a ROA for AS9708, maxLength 20.673 of 673
Route object: RIR210.119.0.0/20Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none210.119.16.0/22No ROA covers it. Add a ROA for AS9708, maxLength 22.673 of 673
Route object: RIR210.119.16.0/22Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none210.119.22.0/24No ROA covers it. Add a ROA for AS9708, maxLength 24.673 of 673
Route object: RIR210.119.22.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none210.125.108.0/22No ROA covers it. Add a ROA for AS9708, maxLength 22.673 of 673
Route object: RIR210.125.108.0/22Route object only in NTTCOM, RADB. Add it in the RIR database for the space.673 of 673
ROA: none210.125.112.0/20No ROA covers it. Add a ROA for AS9708, maxLength 20.673 of 673
Route object: RIR210.125.112.0/20Route object only in NTTCOM, RADB. Add it in the RIR database for the space.673 of 673
ROA: none218.146.146.0/24No ROA covers it. Add a ROA for AS9708, maxLength 24.673 of 673
Route object: RIR218.146.146.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none220.66.243.0/24No ROA covers it. Add a ROA for AS9708, maxLength 24.673 of 673
Route object: RIR220.66.243.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.673 of 673
ROA: none220.92.62.0/23No ROA covers it. Add a ROA for AS9708, maxLength 23.673 of 673
Route object: RIR220.92.62.0/23Route object only in NTTCOM, RADB. Add it in the RIR database for the space.673 of 673
ROA: none220.92.64.0/23No ROA covers it. Add a ROA for AS9708, maxLength 23.673 of 673
Route object: RIR220.92.64.0/23Route object only in NTTCOM, RADB. Add it in the RIR database for the space.673 of 673
ROA: none14.44.112.0/20No ROA covers it. Add a ROA for AS9708, maxLength 20.672 of 673
Route object: RIR14.44.112.0/20Route object only in RADB. Add it in the RIR database for the space.672 of 673

Route objects not announced

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

112.162.4.0/22RADBNo ROA
124.139.234.0/23RADBNo ROA
124.139.236.0/23RADBNo ROA
124.139.238.0/24RADBNo ROA
210.98.32.0/24NTTCOM, RADBNo ROA
210.98.33.0/24NTTCOM, RADBNo ROA
210.98.34.0/24NTTCOM, RADBNo ROA
210.98.35.0/24NTTCOM, RADBNo ROA
210.98.36.0/24NTTCOM, RADBNo ROA
210.98.37.0/24NTTCOM, RADBNo ROA
210.98.38.0/24NTTCOM, RADBNo ROA
210.98.39.0/24NTTCOM, RADBNo ROA
210.119.0.0/24NTTCOM, RADBNo ROA
210.119.1.0/24NTTCOM, RADBNo ROA
210.119.2.0/24NTTCOM, RADBNo ROA
210.119.3.0/24NTTCOM, RADBNo ROA
210.119.4.0/24NTTCOM, RADBNo ROA
210.119.5.0/24NTTCOM, RADBNo ROA
210.119.6.0/24NTTCOM, RADBNo ROA
210.119.7.0/24NTTCOM, RADBNo ROA
210.119.8.0/24NTTCOM, RADBNo ROA
210.119.9.0/24NTTCOM, RADBNo ROA
210.119.10.0/24NTTCOM, RADBNo ROA
210.119.11.0/24NTTCOM, RADBNo ROA
210.119.12.0/24NTTCOM, RADBNo ROA
210.119.13.0/24NTTCOM, RADBNo ROA
210.119.14.0/24NTTCOM, RADBNo ROA
210.119.15.0/24NTTCOM, RADBNo ROA
210.119.16.0/24NTTCOM, RADBNo ROA
210.119.17.0/24NTTCOM, RADBNo ROA
210.119.18.0/24NTTCOM, RADBNo ROA
210.119.19.0/24NTTCOM, RADBNo ROA
218.146.144.0/23RADBNo ROA
220.92.66.0/24NTTCOM, 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.