Network · data from 2026-11-12
AS38106 Korea Security Technology Co., Ltd.
Registry name: SECUREIDC-AS-KR-KR - Korea Security Technology Co., Ltd., KR · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS38106, 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.
| 45.117.12.0/24 | No ROA | Other IRR onlyRADB | 672 100% |
| 45.117.13.0/24 | No ROA | Other IRR onlyRADB | 672 100% |
| 103.144.30.0/24 | No ROA | RIR databaseAPNIC, RADB | 673 100% |
| 103.144.31.0/24 | No ROA | RIR databaseAPNIC, RADB | 673 100% |
AS-SET
AS38106's PeeringDB record names no 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 13 are in fix.csv.
- ROA: none4
- Route object: RIR2
- Route object: not announced7
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 45.117.12.0/24 | No ROA covers it. Add a ROA for AS38106, maxLength 24. |
| Route object: RIR | 45.117.12.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 45.117.13.0/24 | No ROA covers it. Add a ROA for AS38106, maxLength 24. |
| Route object: RIR | 45.117.13.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 103.144.30.0/24 | No ROA covers it. Add a ROA for AS38106, maxLength 24. |
| ROA: none | 103.144.31.0/24 | No ROA covers it. Add a ROA for AS38106, maxLength 24. |
Route objects not announced
Route objects with origin AS38106 whose prefix no peer sees AS38106 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 103.7.236.0/24 | RADB | No ROA |
| 103.57.62.0/24 | RADB | No ROA |
| 103.57.63.0/24 | RADB | No ROA |
| 111.92.247.0/24 | RADB | No ROA |
| 203.238.48.0/21 | RADB | No ROA |
| 203.248.8.0/22 | RADB | No ROA |
| 210.116.248.0/21 | 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.