Network · data from 2026-11-12
AS38116 SEOICHEON-AS-KR-KR - KCTC
Registry name: SEOICHEON-AS-KR-KR - KCTC, KR · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS38116, 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.
| 121.157.6.0/25 | No ROA | None | 16 2%low visibility |
| 211.181.85.0/27 | No ROA | Nonecovered by 211.181.85.0/25 | 14 2%low visibility |
AS-SET
AS38116 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 29 are in fix.csv.
- ROA: none2
- Route object: none2
- Route object: not announced25
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 121.157.6.0/25 | No ROA covers it. Add a ROA for AS38116, maxLength 25. |
| Route object: none | 121.157.6.0/25 | No route object for it. Add a route object with origin AS38116 in the RIR database for the space. |
| ROA: none | 211.181.85.0/27 | No ROA covers it. Add a ROA for AS38116, maxLength 27. |
| Route object: none | 211.181.85.0/27 | No route object for it. A route object for 211.181.85.0/25 with origin AS38116 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS38116 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS38116 whose prefix no peer sees AS38116 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 58.103.80.0/24 | NTTCOM | No ROA |
| 58.103.81.0/24 | NTTCOM | No ROA |
| 58.103.82.0/24 | NTTCOM | No ROA |
| 58.103.83.0/24 | NTTCOM | No ROA |
| 58.103.84.0/24 | NTTCOM | No ROA |
| 58.103.85.0/24 | NTTCOM | No ROA |
| 58.103.86.0/24 | NTTCOM | No ROA |
| 58.103.87.0/24 | NTTCOM | No ROA |
| 58.103.88.0/24 | NTTCOM | No ROA |
| 58.103.89.0/24 | NTTCOM | No ROA |
| 58.103.90.0/24 | NTTCOM | No ROA |
| 58.103.91.0/24 | NTTCOM | No ROA |
| 58.103.95.0/24 | NTTCOM | No ROA |
| 124.136.229.0/24 | NTTCOM | No ROA |
| 125.57.114.0/24 | NTTCOM | No ROA |
| 125.57.115.0/24 | NTTCOM | No ROA |
| 125.57.116.0/24 | NTTCOM | No ROA |
| 125.57.117.0/24 | NTTCOM | No ROA |
| 125.57.170.0/23 | RADB | No ROA |
| 125.57.172.0/22 | RADB | No ROA |
| 125.57.176.0/22 | RADB | No ROA |
| 125.57.186.0/23 | RADB | No ROA |
| 125.57.188.0/23 | RADB | No ROA |
| 125.57.190.0/24 | RADB | No ROA |
| 211.181.85.0/25 | 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.