Network · data from 2026-11-12
AS9857 KOGAS-AS-KR-KR - KOREA GAS CORPORATION
Registry name: KOGAS-AS-KR-KR - KOREA GAS CORPORATION, KR · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS9857, 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.
| 61.36.228.0/24 | No ROA | Other IRR onlyRADB | 673 100% |
| 210.124.38.0/24 | No ROA | Other IRR onlyRADB | 673 100% |
| 210.124.209.0/24 | No ROA | Other IRR onlyRADB | 673 100% |
| 210.124.210.0/24 | No ROA | Other IRR onlyRADB | 673 100% |
| 210.124.211.0/24 | No ROA | Other IRR onlyRADB | 673 100% |
| 211.253.204.0/24 | No ROA | Other IRR onlyRADB | 673 100% |
| 211.253.205.0/24 | No ROA | Other IRR onlyRADB | 673 100% |
| 211.253.206.0/24 | No ROA | Other IRR onlyRADB | 673 100% |
| 211.253.207.0/24 | No ROA | Other IRR onlyRADB | 673 100% |
AS-SET
AS9857 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 23 are in fix.csv.
- ROA: none9
- Route object: RIR9
- Route object: not announced5
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 61.36.228.0/24 | No ROA covers it. Add a ROA for AS9857, maxLength 24. |
| Route object: RIR | 61.36.228.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 210.124.38.0/24 | No ROA covers it. Add a ROA for AS9857, maxLength 24. |
| Route object: RIR | 210.124.38.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 210.124.209.0/24 | No ROA covers it. Add a ROA for AS9857, maxLength 24. |
| Route object: RIR | 210.124.209.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 210.124.210.0/24 | No ROA covers it. Add a ROA for AS9857, maxLength 24. |
| Route object: RIR | 210.124.210.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 210.124.211.0/24 | No ROA covers it. Add a ROA for AS9857, maxLength 24. |
| Route object: RIR | 210.124.211.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 211.253.204.0/24 | No ROA covers it. Add a ROA for AS9857, maxLength 24. |
| Route object: RIR | 211.253.204.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 211.253.205.0/24 | No ROA covers it. Add a ROA for AS9857, maxLength 24. |
| Route object: RIR | 211.253.205.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 211.253.206.0/24 | No ROA covers it. Add a ROA for AS9857, maxLength 24. |
| Route object: RIR | 211.253.206.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 211.253.207.0/24 | No ROA covers it. Add a ROA for AS9857, maxLength 24. |
| Route object: RIR | 211.253.207.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS9857 whose prefix no peer sees AS9857 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 61.36.228.0/23 | RADB | No ROA |
| 61.36.229.0/24 | RADB | No ROA |
| 210.124.210.0/23 | RADB | No ROA |
| 211.36.0.0/22 | RADB | No ROA |
| 211.172.240.0/20 | 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.