Network · data from 2026-11-12
AS38402 GOESW-AS-KR-KR - Gyeonggi Provincial Suwon Office of Education
Registry name: GOESW-AS-KR-KR - Gyeonggi Provincial Suwon Office of Education, KR · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS38402, 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.
| 211.51.255.0/25 | No ROA | None | 16 2%low visibility |
| 220.78.173.0/25 | No ROA | None | 16 2%low visibility |
| 222.98.10.128/25 | No ROA | None | 16 2%low visibility |
| 1.238.6.0/28 | No ROA | Nonecovered by 1.238.6.0/24 | 13 2%low visibility |
| 1.238.6.192/29 | No ROA | Nonecovered by 1.238.6.0/24 | 10 1%low visibility |
| 1.238.6.0/24 | No ROA | Other IRR onlyNTTCOM | 673 100% |
| 1.238.7.0/24 | No ROA | Other IRR onlyNTTCOM | 673 100% |
| 211.114.120.0/24 | No ROA | Other IRR onlyRADB | 673 100% |
| 1.238.24.0/24 | No ROA | Other IRR onlyNTTCOM | 672 100% |
| 115.23.235.0/24 | No ROA | Other IRR onlyRADB | 672 100% |
| 220.65.141.0/24 | No ROA | Other IRR onlyNTTCOM, RADB | 672 100% |
| 220.65.158.0/24 | No ROA | Other IRR onlyNTTCOM, RADB | 672 100% |
| 220.65.207.0/24 | No ROA | Other IRR onlyRADB | 672 100% |
AS-SET
AS38402 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 125 are in fix.csv.
- ROA: none13
- Route object: none5
- Route object: RIR8
- Route object: not announced99
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 211.51.255.0/25 | No ROA covers it. Add a ROA for AS38402, maxLength 25. |
| Route object: none | 211.51.255.0/25 | No route object for it. Add a route object with origin AS38402 in the RIR database for the space. |
| ROA: none | 220.78.173.0/25 | No ROA covers it. Add a ROA for AS38402, maxLength 25. |
| Route object: none | 220.78.173.0/25 | No route object for it. Add a route object with origin AS38402 in the RIR database for the space. |
| ROA: none | 222.98.10.128/25 | No ROA covers it. Add a ROA for AS38402, maxLength 25. |
| Route object: none | 222.98.10.128/25 | No route object for it. Add a route object with origin AS38402 in the RIR database for the space. |
| ROA: none | 1.238.6.0/28 | No ROA covers it. Add a ROA for AS38402, maxLength 28. |
| Route object: none | 1.238.6.0/28 | No route object for it. A route object for 1.238.6.0/24 with origin AS38402 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS38402 in the RIR database for the space. |
| ROA: none | 1.238.6.192/29 | No ROA covers it. Add a ROA for AS38402, maxLength 29. |
| Route object: none | 1.238.6.192/29 | No route object for it. A route object for 1.238.6.0/24 with origin AS38402 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS38402 in the RIR database for the space. |
| ROA: none | 1.238.6.0/24 | No ROA covers it. Add a ROA for AS38402, maxLength 24. |
| Route object: RIR | 1.238.6.0/24 | Route object only in NTTCOM. Add it in the RIR database for the space. |
| ROA: none | 1.238.7.0/24 | No ROA covers it. Add a ROA for AS38402, maxLength 24. |
| Route object: RIR | 1.238.7.0/24 | Route object only in NTTCOM. Add it in the RIR database for the space. |
| ROA: none | 211.114.120.0/24 | No ROA covers it. Add a ROA for AS38402, maxLength 24. |
| Route object: RIR | 211.114.120.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 1.238.24.0/24 | No ROA covers it. Add a ROA for AS38402, maxLength 24. |
| Route object: RIR | 1.238.24.0/24 | Route object only in NTTCOM. Add it in the RIR database for the space. |
| ROA: none | 115.23.235.0/24 | No ROA covers it. Add a ROA for AS38402, maxLength 24. |
| Route object: RIR | 115.23.235.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 220.65.141.0/24 | No ROA covers it. Add a ROA for AS38402, maxLength 24. |
| Route object: RIR | 220.65.141.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| ROA: none | 220.65.158.0/24 | No ROA covers it. Add a ROA for AS38402, maxLength 24. |
| Route object: RIR | 220.65.158.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| ROA: none | 220.65.207.0/24 | No ROA covers it. Add a ROA for AS38402, maxLength 24. |
| Route object: RIR | 220.65.207.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS38402 whose prefix no peer sees AS38402 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 14.35.125.0/24 | RADB | No ROA |
| 14.35.126.0/24 | RADB | No ROA |
| 14.35.127.0/24 | RADB | No ROA |
| 14.35.128.0/24 | NTTCOM | No ROA |
| 14.35.129.0/24 | NTTCOM | No ROA |
| 14.35.130.0/24 | NTTCOM | No ROA |
| 14.35.131.0/24 | NTTCOM | No ROA |
| 14.35.132.0/24 | NTTCOM | No ROA |
| 14.35.133.0/24 | NTTCOM | No ROA |
| 14.35.134.0/24 | NTTCOM | No ROA |
| 14.35.135.0/24 | NTTCOM | No ROA |
| 14.35.136.0/24 | NTTCOM | No ROA |
| 14.35.137.0/24 | NTTCOM | No ROA |
| 14.35.138.0/24 | NTTCOM | No ROA |
| 14.35.139.0/24 | NTTCOM | No ROA |
| 14.35.140.0/24 | NTTCOM | No ROA |
| 14.35.190.0/24 | RADB | No ROA |
| 111.218.92.0/23 | NTTCOM, RADB | No ROA |
| 111.218.94.0/24 | NTTCOM, RADB | No ROA |
| 122.203.32.0/20 | RADB | No ROA |
| 122.203.32.0/24 | NTTCOM, RADB | No ROA |
| 122.203.33.0/24 | NTTCOM | No ROA |
| 122.203.34.0/24 | NTTCOM | No ROA |
| 122.203.35.0/24 | NTTCOM | No ROA |
| 122.203.36.0/24 | NTTCOM | No ROA |
| 122.203.37.0/24 | NTTCOM, RADB | No ROA |
| 122.203.38.0/23 | RADB | No ROA |
| 122.203.38.0/24 | NTTCOM, RADB | No ROA |
| 122.203.39.0/24 | NTTCOM, RADB | No ROA |
| 122.203.40.0/24 | NTTCOM, RADB | No ROA |
| 122.203.41.0/24 | NTTCOM | No ROA |
| 122.203.42.0/23 | RADB | No ROA |
| 122.203.42.0/24 | NTTCOM, RADB | No ROA |
| 122.203.43.0/24 | NTTCOM, RADB | No ROA |
| 122.203.44.0/22 | RADB | No ROA |
| 122.203.44.0/24 | NTTCOM, RADB | No ROA |
| 122.203.45.0/24 | NTTCOM, RADB | No ROA |
| 122.203.46.0/24 | NTTCOM, RADB | No ROA |
| 122.203.47.0/24 | NTTCOM, RADB | No ROA |
| 122.203.48.0/22 | RADB | No ROA |
| 122.203.48.0/24 | NTTCOM, RADB | No ROA |
| 122.203.49.0/24 | NTTCOM, RADB | No ROA |
| 122.203.50.0/24 | NTTCOM, RADB | No ROA |
| 122.203.51.0/24 | NTTCOM, RADB | No ROA |
| 122.203.52.0/24 | RADB | No ROA |
| 122.203.53.0/24 | RADB | No ROA |
| 122.203.54.0/24 | RADB | No ROA |
| 122.203.56.0/21 | RADB | No ROA |
| 122.203.56.0/23 | RADB | No ROA |
| 122.203.56.0/24 | RADB | No ROA |
| 122.203.57.0/24 | RADB | No ROA |
| 122.203.58.0/24 | NTTCOM, RADB | No ROA |
| 122.203.59.0/24 | NTTCOM, RADB | No ROA |
| 122.203.60.0/24 | NTTCOM, RADB | No ROA |
| 122.203.61.0/24 | NTTCOM, RADB | No ROA |
| 122.203.62.0/24 | NTTCOM, RADB | No ROA |
| 122.203.63.0/24 | NTTCOM, RADB | No ROA |
| 122.203.226.0/24 | RADB | No ROA |
| 122.203.227.0/24 | RADB | No ROA |
| 122.203.242.0/24 | NTTCOM, RADB | No ROA |
| 124.1.131.0/24 | RADB | No ROA |
| 124.1.132.0/24 | RADB | No ROA |
| 124.138.202.0/24 | NTTCOM, RADB | No ROA |
| 124.138.203.0/24 | NTTCOM, RADB | No ROA |
| 124.138.204.0/24 | NTTCOM, RADB | No ROA |
| 124.138.205.0/24 | NTTCOM, RADB | No ROA |
| 124.138.206.0/24 | NTTCOM, RADB | No ROA |
| 125.246.26.0/24 | NTTCOM, RADB | No ROA |
| 125.246.32.0/24 | NTTCOM, RADB | No ROA |
| 125.246.38.0/24 | NTTCOM, RADB | No ROA |
| 125.246.44.0/23 | RADB | No ROA |
| 125.246.44.0/24 | NTTCOM | No ROA |
| 125.246.45.0/24 | NTTCOM | No ROA |
| 125.246.46.0/24 | NTTCOM, RADB | No ROA |
| 125.246.63.0/24 | NTTCOM, RADB | No ROA |
| 125.246.64.0/22 | RADB | No ROA |
| 125.246.64.0/24 | NTTCOM, RADB | No ROA |
| 125.246.65.0/24 | NTTCOM, RADB | No ROA |
| 125.246.66.0/24 | NTTCOM, RADB | No ROA |
| 125.246.67.0/24 | NTTCOM, RADB | No ROA |
| 125.246.68.0/24 | NTTCOM, RADB | No ROA |
| 125.246.130.0/23 | RADB | No ROA |
| 125.246.130.0/24 | NTTCOM, RADB | No ROA |
| 125.246.131.0/24 | NTTCOM, RADB | No ROA |
| 125.246.132.0/23 | RADB | No ROA |
| 125.246.132.0/24 | NTTCOM | No ROA |
| 125.246.133.0/24 | NTTCOM, RADB | No ROA |
| 125.246.134.0/24 | NTTCOM, RADB | No ROA |
| 125.246.191.0/24 | NTTCOM, RADB | No ROA |
| 125.246.217.0/24 | NTTCOM, RADB | No ROA |
| 125.246.218.0/24 | NTTCOM, RADB | No ROA |
| 125.246.242.0/24 | RADB | No ROA |
| 125.246.243.0/24 | NTTCOM, RADB | No ROA |
| 180.82.52.0/24 | RADB | No ROA |
| 180.82.53.0/24 | RADB | No ROA |
| 211.241.116.0/24 | NTTCOM, RADB | No ROA |
| 220.65.126.0/24 | NTTCOM, RADB | No ROA |
| 220.65.158.0/23 | RADB | No ROA |
| 220.65.159.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.