bgpreport

Network · data from 2026-11-12

AS38394 GOESN-AS-KR-KR - Gyeonggido Seongnam Office of Education

Registry name: GOESN-AS-KR-KR - Gyeonggido Seongnam Office of Education, KR · not in PeeringDB

10IPv4 routes 0.0% RPKI valid · 60.0% with a route object
0IPv6 routes
0RPKI invalid 0 origin · 0 maxLength
10No ROA 4 with no route object for this origin
4Low visibility seen by under 10% of full-table peers
80Route objects not announced registered with origin AS38394, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS38394, 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.

220.65.157.0/25 No ROA None 16 2%low visibility 13
1.238.16.0/28 No ROA Nonecovered by 1.238.16.0/24 13 2%low visibility 13
125.251.80.144/28 No ROA None 13 2%low visibility 13
1.238.16.192/29 No ROA Nonecovered by 1.238.16.0/24 10 1%low visibility 10
1.238.16.0/24 No ROA Other IRR onlyNTTCOM 673 100% 67
1.238.17.0/24 No ROA Other IRR onlyNTTCOM 673 100% 67
121.133.198.0/24 No ROA Other IRR onlyRADB 673 100% 67
218.155.29.0/24 No ROA Other IRR onlyRADB 673 100% 67
1.237.5.0/24 No ROA Other IRR onlyNTTCOM 672 100% 67
220.65.181.0/24 No ROA Other IRR onlyNTTCOM, RADB 672 100% 67

AS-SET

AS38394 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 100 are in fix.csv.

  • ROA: none10
  • Route object: none4
  • Route object: RIR6
  • Route object: not announced80
ChangePrefix or setDetailFull-table peers
ROA: none220.65.157.0/25No ROA covers it. Add a ROA for AS38394, maxLength 25.16 of 673
Route object: none220.65.157.0/25No route object for it. Add a route object with origin AS38394 in the RIR database for the space.16 of 673
ROA: none1.238.16.0/28No ROA covers it. Add a ROA for AS38394, maxLength 28.13 of 673
Route object: none1.238.16.0/28No route object for it. A route object for 1.238.16.0/24 with origin AS38394 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS38394 in the RIR database for the space.13 of 673
ROA: none125.251.80.144/28No ROA covers it. Add a ROA for AS38394, maxLength 28.13 of 673
Route object: none125.251.80.144/28No route object for it. Add a route object with origin AS38394 in the RIR database for the space.13 of 673
ROA: none1.238.16.192/29No ROA covers it. Add a ROA for AS38394, maxLength 29.10 of 673
Route object: none1.238.16.192/29No route object for it. A route object for 1.238.16.0/24 with origin AS38394 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS38394 in the RIR database for the space.10 of 673
ROA: none1.238.16.0/24No ROA covers it. Add a ROA for AS38394, maxLength 24.673 of 673
Route object: RIR1.238.16.0/24Route object only in NTTCOM. Add it in the RIR database for the space.673 of 673
ROA: none1.238.17.0/24No ROA covers it. Add a ROA for AS38394, maxLength 24.673 of 673
Route object: RIR1.238.17.0/24Route object only in NTTCOM. Add it in the RIR database for the space.673 of 673
ROA: none121.133.198.0/24No ROA covers it. Add a ROA for AS38394, maxLength 24.673 of 673
Route object: RIR121.133.198.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none218.155.29.0/24No ROA covers it. Add a ROA for AS38394, maxLength 24.673 of 673
Route object: RIR218.155.29.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none1.237.5.0/24No ROA covers it. Add a ROA for AS38394, maxLength 24.672 of 673
Route object: RIR1.237.5.0/24Route object only in NTTCOM. Add it in the RIR database for the space.672 of 673
ROA: none220.65.181.0/24No ROA covers it. Add a ROA for AS38394, maxLength 24.672 of 673
Route object: RIR220.65.181.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.672 of 673

Route objects not announced

Route objects with origin AS38394 whose prefix no peer sees AS38394 announce. Many are kept on purpose (backup routes, space announced only in some places).

