Network · data from 2026-11-12
AS10063 KMA-AS-KR - Korea Meteorological Administration
Registry name: KMA-AS-KR - Korea Meteorological Administration, KR · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS10063, 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.247.79.0/24 | No ROA | Nonecovered by 203.247.64.0/18 | 672 100% |
| 203.247.90.0/24 | No ROA | Nonecovered by 203.247.64.0/18 | 672 100% |
| 203.247.92.0/24 | No ROA | Nonecovered by 203.247.64.0/18 | 672 100% |
| 203.247.110.0/29 | No ROA | Nonecovered by 203.247.64.0/18 | 9 1%low visibility |
| 203.247.66.0/24 | No ROA | Other IRR onlyNTTCOM, RADB | 672 100% |
| 203.247.75.0/24 | No ROA | Other IRR onlyNTTCOM | 672 100% |
| 203.247.77.0/24 | No ROA | Other IRR onlyNTTCOM, RADB | 672 100% |
| 203.247.80.0/24 | No ROA | Other IRR onlyNTTCOM, RADB | 672 100% |
| 203.247.91.0/24 | No ROA | Other IRR onlyRADB | 672 100% |
| 203.247.101.0/24 | No ROA | Other IRR onlyNTTCOM, RADB | 672 100% |
| 210.107.255.0/24 | No ROA | Other IRR onlyRADB | 672 100% |
AS-SET
AS10063 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: none11
- Route object: none4
- Route object: RIR7
- Route object: not announced1
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 203.247.79.0/24 | No ROA covers it. Add a ROA for AS10063, maxLength 24. |
| Route object: none | 203.247.79.0/24 | No route object for it. A route object for 203.247.64.0/18 with origin AS10063 covers it (filters allowing more-specifics accept it). Add a route object with origin AS10063 in the RIR database for the space. |
| ROA: none | 203.247.90.0/24 | No ROA covers it. Add a ROA for AS10063, maxLength 24. |
| Route object: none | 203.247.90.0/24 | No route object for it. A route object for 203.247.64.0/18 with origin AS10063 covers it (filters allowing more-specifics accept it). Add a route object with origin AS10063 in the RIR database for the space. |
| ROA: none | 203.247.92.0/24 | No ROA covers it. Add a ROA for AS10063, maxLength 24. |
| Route object: none | 203.247.92.0/24 | No route object for it. A route object for 203.247.64.0/18 with origin AS10063 covers it (filters allowing more-specifics accept it). Add a route object with origin AS10063 in the RIR database for the space. |
| ROA: none | 203.247.110.0/29 | No ROA covers it. Add a ROA for AS10063, maxLength 29. |
| Route object: none | 203.247.110.0/29 | No route object for it. A route object for 203.247.64.0/18 with origin AS10063 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS10063 in the RIR database for the space. |
| ROA: none | 203.247.66.0/24 | No ROA covers it. Add a ROA for AS10063, maxLength 24. |
| Route object: RIR | 203.247.66.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| ROA: none | 203.247.75.0/24 | No ROA covers it. Add a ROA for AS10063, maxLength 24. |
| Route object: RIR | 203.247.75.0/24 | Route object only in NTTCOM. Add it in the RIR database for the space. |
| ROA: none | 203.247.77.0/24 | No ROA covers it. Add a ROA for AS10063, maxLength 24. |
| Route object: RIR | 203.247.77.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| ROA: none | 203.247.80.0/24 | No ROA covers it. Add a ROA for AS10063, maxLength 24. |
| Route object: RIR | 203.247.80.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| ROA: none | 203.247.91.0/24 | No ROA covers it. Add a ROA for AS10063, maxLength 24. |
| Route object: RIR | 203.247.91.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 203.247.101.0/24 | No ROA covers it. Add a ROA for AS10063, maxLength 24. |
| Route object: RIR | 203.247.101.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| ROA: none | 210.107.255.0/24 | No ROA covers it. Add a ROA for AS10063, maxLength 24. |
| Route object: RIR | 210.107.255.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS10063 whose prefix no peer sees AS10063 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 203.247.64.0/18 | 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.