Network · data from 2026-11-12
AS38128 GICO-AS-KR-KR - Gyeonggi Hosing Urban Development Corporation
Registry name: GICO-AS-KR-KR - Gyeonggi Hosing Urban Development Corporation, KR · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS38128, 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.
| 211.118.124.0/25 | No ROA | None | 16 2%low visibility |
| 211.118.124.128/26 | No ROA | None | 14 2%low visibility |
| 211.118.124.192/26 | No ROA | None | 14 2%low visibility |
AS-SET
AS38128 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 7 are in fix.csv.
- ROA: none3
- Route object: none3
- Route object: not announced1
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 211.118.124.0/25 | No ROA covers it. Add a ROA for AS38128, maxLength 25. |
| Route object: none | 211.118.124.0/25 | No route object for it. Add a route object with origin AS38128 in the RIR database for the space. |
| ROA: none | 211.118.124.128/26 | No ROA covers it. Add a ROA for AS38128, maxLength 26. |
| Route object: none | 211.118.124.128/26 | No route object for it. Add a route object with origin AS38128 in the RIR database for the space. |
| ROA: none | 211.118.124.192/26 | No ROA covers it. Add a ROA for AS38128, maxLength 26. |
| Route object: none | 211.118.124.192/26 | No route object for it. Add a route object with origin AS38128 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS38128 whose prefix no peer sees AS38128 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 122.0.8.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.