bgpreport

Network · data from 2026-11-12

AS131094 HYUNDAIMOTORCO-AS-KR-KR - HYUNDAI MOTOR CO

Registry name: HYUNDAIMOTORCO-AS-KR-KR - HYUNDAI MOTOR CO, KR · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS131094, 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.162.52.128/25 Invalid: maxLength Nonecovered by 103.162.52.0/24 2 0%low visibility 2
58.225.9.0/24 No ROA Other IRR onlyRADB 672 100% 67
121.78.27.0/24 No ROA Other IRR onlyRADB 672 100% 67
183.101.125.0/24 No ROA Other IRR onlyRADB 671 100% 66
211.176.36.0/24 No ROA Other IRR onlyRADB 671 100% 66
103.162.52.0/24 Valid RIR databaseAPNIC, RADB 672 100% 67

AS-SET

AS131094 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 12 are in fix.csv.

  • ROA: maxLength1
  • ROA: none4
  • Route object: none1
  • Route object: RIR4
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: maxLength103.162.52.128/25ROA 103.162.52.0/24 AS131094 has maxLength 24; the route is a /25. Raise the maxLength, or add a ROA for 103.162.52.128/25.2 of 673
Route object: none103.162.52.128/25No route object for it. A route object for 103.162.52.0/24 with origin AS131094 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS131094 in the RIR database for the space.2 of 673
ROA: none58.225.9.0/24No ROA covers it. Add a ROA for AS131094, maxLength 24.672 of 673
Route object: RIR58.225.9.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none121.78.27.0/24No ROA covers it. Add a ROA for AS131094, maxLength 24.672 of 673
Route object: RIR121.78.27.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none183.101.125.0/24No ROA covers it. Add a ROA for AS131094, maxLength 24.671 of 673
Route object: RIR183.101.125.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none211.176.36.0/24No ROA covers it. Add a ROA for AS131094, maxLength 24.671 of 673
Route object: RIR211.176.36.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673

Route objects not announced

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

1.232.195.0/24RADBNo ROA
103.162.53.0/24APNICValid

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.