Network · data from 2026-11-12
AS17838 E-HYUNDAI-AS-KR-KR - HYUNDAI HOMESHOPPING
Registry name: E-HYUNDAI-AS-KR-KR - HYUNDAI HOMESHOPPING, KR · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS17838, 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.
| 59.150.52.0/24 | No ROA | Other IRR onlyRADB | 673 100% |
| 124.137.36.0/24 | No ROA | Other IRR onlyRADB | 673 100% |
| 124.137.37.0/24 | No ROA | Other IRR onlyRADB | 673 100% |
| 211.52.154.0/24 | No ROA | Other IRR onlyRADB | 673 100% |
| 211.111.77.0/24 | No ROA | Other IRR onlyNTTCOM, RADB | 673 100% |
| 211.247.156.0/24 | No ROA | Other IRR onlyRADB | 673 100% |
| 211.247.157.0/24 | No ROA | Other IRR onlyRADB | 673 100% |
| 211.247.158.0/24 | No ROA | Other IRR onlyRADB | 673 100% |
AS-SET
AS17838 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: none8
- Route object: RIR8
- Route object: not announced5
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 59.150.52.0/24 | No ROA covers it. Add a ROA for AS17838, maxLength 24. |
| Route object: RIR | 59.150.52.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 124.137.36.0/24 | No ROA covers it. Add a ROA for AS17838, maxLength 24. |
| Route object: RIR | 124.137.36.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 124.137.37.0/24 | No ROA covers it. Add a ROA for AS17838, maxLength 24. |
| Route object: RIR | 124.137.37.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 211.52.154.0/24 | No ROA covers it. Add a ROA for AS17838, maxLength 24. |
| Route object: RIR | 211.52.154.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 211.111.77.0/24 | No ROA covers it. Add a ROA for AS17838, maxLength 24. |
| Route object: RIR | 211.111.77.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| ROA: none | 211.247.156.0/24 | No ROA covers it. Add a ROA for AS17838, maxLength 24. |
| Route object: RIR | 211.247.156.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 211.247.157.0/24 | No ROA covers it. Add a ROA for AS17838, maxLength 24. |
| Route object: RIR | 211.247.157.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 211.247.158.0/24 | No ROA covers it. Add a ROA for AS17838, maxLength 24. |
| Route object: RIR | 211.247.158.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS17838 whose prefix no peer sees AS17838 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 61.255.127.0/24 | RADB | No ROA |
| 61.255.128.0/24 | RADB | No ROA |
| 211.111.78.0/24 | NTTCOM, RADB | No ROA |
| 211.183.26.0/24 | NTTCOM, RADB | No ROA |
| 211.183.185.0/24 | NTTCOM, RADB | No 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.