Network · data from 2026-11-12
AS38388 KCOPA-AS-KR-KR - Korea Copyright Protection Agency
Registry name: KCOPA-AS-KR-KR - Korea Copyright Protection Agency, KR · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS38388, 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.
| 125.129.210.64/26 | No ROA | Nonecovered by 125.129.210.0/24 | 14 2%low visibility |
| 59.6.155.240/28 | No ROA | None | 13 2%low visibility |
| 125.129.210.0/24 | No ROA | Other IRR onlyRADB | 673 100% |
| 218.38.82.0/24 | No ROA | Other IRR onlyRADB | 673 100% |
AS-SET
AS38388 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 47 are in fix.csv.
- ROA: none4
- Route object: none2
- Route object: RIR2
- Route object: not announced39
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 125.129.210.64/26 | No ROA covers it. Add a ROA for AS38388, maxLength 26. |
| Route object: none | 125.129.210.64/26 | No route object for it. A route object for 125.129.210.0/24 with origin AS38388 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS38388 in the RIR database for the space. |
| ROA: none | 59.6.155.240/28 | No ROA covers it. Add a ROA for AS38388, maxLength 28. |
| Route object: none | 59.6.155.240/28 | No route object for it. Add a route object with origin AS38388 in the RIR database for the space. |
| ROA: none | 125.129.210.0/24 | No ROA covers it. Add a ROA for AS38388, maxLength 24. |
| Route object: RIR | 125.129.210.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 218.38.82.0/24 | No ROA covers it. Add a ROA for AS38388, maxLength 24. |
| Route object: RIR | 218.38.82.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS38388 whose prefix no peer sees AS38388 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 1.231.2.0/23 | NTTCOM, RADB | No ROA |
| 1.231.4.0/24 | NTTCOM, RADB | No ROA |
| 1.231.12.0/24 | NTTCOM, RADB | No ROA |
| 1.231.13.0/24 | NTTCOM, RADB | No ROA |
| 1.231.14.0/24 | RADB | No ROA |
| 14.38.32.0/20 | RADB | No ROA |
| 14.38.48.0/23 | RADB | No ROA |
| 58.29.2.0/24 | NTTCOM, RADB | No ROA |
| 58.29.32.0/21 | RADB | No ROA |
| 58.29.32.0/22 | RADB | No ROA |
| 58.29.36.0/23 | RADB | No ROA |
| 58.29.36.0/24 | RADB | No ROA |
| 58.29.39.0/24 | RADB | No ROA |
| 111.218.72.0/22 | RADB | No ROA |
| 111.218.76.0/23 | RADB | No ROA |
| 124.3.44.0/22 | RADB | No ROA |
| 124.3.44.0/24 | RADB | No ROA |
| 124.3.46.0/24 | NTTCOM, RADB | No ROA |
| 124.3.47.0/24 | RADB | No ROA |
| 124.3.48.0/21 | RADB | No ROA |
| 124.3.48.0/24 | RADB | No ROA |
| 124.3.49.0/24 | RADB | No ROA |
| 124.3.50.0/24 | RADB | No ROA |
| 124.3.52.0/24 | RADB | No ROA |
| 124.3.53.0/24 | RADB | No ROA |
| 124.3.54.0/24 | RADB | No ROA |
| 124.3.55.0/24 | RADB | No ROA |
| 124.3.84.0/24 | RADB | No ROA |
| 124.138.96.0/24 | RADB | No ROA |
| 124.138.97.0/24 | RADB | No ROA |
| 124.138.98.0/23 | RADB | No ROA |
| 124.138.100.0/23 | RADB | No ROA |
| 124.138.100.0/24 | RADB | No ROA |
| 124.138.101.0/24 | RADB | No ROA |
| 125.240.192.0/19 | NTTCOM | No ROA |
| 125.241.96.0/20 | NTTCOM, RADB | No ROA |
| 125.241.168.0/21 | NTTCOM, RADB | No ROA |
| 180.82.10.0/23 | NTTCOM, RADB | No ROA |
| 180.82.12.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.