Network · data from 2026-11-12
AS38411 GOEYI-AS-KR-KR - Yongin office of education
Registry name: GOEYI-AS-KR-KR - Yongin office of education, KR · not in PeeringDB
9IPv4 routes
0.0% RPKI valid · 55.6% with a route object
0IPv6 routes
0RPKI invalid
0 origin · 0 maxLength
9No ROA
4 with no route object for this origin
3Low visibility
seen by under 10% of full-table peers
78Route objects not announced
registered with origin AS38411, seen from no peer
Announced routes
Every prefix a peer of the route collectors sees with origin AS38411, 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.77.120.0/24 | No ROA | None | 673 100% |
| 1.238.28.0/25 | No ROA | None | 16 2%low visibility |
| 124.138.129.0/28 | No ROA | Nonecovered by 124.138.129.0/24 | 13 2%low visibility |
| 124.138.129.192/29 | No ROA | Nonecovered by 124.138.129.0/24 | 10 1%low visibility |
| 124.138.128.0/24 | No ROA | Other IRR onlyNTTCOM, RADB | 673 100% |
| 124.138.129.0/24 | No ROA | Other IRR onlyNTTCOM, RADB | 673 100% |
| 211.114.122.0/24 | No ROA | Other IRR onlyRADB | 673 100% |
| 218.147.129.0/24 | No ROA | Other IRR onlyRADB | 673 100% |
| 1.238.12.0/24 | No ROA | Other IRR onlyNTTCOM | 672 100% |
AS-SET
AS38411 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 96 are in fix.csv.
- ROA: none9
- Route object: none4
- Route object: RIR5
- Route object: not announced78
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 61.77.120.0/24 | No ROA covers it. Add a ROA for AS38411, maxLength 24. |
| Route object: none | 61.77.120.0/24 | No route object for it. Add a route object with origin AS38411 in the RIR database for the space. |
| ROA: none | 1.238.28.0/25 | No ROA covers it. Add a ROA for AS38411, maxLength 25. |
| Route object: none | 1.238.28.0/25 | No route object for it. Add a route object with origin AS38411 in the RIR database for the space. |
| ROA: none | 124.138.129.0/28 | No ROA covers it. Add a ROA for AS38411, maxLength 28. |
| Route object: none | 124.138.129.0/28 | No route object for it. A route object for 124.138.129.0/24 with origin AS38411 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS38411 in the RIR database for the space. |
| ROA: none | 124.138.129.192/29 | No ROA covers it. Add a ROA for AS38411, maxLength 29. |
| Route object: none | 124.138.129.192/29 | No route object for it. A route object for 124.138.129.0/24 with origin AS38411 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS38411 in the RIR database for the space. |
| ROA: none | 124.138.128.0/24 | No ROA covers it. Add a ROA for AS38411, maxLength 24. |
| Route object: RIR | 124.138.128.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| ROA: none | 124.138.129.0/24 | No ROA covers it. Add a ROA for AS38411, maxLength 24. |
| Route object: RIR | 124.138.129.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| ROA: none | 211.114.122.0/24 | No ROA covers it. Add a ROA for AS38411, maxLength 24. |
| Route object: RIR | 211.114.122.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 218.147.129.0/24 | No ROA covers it. Add a ROA for AS38411, maxLength 24. |
| Route object: RIR | 218.147.129.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 1.238.12.0/24 | No ROA covers it. Add a ROA for AS38411, maxLength 24. |
| Route object: RIR | 1.238.12.0/24 | Route object only in NTTCOM. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS38411 whose prefix no peer sees AS38411 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 14.35.141.0/24 | NTTCOM | No ROA |
| 14.35.142.0/24 | NTTCOM | No ROA |
| 14.35.143.0/24 | NTTCOM | No ROA |
| 14.35.144.0/24 | NTTCOM | No ROA |
| 14.35.145.0/24 | NTTCOM | No ROA |
| 14.35.146.0/24 | NTTCOM | No ROA |
| 14.35.147.0/24 | NTTCOM | No ROA |
| 14.35.148.0/24 | NTTCOM | No ROA |
| 14.35.149.0/24 | NTTCOM | No ROA |
| 14.35.150.0/24 | NTTCOM | No ROA |
| 14.35.151.0/24 | NTTCOM | No ROA |
| 111.218.108.0/23 | NTTCOM, RADB | No ROA |
| 117.110.84.0/24 | NTTCOM, RADB | No ROA |
| 117.110.85.0/24 | NTTCOM | No ROA |
| 117.110.86.0/24 | NTTCOM | No ROA |
| 117.110.87.0/24 | RADB | No ROA |
| 117.110.89.0/24 | RADB | No ROA |
| 117.110.90.0/24 | NTTCOM | No ROA |
| 122.203.64.0/24 | RADB | No ROA |
| 122.203.65.0/24 | NTTCOM, RADB | No ROA |
| 122.203.66.0/23 | RADB | No ROA |
| 122.203.66.0/24 | NTTCOM, RADB | No ROA |
| 122.203.67.0/24 | NTTCOM, RADB | No ROA |
| 122.203.68.0/22 | RADB | No ROA |
| 122.203.68.0/24 | NTTCOM, RADB | No ROA |
| 122.203.69.0/24 | NTTCOM, RADB | No ROA |
| 122.203.70.0/24 | NTTCOM, RADB | No ROA |
| 122.203.71.0/24 | NTTCOM, RADB | No ROA |
| 122.203.72.0/21 | RADB | No ROA |
| 122.203.72.0/24 | NTTCOM, RADB | No ROA |
| 122.203.73.0/24 | NTTCOM, RADB | No ROA |
| 122.203.74.0/24 | NTTCOM, RADB | No ROA |
| 122.203.75.0/24 | NTTCOM, RADB | No ROA |
| 122.203.76.0/24 | NTTCOM, RADB | No ROA |
| 122.203.77.0/24 | NTTCOM, RADB | No ROA |
| 122.203.78.0/24 | NTTCOM, RADB | No ROA |
| 122.203.79.0/24 | NTTCOM, RADB | No ROA |
| 122.203.80.0/22 | RADB | No ROA |
| 122.203.80.0/24 | NTTCOM, RADB | No ROA |
| 122.203.81.0/24 | NTTCOM, RADB | No ROA |
| 122.203.82.0/24 | NTTCOM, RADB | No ROA |
| 122.203.83.0/24 | NTTCOM, RADB | No ROA |
| 122.203.84.0/23 | RADB | No ROA |
| 122.203.84.0/24 | NTTCOM, RADB | No ROA |
| 122.203.85.0/24 | NTTCOM, RADB | No ROA |
| 122.203.86.0/24 | NTTCOM, RADB | No ROA |
| 122.203.88.0/22 | RADB | No ROA |
| 122.203.88.0/24 | NTTCOM, RADB | No ROA |
| 122.203.89.0/24 | NTTCOM, RADB | No ROA |
| 122.203.90.0/24 | NTTCOM, RADB | No ROA |
| 122.203.91.0/24 | NTTCOM, RADB | No ROA |
| 122.203.92.0/24 | NTTCOM, RADB | No ROA |
| 122.203.228.0/24 | NTTCOM | No ROA |
| 122.203.229.0/24 | NTTCOM | No ROA |
| 122.203.249.0/24 | NTTCOM, RADB | No ROA |
| 124.1.69.0/24 | NTTCOM | No ROA |
| 124.3.88.0/24 | NTTCOM | No ROA |
| 124.138.128.0/22 | RADB | No ROA |
| 124.138.130.0/24 | NTTCOM, RADB | No ROA |
| 124.138.131.0/24 | NTTCOM, RADB | No ROA |
| 124.138.132.0/24 | NTTCOM, RADB | No ROA |
| 125.246.56.0/24 | NTTCOM, RADB | No ROA |
| 125.246.108.0/23 | RADB | No ROA |
| 125.246.108.0/24 | NTTCOM, RADB | No ROA |
| 125.246.109.0/24 | NTTCOM, RADB | No ROA |
| 125.246.111.0/24 | NTTCOM, RADB | No ROA |
| 125.246.173.0/24 | NTTCOM, RADB | No ROA |
| 125.246.174.0/24 | NTTCOM, RADB | No ROA |
| 125.246.175.0/24 | RADB | No ROA |
| 125.246.177.0/24 | NTTCOM, RADB | No ROA |
| 125.246.211.0/24 | NTTCOM, RADB | No ROA |
| 125.246.235.0/24 | NTTCOM, RADB | No ROA |
| 125.247.11.0/24 | NTTCOM, RADB | No ROA |
| 125.247.79.0/24 | NTTCOM, RADB | No ROA |
| 125.248.133.0/24 | NTTCOM, RADB | No ROA |
| 180.82.75.0/24 | NTTCOM | No ROA |
| 180.82.76.0/24 | NTTCOM | No ROA |
| 180.82.77.0/24 | NTTCOM | 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.