Network · data from 2026-11-12
AS38101 YULCHON-AS-KR-KR - Yulchon LLC
Registry name: YULCHON-AS-KR-KR - Yulchon LLC, KR · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS38101, 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.96.207.0/24 | No ROA | None | 673 100% |
| 118.128.51.0/24 | No ROA | None | 673 100% |
| 121.53.255.0/24 | No ROA | None | 673 100% |
| 211.61.146.0/24 | No ROA | None | 673 100% |
| 211.183.91.0/24 | No ROA | None | 673 100% |
| 211.183.93.0/24 | No ROA | None | 673 100% |
| 211.60.79.0/24 | No ROA | None | 56 8%low visibility |
AS-SET
AS38101 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 20 are in fix.csv.
- ROA: none7
- Route object: none7
- Route object: not announced6
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 61.96.207.0/24 | No ROA covers it. Add a ROA for AS38101, maxLength 24. |
| Route object: none | 61.96.207.0/24 | No route object for it. Add a route object with origin AS38101 in the RIR database for the space. |
| ROA: none | 118.128.51.0/24 | No ROA covers it. Add a ROA for AS38101, maxLength 24. |
| Route object: none | 118.128.51.0/24 | No route object for it. Add a route object with origin AS38101 in the RIR database for the space. |
| ROA: none | 121.53.255.0/24 | No ROA covers it. Add a ROA for AS38101, maxLength 24. |
| Route object: none | 121.53.255.0/24 | No route object for it. Add a route object with origin AS38101 in the RIR database for the space. |
| ROA: none | 211.61.146.0/24 | No ROA covers it. Add a ROA for AS38101, maxLength 24. |
| Route object: none | 211.61.146.0/24 | No route object for it. Add a route object with origin AS38101 in the RIR database for the space. |
| ROA: none | 211.183.91.0/24 | No ROA covers it. Add a ROA for AS38101, maxLength 24. |
| Route object: none | 211.183.91.0/24 | No route object for it. Add a route object with origin AS38101 in the RIR database for the space. |
| ROA: none | 211.183.93.0/24 | No ROA covers it. Add a ROA for AS38101, maxLength 24. |
| Route object: none | 211.183.93.0/24 | No route object for it. Add a route object with origin AS38101 in the RIR database for the space. |
| ROA: none | 211.60.79.0/24 | No ROA covers it. Add a ROA for AS38101, maxLength 24. |
| Route object: none | 211.60.79.0/24 | No route object for it. Add a route object with origin AS38101 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS38101 whose prefix no peer sees AS38101 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 61.34.251.0/24 | RADB | No ROA |
| 61.100.88.0/23 | RADB | No ROA |
| 61.100.88.0/24 | RADB | No ROA |
| 61.100.89.0/24 | RADB | No ROA |
| 118.128.233.0/24 | RADB | No ROA |
| 123.140.242.0/24 | 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.