Network · data from 2026-11-12
AS38406 GOEHS-AS-KR-KR - Kyeonggi-Do Hwaseong Office of Education
Registry name: GOEHS-AS-KR-KR - Kyeonggi-Do Hwaseong Office of Education, KR · not in PeeringDB
7IPv4 routes
0.0% RPKI valid · 57.1% with a route object
0IPv6 routes
0RPKI invalid
0 origin · 0 maxLength
7No ROA
3 with no route object for this origin
3Low visibility
seen by under 10% of full-table peers
74Route objects not announced
registered with origin AS38406, seen from no peer
Announced routes
Every prefix a peer of the route collectors sees with origin AS38406, 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.
| 1.238.28.128/25 | No ROA | None | 16 2%low visibility |
| 124.138.137.0/28 | No ROA | Nonecovered by 124.138.137.0/24 | 13 2%low visibility |
| 124.138.137.192/29 | No ROA | Nonecovered by 124.138.137.0/24 | 10 1%low visibility |
| 124.138.137.0/24 | No ROA | Other IRR onlyNTTCOM, RADB | 673 100% |
| 211.114.121.0/24 | No ROA | Other IRR onlyRADB | 673 100% |
| 61.77.45.0/24 | No ROA | Other IRR onlyRADB | 672 100% |
| 211.226.95.0/24 | No ROA | Other IRR onlyRADB | 672 100% |
AS-SET
AS38406 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 88 are in fix.csv.
- ROA: none7
- Route object: none3
- Route object: RIR4
- Route object: not announced74
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 1.238.28.128/25 | No ROA covers it. Add a ROA for AS38406, maxLength 25. |
| Route object: none | 1.238.28.128/25 | No route object for it. Add a route object with origin AS38406 in the RIR database for the space. |
| ROA: none | 124.138.137.0/28 | No ROA covers it. Add a ROA for AS38406, maxLength 28. |
| Route object: none | 124.138.137.0/28 | No route object for it. A route object for 124.138.137.0/24 with origin AS38406 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS38406 in the RIR database for the space. |
| ROA: none | 124.138.137.192/29 | No ROA covers it. Add a ROA for AS38406, maxLength 29. |
| Route object: none | 124.138.137.192/29 | No route object for it. A route object for 124.138.137.0/24 with origin AS38406 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS38406 in the RIR database for the space. |
| ROA: none | 124.138.137.0/24 | No ROA covers it. Add a ROA for AS38406, maxLength 24. |
| Route object: RIR | 124.138.137.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| ROA: none | 211.114.121.0/24 | No ROA covers it. Add a ROA for AS38406, maxLength 24. |
| Route object: RIR | 211.114.121.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 61.77.45.0/24 | No ROA covers it. Add a ROA for AS38406, maxLength 24. |
| Route object: RIR | 61.77.45.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 211.226.95.0/24 | No ROA covers it. Add a ROA for AS38406, maxLength 24. |
| Route object: RIR | 211.226.95.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS38406 whose prefix no peer sees AS38406 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 14.35.152.0/24 | NTTCOM | No ROA |
| 14.35.153.0/24 | NTTCOM | No ROA |
| 14.35.154.0/24 | NTTCOM | No ROA |
| 14.35.155.0/24 | NTTCOM | No ROA |
| 14.35.156.0/24 | NTTCOM | No ROA |
| 14.35.157.0/24 | NTTCOM | No ROA |
| 14.35.158.0/24 | NTTCOM | No ROA |
| 14.35.159.0/24 | NTTCOM | No ROA |
| 14.35.160.0/24 | NTTCOM | No ROA |
| 14.35.161.0/24 | NTTCOM | No ROA |
| 14.35.162.0/24 | NTTCOM | No ROA |
| 111.218.116.0/23 | NTTCOM, RADB | No ROA |
| 117.110.70.0/24 | RADB | No ROA |
| 117.110.72.0/24 | RADB | No ROA |
| 117.110.83.0/24 | RADB | No ROA |
| 122.203.112.0/20 | RADB | No ROA |
| 122.203.112.0/24 | NTTCOM, RADB | No ROA |
| 122.203.113.0/24 | NTTCOM, RADB | No ROA |
| 122.203.114.0/24 | NTTCOM, RADB | No ROA |
| 122.203.115.0/24 | NTTCOM, RADB | No ROA |
| 122.203.116.0/24 | NTTCOM, RADB | No ROA |
| 122.203.117.0/24 | NTTCOM, RADB | No ROA |
| 122.203.118.0/24 | NTTCOM, RADB | No ROA |
| 122.203.119.0/24 | NTTCOM, RADB | No ROA |
| 122.203.120.0/24 | NTTCOM, RADB | No ROA |
| 122.203.121.0/24 | NTTCOM, RADB | No ROA |
| 122.203.122.0/24 | NTTCOM, RADB | No ROA |
| 122.203.123.0/24 | NTTCOM, RADB | No ROA |
| 122.203.124.0/24 | NTTCOM, RADB | No ROA |
| 122.203.125.0/24 | NTTCOM, RADB | No ROA |
| 122.203.126.0/24 | NTTCOM, RADB | No ROA |
| 122.203.127.0/24 | NTTCOM, RADB | No ROA |
| 122.203.128.0/23 | RADB | No ROA |
| 122.203.128.0/24 | NTTCOM, RADB | No ROA |
| 122.203.129.0/24 | NTTCOM, RADB | No ROA |
| 122.203.130.0/24 | NTTCOM, RADB | No ROA |
| 122.203.131.0/24 | RADB | No ROA |
| 122.203.132.0/24 | RADB | No ROA |
| 122.203.133.0/24 | NTTCOM, RADB | No ROA |
| 122.203.134.0/24 | NTTCOM, RADB | No ROA |
| 122.203.135.0/24 | RADB | No ROA |
| 122.203.137.0/24 | NTTCOM, RADB | No ROA |
| 122.203.138.0/23 | RADB | No ROA |
| 122.203.138.0/24 | NTTCOM, RADB | No ROA |
| 122.203.139.0/24 | NTTCOM, RADB | No ROA |
| 122.203.140.0/23 | RADB | No ROA |
| 122.203.140.0/24 | NTTCOM, RADB | No ROA |
| 122.203.141.0/24 | NTTCOM, RADB | No ROA |
| 122.203.201.0/24 | NTTCOM, RADB | No ROA |
| 122.203.202.0/24 | NTTCOM, RADB | No ROA |
| 122.203.203.0/24 | NTTCOM, RADB | No ROA |
| 122.203.204.0/24 | NTTCOM | No ROA |
| 122.203.205.0/24 | NTTCOM, RADB | No ROA |
| 122.203.220.0/24 | RADB | No ROA |
| 122.203.221.0/24 | RADB | No ROA |
| 122.203.244.0/24 | NTTCOM, RADB | No ROA |
| 124.1.57.0/24 | NTTCOM | No ROA |
| 124.138.136.0/24 | NTTCOM, RADB | No ROA |
| 124.138.138.0/24 | NTTCOM, RADB | No ROA |
| 124.138.139.0/24 | NTTCOM, RADB | No ROA |
| 124.138.140.0/24 | NTTCOM, RADB | No ROA |
| 124.138.141.0/24 | NTTCOM, RADB | No ROA |
| 124.138.142.0/24 | NTTCOM, RADB | No ROA |
| 125.246.28.0/23 | RADB | No ROA |
| 125.246.28.0/24 | NTTCOM, RADB | No ROA |
| 125.246.29.0/24 | NTTCOM, RADB | No ROA |
| 125.246.92.0/24 | RADB | No ROA |
| 125.246.121.0/24 | NTTCOM, RADB | No ROA |
| 125.246.162.0/24 | NTTCOM, RADB | No ROA |
| 125.246.164.0/24 | NTTCOM, RADB | No ROA |
| 125.246.188.0/24 | NTTCOM, RADB | No ROA |
| 125.246.206.0/24 | NTTCOM, RADB | No ROA |
| 180.82.55.0/24 | RADB | No ROA |
| 180.82.56.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.