Network · data from 2026-11-12
AS18339 DAEWONJINCHEON-AS-KR-KR - daewonpharm
Registry name: DAEWONJINCHEON-AS-KR-KR - daewonpharm, KR · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS18339, 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.
| 1.248.19.128/26 | No ROA | Nonecovered by 1.248.19.0/24 | 14 2%low visibility |
| 210.222.236.0/26 | No ROA | None | 14 2%low visibility |
AS-SET
AS18339 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 6 are in fix.csv.
- ROA: none2
- Route object: none2
- Route object: not announced2
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 1.248.19.128/26 | No ROA covers it. Add a ROA for AS18339, maxLength 26. |
| Route object: none | 1.248.19.128/26 | No route object for it. A route object for 1.248.19.0/24 with origin AS18339 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS18339 in the RIR database for the space. |
| ROA: none | 210.222.236.0/26 | No ROA covers it. Add a ROA for AS18339, maxLength 26. |
| Route object: none | 210.222.236.0/26 | No route object for it. Add a route object with origin AS18339 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS18339 whose prefix no peer sees AS18339 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 1.248.19.0/24 | RADB | No ROA |
| 220.66.108.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.