bgpreport

Network · data from 2026-11-12

AS9868 CUTH-AS-KR - Catholic University of DAEGU

Registry name: CUTH-AS-KR - Catholic University of DAEGU, KR · not in PeeringDB

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

Announced routes

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

211.48.183.0/25 No ROA None 16 2%low visibility 13
114.71.22.0/23 No ROA Other IRR onlyRADB 673 100% 66
114.71.24.0/21 No ROA Other IRR onlyRADB 673 100% 66
114.71.32.0/22 No ROA Other IRR onlyRADB 673 100% 66
114.71.176.0/20 No ROA Other IRR onlyRADB 673 100% 66
114.71.192.0/24 No ROA Other IRR onlyRADB 673 100% 66
116.90.216.0/21 No ROA Other IRR onlyRADB 673 100% 66
117.17.240.0/21 No ROA Other IRR onlyRADB 673 100% 66
117.17.248.0/23 No ROA Other IRR onlyRADB 673 100% 66
203.250.32.0/21 No ROA Other IRR onlyRADB 673 100% 67
203.250.40.0/21 No ROA Other IRR onlyRADB 673 100% 67
203.250.48.0/21 No ROA Other IRR onlyRADB 673 100% 67
203.250.56.0/21 No ROA Other IRR onlyRADB 673 100% 66
211.48.171.0/24 No ROA Other IRR onlyRADB 673 100% 66

AS-SET

AS9868 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 45 are in fix.csv.

  • ROA: none14
  • Route object: none1
  • Route object: RIR13
  • Route object: not announced17
ChangePrefix or setDetailFull-table peers
ROA: none211.48.183.0/25No ROA covers it. Add a ROA for AS9868, maxLength 25.16 of 673
Route object: none211.48.183.0/25No route object for it. Add a route object with origin AS9868 in the RIR database for the space.16 of 673
ROA: none114.71.22.0/23No ROA covers it. Add a ROA for AS9868, maxLength 23.673 of 673
Route object: RIR114.71.22.0/23Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none114.71.24.0/21No ROA covers it. Add a ROA for AS9868, maxLength 21.673 of 673
Route object: RIR114.71.24.0/21Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none114.71.32.0/22No ROA covers it. Add a ROA for AS9868, maxLength 22.673 of 673
Route object: RIR114.71.32.0/22Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none114.71.176.0/20No ROA covers it. Add a ROA for AS9868, maxLength 20.673 of 673
Route object: RIR114.71.176.0/20Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none114.71.192.0/24No ROA covers it. Add a ROA for AS9868, maxLength 24.673 of 673
Route object: RIR114.71.192.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none116.90.216.0/21No ROA covers it. Add a ROA for AS9868, maxLength 21.673 of 673
Route object: RIR116.90.216.0/21Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none117.17.240.0/21No ROA covers it. Add a ROA for AS9868, maxLength 21.673 of 673
Route object: RIR117.17.240.0/21Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none117.17.248.0/23No ROA covers it. Add a ROA for AS9868, maxLength 23.673 of 673
Route object: RIR117.17.248.0/23Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none203.250.32.0/21No ROA covers it. Add a ROA for AS9868, maxLength 21.673 of 673
Route object: RIR203.250.32.0/21Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none203.250.40.0/21No ROA covers it. Add a ROA for AS9868, maxLength 21.673 of 673
Route object: RIR203.250.40.0/21Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none203.250.48.0/21No ROA covers it. Add a ROA for AS9868, maxLength 21.673 of 673
Route object: RIR203.250.48.0/21Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none203.250.56.0/21No ROA covers it. Add a ROA for AS9868, maxLength 21.673 of 673
Route object: RIR203.250.56.0/21Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none211.48.171.0/24No ROA covers it. Add a ROA for AS9868, maxLength 24.673 of 673
Route object: RIR211.48.171.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673

Route objects not announced

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

114.71.20.0/22RADBNo ROA
114.71.192.0/23RADBNo ROA
114.71.194.0/24RADBNo ROA
117.17.240.0/24RADBNo ROA
117.17.241.0/24RADBNo ROA
117.17.242.0/24RADBNo ROA
117.17.243.0/24RADBNo ROA
117.17.244.0/24RADBNo ROA
117.17.245.0/24RADBNo ROA
117.17.246.0/24RADBNo ROA
117.17.247.0/24RADBNo ROA
117.17.248.0/24RADBNo ROA
117.17.249.0/24RADBNo ROA
203.250.32.0/19RADBNo ROA
211.48.183.0/26RADBNo ROA
222.238.16.0/21RADBNo ROA
222.238.24.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.