bgpreport

Network · data from 2026-11-12

AS17582 KIC-AS-KR-KR - Korea Investment Corporation

Registry name: KIC-AS-KR-KR - Korea Investment Corporation, KR · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS17582, 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.108.163.0/24 No ROA Other IRR onlyRADB 673 100% 67
220.65.225.0/24 No ROA Other IRR onlyNTTCOM, RADB 673 100% 67
210.220.28.32/27 No ROA Other IRR onlyRADB 14 2%low visibility 13
112.77.9.0/28 No ROA Other IRR onlyRADB 13 2%low visibility 13
112.77.9.16/28 No ROA Other IRR onlyRADB 13 2%low visibility 13
112.77.9.32/28 No ROA Other IRR onlyRADB 13 2%low visibility 13

AS-SET

AS17582 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 13 are in fix.csv.

  • ROA: none6
  • Route object: RIR6
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: none61.108.163.0/24No ROA covers it. Add a ROA for AS17582, maxLength 24.673 of 673
Route object: RIR61.108.163.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none220.65.225.0/24No ROA covers it. Add a ROA for AS17582, maxLength 24.673 of 673
Route object: RIR220.65.225.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.673 of 673
ROA: none210.220.28.32/27No ROA covers it. Add a ROA for AS17582, maxLength 27.14 of 673
Route object: RIR210.220.28.32/27Route object only in RADB. Add it in the RIR database for the space.14 of 673
ROA: none112.77.9.0/28No ROA covers it. Add a ROA for AS17582, maxLength 28.13 of 673
Route object: RIR112.77.9.0/28Route object only in RADB. Add it in the RIR database for the space.13 of 673
ROA: none112.77.9.16/28No ROA covers it. Add a ROA for AS17582, maxLength 28.13 of 673
Route object: RIR112.77.9.16/28Route object only in RADB. Add it in the RIR database for the space.13 of 673
ROA: none112.77.9.32/28No ROA covers it. Add a ROA for AS17582, maxLength 28.13 of 673
Route object: RIR112.77.9.32/28Route object only in RADB. Add it in the RIR database for the space.13 of 673

Route objects not announced

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

112.77.9.128/28RADBNo 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.