Network · data from 2026-11-12
AS38428 KICC-AS-KR-KR - Korea Information Communicaions Co.
Registry name: KICC-AS-KR-KR - Korea Information Communicaions Co., KR · not in PeeringDB
18IPv4 routes
0.0% RPKI valid · 33.3% with a route object
0IPv6 routes
0RPKI invalid
0 origin · 0 maxLength
18No ROA
12 with no route object for this origin
12Low visibility
seen by under 10% of full-table peers
0Route objects not announced
registered with origin AS38428, seen from no peer
Announced routes
Every prefix a peer of the route collectors sees with origin AS38428, 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.33.205.0/25 | No ROA | Nonecovered by 61.33.205.0/24 | 16 2%low visibility |
| 61.33.205.128/25 | No ROA | Nonecovered by 61.33.205.0/24 | 16 2%low visibility |
| 61.33.211.0/25 | No ROA | Nonecovered by 61.33.211.0/24 | 16 2%low visibility |
| 61.33.211.128/25 | No ROA | Nonecovered by 61.33.211.0/24 | 16 2%low visibility |
| 118.130.43.0/25 | No ROA | Nonecovered by 118.130.43.0/24 | 16 2%low visibility |
| 118.130.43.128/25 | No ROA | Nonecovered by 118.130.43.0/24 | 16 2%low visibility |
| 203.233.72.0/25 | No ROA | Nonecovered by 203.233.72.0/24 | 16 2%low visibility |
| 203.233.72.128/25 | No ROA | Nonecovered by 203.233.72.0/24 | 16 2%low visibility |
| 203.233.73.0/25 | No ROA | Nonecovered by 203.233.73.0/24 | 16 2%low visibility |
| 203.233.73.128/25 | No ROA | Nonecovered by 203.233.73.0/24 | 16 2%low visibility |
| 203.233.74.0/25 | No ROA | Nonecovered by 203.233.74.0/24 | 16 2%low visibility |
| 203.233.74.128/25 | No ROA | Nonecovered by 203.233.74.0/24 | 16 2%low visibility |
| 61.33.205.0/24 | No ROA | Other IRR onlyRADB | 673 100% |
| 61.33.211.0/24 | No ROA | Other IRR onlyRADB | 673 100% |
| 118.130.43.0/24 | No ROA | Other IRR onlyRADB | 673 100% |
| 203.233.72.0/24 | No ROA | Other IRR onlyRADB | 673 100% |
| 203.233.73.0/24 | No ROA | Other IRR onlyRADB | 673 100% |
| 203.233.74.0/24 | No ROA | Other IRR onlyRADB | 673 100% |
AS-SET
AS38428 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 36 are in fix.csv.
- ROA: none18
- Route object: none12
- Route object: RIR6
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 61.33.205.0/25 | No ROA covers it. Add a ROA for AS38428, maxLength 25. |
| Route object: none | 61.33.205.0/25 | No route object for it. A route object for 61.33.205.0/24 with origin AS38428 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS38428 in the RIR database for the space. |
| ROA: none | 61.33.205.128/25 | No ROA covers it. Add a ROA for AS38428, maxLength 25. |
| Route object: none | 61.33.205.128/25 | No route object for it. A route object for 61.33.205.0/24 with origin AS38428 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS38428 in the RIR database for the space. |
| ROA: none | 61.33.211.0/25 | No ROA covers it. Add a ROA for AS38428, maxLength 25. |
| Route object: none | 61.33.211.0/25 | No route object for it. A route object for 61.33.211.0/24 with origin AS38428 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS38428 in the RIR database for the space. |
| ROA: none | 61.33.211.128/25 | No ROA covers it. Add a ROA for AS38428, maxLength 25. |
| Route object: none | 61.33.211.128/25 | No route object for it. A route object for 61.33.211.0/24 with origin AS38428 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS38428 in the RIR database for the space. |
| ROA: none | 118.130.43.0/25 | No ROA covers it. Add a ROA for AS38428, maxLength 25. |
| Route object: none | 118.130.43.0/25 | No route object for it. A route object for 118.130.43.0/24 with origin AS38428 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS38428 in the RIR database for the space. |
| ROA: none | 118.130.43.128/25 | No ROA covers it. Add a ROA for AS38428, maxLength 25. |
| Route object: none | 118.130.43.128/25 | No route object for it. A route object for 118.130.43.0/24 with origin AS38428 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS38428 in the RIR database for the space. |
| ROA: none | 203.233.72.0/25 | No ROA covers it. Add a ROA for AS38428, maxLength 25. |
| Route object: none | 203.233.72.0/25 | No route object for it. A route object for 203.233.72.0/24 with origin AS38428 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS38428 in the RIR database for the space. |
| ROA: none | 203.233.72.128/25 | No ROA covers it. Add a ROA for AS38428, maxLength 25. |
| Route object: none | 203.233.72.128/25 | No route object for it. A route object for 203.233.72.0/24 with origin AS38428 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS38428 in the RIR database for the space. |
| ROA: none | 203.233.73.0/25 | No ROA covers it. Add a ROA for AS38428, maxLength 25. |
| Route object: none | 203.233.73.0/25 | No route object for it. A route object for 203.233.73.0/24 with origin AS38428 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS38428 in the RIR database for the space. |
| ROA: none | 203.233.73.128/25 | No ROA covers it. Add a ROA for AS38428, maxLength 25. |
| Route object: none | 203.233.73.128/25 | No route object for it. A route object for 203.233.73.0/24 with origin AS38428 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS38428 in the RIR database for the space. |
| ROA: none | 203.233.74.0/25 | No ROA covers it. Add a ROA for AS38428, maxLength 25. |
| Route object: none | 203.233.74.0/25 | No route object for it. A route object for 203.233.74.0/24 with origin AS38428 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS38428 in the RIR database for the space. |
| ROA: none | 203.233.74.128/25 | No ROA covers it. Add a ROA for AS38428, maxLength 25. |
| Route object: none | 203.233.74.128/25 | No route object for it. A route object for 203.233.74.0/24 with origin AS38428 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS38428 in the RIR database for the space. |
| ROA: none | 61.33.205.0/24 | No ROA covers it. Add a ROA for AS38428, maxLength 24. |
| Route object: RIR | 61.33.205.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 61.33.211.0/24 | No ROA covers it. Add a ROA for AS38428, maxLength 24. |
| Route object: RIR | 61.33.211.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 118.130.43.0/24 | No ROA covers it. Add a ROA for AS38428, maxLength 24. |
| Route object: RIR | 118.130.43.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 203.233.72.0/24 | No ROA covers it. Add a ROA for AS38428, maxLength 24. |
| Route object: RIR | 203.233.72.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 203.233.73.0/24 | No ROA covers it. Add a ROA for AS38428, maxLength 24. |
| Route object: RIR | 203.233.73.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 203.233.74.0/24 | No ROA covers it. Add a ROA for AS38428, maxLength 24. |
| Route object: RIR | 203.233.74.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Every route object with origin AS38428 is announced.
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.