Network · data from 2026-11-12
AS10165 CUSTOMS-AS-KR-KR - KOREA CUSTOMS SERVICE
Registry name: CUSTOMS-AS-KR-KR - KOREA CUSTOMS SERVICE, KR · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS10165, 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.
| 58.184.124.32/27 | No ROA | None | 13 2%low visibility |
| 210.90.17.128/26 | No ROA | None | 13 2%low visibility |
| 211.173.40.0/24 | No ROA | Other IRR onlyRADB | 672 100% |
| 211.173.41.0/24 | No ROA | Other IRR onlyRADB | 672 100% |
| 211.173.42.0/24 | No ROA | Other IRR onlyRADB | 672 100% |
| 211.173.43.0/24 | No ROA | Other IRR onlyRADB | 672 100% |
| 211.173.44.0/24 | No ROA | Other IRR onlyRADB | 672 100% |
| 211.173.45.0/24 | No ROA | Other IRR onlyRADB | 672 100% |
AS-SET
AS10165 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 19 are in fix.csv.
- ROA: none8
- Route object: none2
- Route object: RIR6
- Route object: not announced3
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 58.184.124.32/27 | No ROA covers it. Add a ROA for AS10165, maxLength 27. |
| Route object: none | 58.184.124.32/27 | No route object for it. Add a route object with origin AS10165 in the RIR database for the space. |
| ROA: none | 210.90.17.128/26 | No ROA covers it. Add a ROA for AS10165, maxLength 26. |
| Route object: none | 210.90.17.128/26 | No route object for it. Add a route object with origin AS10165 in the RIR database for the space. |
| ROA: none | 211.173.40.0/24 | No ROA covers it. Add a ROA for AS10165, maxLength 24. |
| Route object: RIR | 211.173.40.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 211.173.41.0/24 | No ROA covers it. Add a ROA for AS10165, maxLength 24. |
| Route object: RIR | 211.173.41.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 211.173.42.0/24 | No ROA covers it. Add a ROA for AS10165, maxLength 24. |
| Route object: RIR | 211.173.42.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 211.173.43.0/24 | No ROA covers it. Add a ROA for AS10165, maxLength 24. |
| Route object: RIR | 211.173.43.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 211.173.44.0/24 | No ROA covers it. Add a ROA for AS10165, maxLength 24. |
| Route object: RIR | 211.173.44.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 211.173.45.0/24 | No ROA covers it. Add a ROA for AS10165, maxLength 24. |
| Route object: RIR | 211.173.45.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS10165 whose prefix no peer sees AS10165 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 202.30.224.0/23 | RADB | No ROA |
| 203.30.226.0/24 | RADB | No ROA |
| 210.118.176.0/23 | 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.