bgpreport

Network · data from 2026-11-12

AS17607 AS5665-AS-KR-KR - Mirae Asset Life Insurance Co., Ltd

Registry name: AS5665-AS-KR-KR - Mirae Asset Life Insurance Co., Ltd, KR · not in PeeringDB

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

Announced routes

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

103.166.223.0/25 No ROA Nonecovered by 103.166.223.0/24 0 0%low visibility 1
103.166.222.0/24 No ROA Other IRR onlyRADB 673 100% 67
103.166.223.0/24 No ROA Other IRR onlyRADB 673 100% 67
168.154.181.0/24 No ROA Other IRR onlyRADB 673 100% 67
168.154.226.0/24 No ROA Other IRR onlyRADB 673 100% 67
168.154.228.0/24 No ROA Other IRR onlyRADB 673 100% 67
210.211.82.0/24 No ROA Other IRR onlyRADB 673 100% 67
210.211.83.0/24 No ROA Other IRR onlyRADB 673 100% 67
210.211.84.0/24 No ROA Other IRR onlyRADB 673 100% 67

AS-SET

AS17607 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 21 are in fix.csv.

  • ROA: none9
  • Route object: none1
  • Route object: RIR8
  • Route object: not announced3
ChangePrefix or setDetailFull-table peers
ROA: none103.166.223.0/25No ROA covers it. Add a ROA for AS17607, maxLength 25.0 of 673
Route object: none103.166.223.0/25No route object for it. A route object for 103.166.223.0/24 with origin AS17607 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS17607 in the RIR database for the space.0 of 673
ROA: none103.166.222.0/24No ROA covers it. Add a ROA for AS17607, maxLength 24.673 of 673
Route object: RIR103.166.222.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none103.166.223.0/24No ROA covers it. Add a ROA for AS17607, maxLength 24.673 of 673
Route object: RIR103.166.223.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none168.154.181.0/24No ROA covers it. Add a ROA for AS17607, maxLength 24.673 of 673
Route object: RIR168.154.181.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none168.154.226.0/24No ROA covers it. Add a ROA for AS17607, maxLength 24.673 of 673
Route object: RIR168.154.226.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none168.154.228.0/24No ROA covers it. Add a ROA for AS17607, maxLength 24.673 of 673
Route object: RIR168.154.228.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none210.211.82.0/24No ROA covers it. Add a ROA for AS17607, maxLength 24.673 of 673
Route object: RIR210.211.82.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none210.211.83.0/24No ROA covers it. Add a ROA for AS17607, maxLength 24.673 of 673
Route object: RIR210.211.83.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none210.211.84.0/24No ROA covers it. Add a ROA for AS17607, maxLength 24.673 of 673
Route object: RIR210.211.84.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 AS17607 whose prefix no peer sees AS17607 announce. Many are kept on purpose (backup routes, space announced only in some places).

61.36.230.0/24RADBNo ROA
61.41.18.0/24RADBNo ROA
61.41.19.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.