Network · data from 2026-11-12
AS24026 KFE-AS-KR-KR - KOREA INSTITUTE OF FUSION ENERGY
Registry name: KFE-AS-KR-KR - KOREA INSTITUTE OF FUSION ENERGY, KR · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS24026, 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.
| 203.230.118.0/24 | No ROA | Other IRR onlyRADB | 673 100% |
| 203.230.119.0/24 | No ROA | Other IRR onlyRADB | 673 100% |
| 203.230.124.0/24 | No ROA | Other IRR onlyRADB | 673 100% |
| 203.230.125.0/24 | No ROA | Other IRR onlyRADB | 673 100% |
| 203.230.127.0/24 | No ROA | Other IRR onlyRADB | 673 100% |
| 210.107.148.0/24 | No ROA | Other IRR onlyRADB | 673 100% |
| 210.107.149.0/24 | No ROA | Other IRR onlyRADB | 673 100% |
| 210.107.150.0/24 | No ROA | Other IRR onlyRADB | 673 100% |
| 210.107.151.0/24 | No ROA | Other IRR onlyRADB | 673 100% |
AS-SET
AS24026 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 25 are in fix.csv.
- ROA: none9
- Route object: RIR9
- Route object: not announced7
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 203.230.118.0/24 | No ROA covers it. Add a ROA for AS24026, maxLength 24. |
| Route object: RIR | 203.230.118.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 203.230.119.0/24 | No ROA covers it. Add a ROA for AS24026, maxLength 24. |
| Route object: RIR | 203.230.119.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 203.230.124.0/24 | No ROA covers it. Add a ROA for AS24026, maxLength 24. |
| Route object: RIR | 203.230.124.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 203.230.125.0/24 | No ROA covers it. Add a ROA for AS24026, maxLength 24. |
| Route object: RIR | 203.230.125.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 203.230.127.0/24 | No ROA covers it. Add a ROA for AS24026, maxLength 24. |
| Route object: RIR | 203.230.127.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 210.107.148.0/24 | No ROA covers it. Add a ROA for AS24026, maxLength 24. |
| Route object: RIR | 210.107.148.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 210.107.149.0/24 | No ROA covers it. Add a ROA for AS24026, maxLength 24. |
| Route object: RIR | 210.107.149.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 210.107.150.0/24 | No ROA covers it. Add a ROA for AS24026, maxLength 24. |
| Route object: RIR | 210.107.150.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 210.107.151.0/24 | No ROA covers it. Add a ROA for AS24026, maxLength 24. |
| Route object: RIR | 210.107.151.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS24026 whose prefix no peer sees AS24026 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 203.232.108.0/24 | RADB | No ROA |
| 210.211.1.0/24 | RADB | No ROA |
| 210.216.41.0/24 | RADB | No ROA |
| 210.216.42.0/23 | RADB | No ROA |
| 218.149.15.0/24 | RADB | No ROA |
| 218.149.16.0/23 | RADB | No ROA |
| 220.66.6.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.