bgpreport

Network · data from 2026-11-12

AS10056 HDMF-AS-KR - Hyundai Marin Fire Insurance

Registry name: HDMF-AS-KR - Hyundai Marin Fire Insurance, KR · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS10056, 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.175.24.128/25 No ROA None 15 2%low visibility 13
211.249.86.112/28 No ROA None 12 2%low visibility 12
61.96.143.0/24 No ROA Other IRR onlyNTTCOM 672 100% 67
115.21.8.0/24 No ROA Other IRR onlyRADB 672 100% 67
211.192.0.0/24 No ROA Other IRR onlyNTTCOM, RADB 672 100% 67
220.64.15.0/24 No ROA Other IRR onlyNTTCOM, RADB 672 100% 67
220.64.74.0/24 No ROA Other IRR onlyRADB 672 100% 67

AS-SET

AS10056 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 14 are in fix.csv.

  • ROA: none7
  • Route object: none2
  • Route object: RIR5
ChangePrefix or setDetailFull-table peers
ROA: none211.175.24.128/25No ROA covers it. Add a ROA for AS10056, maxLength 25.15 of 673
Route object: none211.175.24.128/25No route object for it. Add a route object with origin AS10056 in the RIR database for the space.15 of 673
ROA: none211.249.86.112/28No ROA covers it. Add a ROA for AS10056, maxLength 28.12 of 673
Route object: none211.249.86.112/28No route object for it. Add a route object with origin AS10056 in the RIR database for the space.12 of 673
ROA: none61.96.143.0/24No ROA covers it. Add a ROA for AS10056, maxLength 24.672 of 673
Route object: RIR61.96.143.0/24Route object only in NTTCOM. Add it in the RIR database for the space.672 of 673
ROA: none115.21.8.0/24No ROA covers it. Add a ROA for AS10056, maxLength 24.672 of 673
Route object: RIR115.21.8.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none211.192.0.0/24No ROA covers it. Add a ROA for AS10056, maxLength 24.672 of 673
Route object: RIR211.192.0.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.672 of 673
ROA: none220.64.15.0/24No ROA covers it. Add a ROA for AS10056, maxLength 24.672 of 673
Route object: RIR220.64.15.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.672 of 673
ROA: none220.64.74.0/24No ROA covers it. Add a ROA for AS10056, maxLength 24.672 of 673
Route object: RIR220.64.74.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673

Route objects not announced

Every route object with origin AS10056 is announced.

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.