bgpreport

Network · data from 2026-11-12

AS38660 KHNP-AS-KR-KR - KHNP

Registry name: KHNP-AS-KR-KR - KHNP, KR · not in PeeringDB

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

Announced routes

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

61.248.189.0/24 No ROA Other IRR onlyRADB 673 100% 66
61.248.190.0/24 No ROA Other IRR onlyRADB 673 100% 66
61.249.249.0/24 No ROA Other IRR onlyRADB 673 100% 66
103.21.189.0/24 No ROA Other IRR onlyRADB 673 100% 66
211.190.230.0/24 No ROA Other IRR onlyRADB 673 100% 66

AS-SET

AS38660 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 43 are in fix.csv.

  • ROA: none5
  • Route object: RIR5
  • Route object: not announced33
ChangePrefix or setDetailFull-table peers
ROA: none61.248.189.0/24No ROA covers it. Add a ROA for AS38660, maxLength 24.673 of 673
Route object: RIR61.248.189.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none61.248.190.0/24No ROA covers it. Add a ROA for AS38660, maxLength 24.673 of 673
Route object: RIR61.248.190.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none61.249.249.0/24No ROA covers it. Add a ROA for AS38660, maxLength 24.673 of 673
Route object: RIR61.249.249.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none103.21.189.0/24No ROA covers it. Add a ROA for AS38660, maxLength 24.673 of 673
Route object: RIR103.21.189.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none211.190.230.0/24No ROA covers it. Add a ROA for AS38660, maxLength 24.673 of 673
Route object: RIR211.190.230.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 AS38660 whose prefix no peer sees AS38660 announce. Many are kept on purpose (backup routes, space announced only in some places).

61.43.162.0/23RADBNo ROA
103.21.188.0/24RADBNo ROA
113.52.192.0/19RADBNo ROA
113.52.192.0/20RADBNo ROA
113.52.192.0/21RADBNo ROA
113.52.200.0/21RADBNo ROA
113.52.208.0/21RADBNo ROA
113.52.216.0/21RADBNo ROA
114.30.48.0/20RADBNo ROA
114.30.48.0/21RADBNo ROA
114.30.56.0/21RADBNo ROA
114.30.56.0/24RADBNo ROA
115.69.96.0/19NTTCOM, RADBNo ROA
115.69.96.0/20RADBNo ROA
115.69.96.0/22NTTCOMNo ROA
115.69.100.0/22NTTCOMNo ROA
115.69.112.0/20RADBNo ROA
175.118.205.0/24RADBNo ROA
180.189.64.0/18RADBNo ROA
180.189.64.0/19RADBNo ROA
180.189.64.0/21RADBNo ROA
180.189.72.0/21RADBNo ROA
180.189.80.0/21RADBNo ROA
180.189.88.0/21RADBNo ROA
180.189.96.0/19RADBNo ROA
180.189.96.0/21RADBNo ROA
180.189.104.0/21RADBNo ROA
180.189.112.0/21RADBNo ROA
180.189.120.0/21RADBNo ROA
183.86.201.0/24RADBNo ROA
210.114.252.144/28RADBNo ROA
211.190.229.0/24RADBNo ROA
211.190.231.0/24RADBNo 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.