bgpreport

Network · data from 2026-11-12

AS38104 HYEJEON-AS-KR-KR - Hyejeon University

Registry name: HYEJEON-AS-KR-KR - Hyejeon University, KR · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS38104, 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.25.64.0/24 No ROA None 673 100% 67
59.25.65.0/24 No ROA None 673 100% 67
59.25.66.0/24 No ROA None 673 100% 67
59.25.67.0/24 No ROA None 673 100% 67
59.25.68.0/24 No ROA None 673 100% 67
61.34.157.0/24 No ROA Other origin only 673 100% 67

AS-SET

AS38104 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 28 are in fix.csv.

  • ROA: none6
  • Route object: none6
  • Route object: not announced16
ChangePrefix or setDetailFull-table peers
ROA: none59.25.64.0/24No ROA covers it. Add a ROA for AS38104, maxLength 24.673 of 673
Route object: none59.25.64.0/24No route object for it. Add a route object with origin AS38104 in the RIR database for the space.673 of 673
ROA: none59.25.65.0/24No ROA covers it. Add a ROA for AS38104, maxLength 24.673 of 673
Route object: none59.25.65.0/24No route object for it. Add a route object with origin AS38104 in the RIR database for the space.673 of 673
ROA: none59.25.66.0/24No ROA covers it. Add a ROA for AS38104, maxLength 24.673 of 673
Route object: none59.25.66.0/24No route object for it. Add a route object with origin AS38104 in the RIR database for the space.673 of 673
ROA: none59.25.67.0/24No ROA covers it. Add a ROA for AS38104, maxLength 24.673 of 673
Route object: none59.25.67.0/24No route object for it. Add a route object with origin AS38104 in the RIR database for the space.673 of 673
ROA: none59.25.68.0/24No ROA covers it. Add a ROA for AS38104, maxLength 24.673 of 673
Route object: none59.25.68.0/24No route object for it. Add a route object with origin AS38104 in the RIR database for the space.673 of 673
ROA: none61.34.157.0/24No ROA covers it. Add a ROA for AS38104, maxLength 24.673 of 673
Route object: none61.34.157.0/24Route objects for it name AS17598. Add a route object with origin AS38104 in the RIR database for the space.673 of 673

Route objects not announced

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

58.143.244.0/22RADBNo ROA
112.214.253.0/24RADBNo ROA
118.176.80.0/20RADBNo ROA
118.176.224.0/21RADBNo ROA
118.176.232.0/22RADBNo ROA
118.176.236.0/23RADBNo ROA
118.176.240.0/20RADBNo ROA
120.142.78.0/23RADBNo ROA
120.142.88.0/21RADBNo ROA
120.142.242.0/23RADBNo ROA
120.142.246.0/23RADBNo ROA
121.88.32.0/20RADBNo ROA
121.88.168.0/21RADBNo ROA
121.88.176.0/20RADBNo ROA
124.5.0.0/18RADBNo ROA
124.5.64.0/19RADBNo 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.