Network · data from 2026-11-12
AS38418 APPLYHOME-AS-KR-KR - KOREA APPRAISAL BOARD
Registry name: APPLYHOME-AS-KR-KR - KOREA APPRAISAL BOARD, KR · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS38418, 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.43.243.0/24 | No ROA | None | 671 100% |
AS-SET
AS38418 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: none1
- Route object: none1
- Route object: not announced21
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 61.43.243.0/24 | No ROA covers it. Add a ROA for AS38418, maxLength 24. |
| Route object: none | 61.43.243.0/24 | No route object for it. Add a route object with origin AS38418 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS38418 whose prefix no peer sees AS38418 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 1.231.8.0/24 | RADB | No ROA |
| 1.231.9.0/24 | RADB | No ROA |
| 58.29.3.0/24 | RADB | No ROA |
| 58.29.40.0/21 | RADB | No ROA |
| 58.29.40.0/22 | RADB | No ROA |
| 58.29.40.0/23 | RADB | No ROA |
| 58.29.42.0/24 | RADB | No ROA |
| 58.29.87.0/24 | RADB | No ROA |
| 111.218.78.0/23 | RADB | No ROA |
| 111.218.80.0/23 | RADB | No ROA |
| 124.3.76.0/24 | RADB | No ROA |
| 124.3.77.0/24 | RADB | No ROA |
| 124.138.102.0/23 | RADB | No ROA |
| 124.138.104.0/22 | RADB | No ROA |
| 124.138.108.0/22 | RADB | No ROA |
| 125.241.0.0/20 | RADB | No ROA |
| 125.241.16.0/22 | RADB | No ROA |
| 125.241.20.0/24 | RADB | No ROA |
| 125.241.22.0/23 | RADB | No ROA |
| 125.241.24.0/21 | RADB | No ROA |
| 221.106.129.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.