14.35.64.0/24NTTCOMNo ROA
14.35.65.0/24NTTCOMNo ROA
14.35.66.0/24NTTCOMNo ROA
14.35.67.0/24NTTCOMNo ROA
14.35.68.0/24NTTCOMNo ROA
14.35.69.0/24NTTCOMNo ROA
14.35.70.0/24NTTCOMNo ROA
14.35.71.0/24NTTCOMNo ROA
14.35.72.0/24NTTCOMNo ROA
14.35.73.0/24NTTCOMNo ROA
14.35.74.0/24NTTCOMNo ROA
14.35.75.0/24NTTCOMNo ROA
14.35.76.0/24NTTCOMNo ROA
14.35.77.0/24NTTCOMNo ROA
14.35.78.0/24NTTCOMNo ROA
14.35.79.0/24NTTCOMNo ROA
14.35.80.0/24NTTCOMNo ROA
14.35.81.0/24NTTCOMNo ROA
111.218.176.0/22NTTCOM, RADBNo ROA
111.218.180.0/24NTTCOM, RADBNo ROA
122.153.78.0/23RADBNo ROA
122.153.78.0/24RADBNo ROA
122.153.79.0/24RADBNo ROA
122.153.80.0/24NTTCOM, RADBNo ROA
122.153.81.0/24RADBNo ROA
122.153.82.0/23RADBNo ROA
122.153.82.0/24NTTCOM, RADBNo ROA
122.153.83.0/24NTTCOM, RADBNo ROA
122.153.84.0/22RADBNo ROA
122.153.84.0/24NTTCOM, RADBNo ROA
122.153.85.0/24NTTCOM, RADBNo ROA
122.153.86.0/24NTTCOM, RADBNo ROA
122.153.87.0/24NTTCOM, RADBNo ROA
122.153.88.0/24RADBNo ROA
122.153.89.0/24NTTCOM, RADBNo ROA
122.153.90.0/24RADBNo ROA
122.153.91.0/24RADBNo ROA
122.153.92.0/24RADBNo ROA
122.153.93.0/24NTTCOM, RADBNo ROA
122.153.94.0/23RADBNo ROA
122.153.94.0/24NTTCOM, RADBNo ROA
122.153.95.0/24NTTCOMNo ROA
122.153.99.0/24RADBNo ROA
122.203.55.0/24RADBNo ROA
122.203.192.0/24RADBNo ROA
122.203.195.0/24RADBNo ROA
122.203.198.0/24RADBNo ROA
122.203.199.0/24NTTCOMNo ROA
122.203.200.0/24NTTCOM, RADBNo ROA
122.203.206.0/24NTTCOMNo ROA
122.203.207.0/24NTTCOMNo ROA
122.203.208.0/24NTTCOMNo ROA
122.203.209.0/24NTTCOMNo ROA
122.203.210.0/24NTTCOMNo ROA
122.203.211.0/24NTTCOM, RADBNo ROA
122.203.212.0/24NTTCOMNo ROA
122.203.213.0/24RADBNo ROA
122.203.214.0/24RADBNo ROA
122.203.215.0/24NTTCOMNo ROA
122.203.216.0/24NTTCOMNo ROA
122.203.217.0/24NTTCOMNo ROA
122.203.247.0/24NTTCOM, RADBNo ROA
124.1.71.0/25NTTCOMNo ROA
124.138.192.0/24NTTCOM, RADBNo ROA
124.138.193.0/24NTTCOM, RADBNo ROA
124.138.194.0/24NTTCOM, RADBNo ROA
124.138.195.0/24NTTCOM, RADBNo ROA
124.138.196.0/24NTTCOM, RADBNo ROA
124.138.197.0/24NTTCOM, RADBNo ROA
124.138.198.0/24NTTCOM, RADBNo ROA
124.138.199.0/24NTTCOM, RADBNo ROA
125.246.222.0/23RADBNo ROA
125.246.222.0/24NTTCOM, RADBNo ROA
125.246.223.0/24NTTCOM, RADBNo ROA
125.246.246.0/24RADBNo ROA
125.246.247.0/24RADBNo ROA
125.250.253.0/24RADBNo ROA
125.251.0.0/24RADBNo ROA
125.251.66.0/24RADBNo ROA
125.251.68.0/24RADBNo 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.