Network · data from 2026-11-12
AS38123 AMCSEOUL-AS-KR-KR - asan medical center
Registry name: AMCSEOUL-AS-KR-KR - asan medical center, KR · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS38123, 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.233.2.0/24 | No ROA | Other IRR onlyRADB | 673 100% |
| 210.122.170.0/24 | No ROA | Other IRR onlyRADB | 673 100% |
| 210.122.171.0/24 | No ROA | Other IRR onlyRADB | 673 100% |
| 210.122.172.0/24 | No ROA | Other IRR onlyRADB | 673 100% |
| 210.122.173.0/24 | No ROA | Other IRR onlyRADB | 673 100% |
| 211.109.239.0/24 | No ROA | Other IRR onlyRADB | 673 100% |
| 211.245.65.0/24 | No ROA | Other IRR onlyRADB | 673 100% |
| 211.245.254.0/24 | No ROA | Other IRR onlyRADB | 673 100% |
AS-SET
AS38123 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 35 are in fix.csv.
- ROA: none8
- Route object: RIR8
- Route object: not announced19
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 1.233.2.0/24 | No ROA covers it. Add a ROA for AS38123, maxLength 24. |
| Route object: RIR | 1.233.2.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 210.122.170.0/24 | No ROA covers it. Add a ROA for AS38123, maxLength 24. |
| Route object: RIR | 210.122.170.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 210.122.171.0/24 | No ROA covers it. Add a ROA for AS38123, maxLength 24. |
| Route object: RIR | 210.122.171.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 210.122.172.0/24 | No ROA covers it. Add a ROA for AS38123, maxLength 24. |
| Route object: RIR | 210.122.172.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 210.122.173.0/24 | No ROA covers it. Add a ROA for AS38123, maxLength 24. |
| Route object: RIR | 210.122.173.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 211.109.239.0/24 | No ROA covers it. Add a ROA for AS38123, maxLength 24. |
| Route object: RIR | 211.109.239.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 211.245.65.0/24 | No ROA covers it. Add a ROA for AS38123, maxLength 24. |
| Route object: RIR | 211.245.65.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 211.245.254.0/24 | No ROA covers it. Add a ROA for AS38123, maxLength 24. |
| Route object: RIR | 211.245.254.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS38123 whose prefix no peer sees AS38123 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 61.83.233.0/24 | RADB | No ROA |
| 210.101.104.0/24 | RADB | No ROA |
| 210.101.105.0/24 | RADB | No ROA |
| 210.101.106.0/24 | RADB | No ROA |
| 210.121.228.0/24 | RADB | No ROA |
| 210.121.229.0/24 | RADB | No ROA |
| 210.121.230.0/24 | RADB | No ROA |
| 210.122.85.0/24 | RADB | No ROA |
| 210.122.174.0/24 | RADB | No ROA |
| 210.122.175.0/24 | RADB | No ROA |
| 211.245.255.0/24 | RADB | No ROA |
| 218.147.67.0/24 | RADB | No ROA |
| 218.148.63.0/24 | RADB | No ROA |
| 218.155.100.0/24 | RADB | No ROA |
| 218.155.102.0/24 | RADB | No ROA |
| 218.155.211.0/24 | RADB | No ROA |
| 220.120.228.0/24 | RADB | No ROA |
| 220.120.229.0/24 | RADB | No ROA |
| 220.127.13.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.