Network · data from 2026-11-12
AS131819 DSC-AS-KR-KR - Doosan Engineering Construction Co.,Ltd
Registry name: DSC-AS-KR-KR - Doosan Engineering Construction Co.,Ltd, KR · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS131819, 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.
| 220.120.253.0/24 | No ROA | None | 673 100% |
| 222.121.49.0/24 | No ROA | None | 673 100% |
| 211.42.177.0/29 | No ROA | Nonecovered by 211.42.177.0/24 | 10 1%low visibility |
| 211.42.177.8/29 | No ROA | Nonecovered by 211.42.177.0/24 | 10 1%low visibility |
| 211.42.177.16/29 | No ROA | Nonecovered by 211.42.177.0/24 | 10 1%low visibility |
| 211.42.177.24/29 | No ROA | Nonecovered by 211.42.177.0/24 | 10 1%low visibility |
| 106.241.74.0/24 | No ROA | Other IRR onlyRADB | 673 100% |
AS-SET
AS131819 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 15 are in fix.csv.
- ROA: none7
- Route object: none6
- Route object: RIR1
- Route object: not announced1
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 220.120.253.0/24 | No ROA covers it. Add a ROA for AS131819, maxLength 24. |
| Route object: none | 220.120.253.0/24 | No route object for it. Add a route object with origin AS131819 in the RIR database for the space. |
| ROA: none | 222.121.49.0/24 | No ROA covers it. Add a ROA for AS131819, maxLength 24. |
| Route object: none | 222.121.49.0/24 | No route object for it. Add a route object with origin AS131819 in the RIR database for the space. |
| ROA: none | 211.42.177.0/29 | No ROA covers it. Add a ROA for AS131819, maxLength 29. |
| Route object: none | 211.42.177.0/29 | No route object for it. A route object for 211.42.177.0/24 with origin AS131819 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS131819 in the RIR database for the space. |
| ROA: none | 211.42.177.8/29 | No ROA covers it. Add a ROA for AS131819, maxLength 29. |
| Route object: none | 211.42.177.8/29 | No route object for it. A route object for 211.42.177.0/24 with origin AS131819 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS131819 in the RIR database for the space. |
| ROA: none | 211.42.177.16/29 | No ROA covers it. Add a ROA for AS131819, maxLength 29. |
| Route object: none | 211.42.177.16/29 | No route object for it. A route object for 211.42.177.0/24 with origin AS131819 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS131819 in the RIR database for the space. |
| ROA: none | 211.42.177.24/29 | No ROA covers it. Add a ROA for AS131819, maxLength 29. |
| Route object: none | 211.42.177.24/29 | No route object for it. A route object for 211.42.177.0/24 with origin AS131819 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS131819 in the RIR database for the space. |
| ROA: none | 106.241.74.0/24 | No ROA covers it. Add a ROA for AS131819, maxLength 24. |
| Route object: RIR | 106.241.74.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS131819 whose prefix no peer sees AS131819 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 211.42.177.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.