Network · data from 2026-11-12
AS38088 EWP-AS-KR-KR - KOREA EAST-WEST POWER
Registry name: EWP-AS-KR-KR - KOREA EAST-WEST POWER, KR · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS38088, 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.
| 221.161.70.0/29 | No ROA | Nonecovered by 221.161.70.0/27 | 10 1%low visibility |
| 221.161.70.8/29 | No ROA | Nonecovered by 221.161.70.0/27 | 10 1%low visibility |
| 221.161.70.16/29 | No ROA | Nonecovered by 221.161.70.0/27 | 10 1%low visibility |
| 58.125.98.0/24 | No ROA | Other IRR onlyRADB | 672 100% |
| 58.235.227.0/24 | No ROA | Other IRR onlyRADB | 672 100% |
| 58.235.239.0/24 | No ROA | Other IRR onlyRADB | 672 100% |
AS-SET
AS38088 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 24 are in fix.csv.
- ROA: none6
- Route object: none3
- Route object: RIR3
- Route object: not announced12
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 221.161.70.0/29 | No ROA covers it. Add a ROA for AS38088, maxLength 29. |
| Route object: none | 221.161.70.0/29 | No route object for it. A route object for 221.161.70.0/27 with origin AS38088 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS38088 in the RIR database for the space. |
| ROA: none | 221.161.70.8/29 | No ROA covers it. Add a ROA for AS38088, maxLength 29. |
| Route object: none | 221.161.70.8/29 | No route object for it. A route object for 221.161.70.0/27 with origin AS38088 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS38088 in the RIR database for the space. |
| ROA: none | 221.161.70.16/29 | No ROA covers it. Add a ROA for AS38088, maxLength 29. |
| Route object: none | 221.161.70.16/29 | No route object for it. A route object for 221.161.70.0/27 with origin AS38088 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS38088 in the RIR database for the space. |
| ROA: none | 58.125.98.0/24 | No ROA covers it. Add a ROA for AS38088, maxLength 24. |
| Route object: RIR | 58.125.98.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 58.235.227.0/24 | No ROA covers it. Add a ROA for AS38088, maxLength 24. |
| Route object: RIR | 58.235.227.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 58.235.239.0/24 | No ROA covers it. Add a ROA for AS38088, maxLength 24. |
| Route object: RIR | 58.235.239.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS38088 whose prefix no peer sees AS38088 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 58.76.208.0/21 | RADB | No ROA |
| 58.102.208.0/23 | NTTCOM | No ROA |
| 61.37.122.0/24 | RADB | No ROA |
| 61.42.188.0/23 | RADB | No ROA |
| 124.3.236.0/22 | NTTCOM | No ROA |
| 124.136.104.0/22 | NTTCOM | No ROA |
| 211.169.61.0/24 | RADB | No ROA |
| 211.169.68.0/24 | RADB | No ROA |
| 211.181.123.0/24 | RADB | No ROA |
| 211.215.130.0/24 | RADB | No ROA |
| 219.249.162.0/24 | RADB | No ROA |
| 221.161.70.0/27 | 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.