bgpreport

Network · data from 2026-11-12

AS38399 GOEYJ-AS-KR-KR - Gyeonggi-do Yeoju Office of Education

Registry name: GOEYJ-AS-KR-KR - Gyeonggi-do Yeoju Office of Education, KR · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS38399, 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.20.0/28 No ROA Nonecovered by 1.238.20.0/24 13 2%low visibility 13
121.133.203.0/28 No ROA Nonecovered by 121.133.203.0/24 13 2%low visibility 13
121.133.203.16/28 No ROA Nonecovered by 121.133.203.0/24 13 2%low visibility 13
121.133.203.32/28 No ROA Nonecovered by 121.133.203.0/24 13 2%low visibility 13
121.133.203.48/28 No ROA Nonecovered by 121.133.203.0/24 13 2%low visibility 13
121.133.203.64/28 No ROA Nonecovered by 121.133.203.0/24 13 2%low visibility 13
121.133.203.80/28 No ROA Nonecovered by 121.133.203.0/24 13 2%low visibility 13
121.133.203.96/28 No ROA Nonecovered by 121.133.203.0/24 13 2%low visibility 13
121.133.203.112/28 No ROA Nonecovered by 121.133.203.0/24 13 2%low visibility 13
121.133.203.128/28 No ROA Nonecovered by 121.133.203.0/24 13 2%low visibility 13
121.133.203.144/28 No ROA Nonecovered by 121.133.203.0/24 13 2%low visibility 13
121.133.203.160/28 No ROA Nonecovered by 121.133.203.0/24 13 2%low visibility 13
121.133.203.176/28 No ROA Nonecovered by 121.133.203.0/24 13 2%low visibility 13
121.133.203.192/28 No ROA Nonecovered by 121.133.203.0/24 13 2%low visibility 13
121.133.203.208/28 No ROA Nonecovered by 121.133.203.0/24 13 2%low visibility 13
121.133.203.224/28 No ROA Nonecovered by 121.133.203.0/24 13 2%low visibility 13
121.133.203.240/28 No ROA Nonecovered by 121.133.203.0/24 13 2%low visibility 13
1.238.20.192/29 No ROA Nonecovered by 1.238.20.0/24 10 1%low visibility 10
1.238.20.0/24 No ROA Other IRR onlyNTTCOM 673 100% 67
1.238.21.0/24 No ROA Other IRR onlyNTTCOM 673 100% 67
121.133.203.0/24 No ROA Other IRR onlyRADB 673 100% 67
218.155.187.0/24 No ROA Other IRR onlyRADB 673 100% 67

AS-SET

AS38399 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 80 are in fix.csv.

  • ROA: none22
  • Route object: none18
  • Route object: RIR4
  • Route object: not announced36
ChangePrefix or setDetailFull-table peers
ROA: none1.238.20.0/28No ROA covers it. Add a ROA for AS38399, maxLength 28.13 of 673
Route object: none1.238.20.0/28No route object for it. A route object for 1.238.20.0/24 with origin AS38399 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS38399 in the RIR database for the space.13 of 673
ROA: none121.133.203.0/28No ROA covers it. Add a ROA for AS38399, maxLength 28.13 of 673
Route object: none121.133.203.0/28No route object for it. A route object for 121.133.203.0/24 with origin AS38399 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS38399 in the RIR database for the space.13 of 673
ROA: none121.133.203.16/28No ROA covers it. Add a ROA for AS38399, maxLength 28.13 of 673
Route object: none121.133.203.16/28No route object for it. A route object for 121.133.203.0/24 with origin AS38399 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS38399 in the RIR database for the space.13 of 673
ROA: none121.133.203.32/28No ROA covers it. Add a ROA for AS38399, maxLength 28.13 of 673
Route object: none121.133.203.32/28No route object for it. A route object for 121.133.203.0/24 with origin AS38399 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS38399 in the RIR database for the space.13 of 673
ROA: none121.133.203.48/28No ROA covers it. Add a ROA for AS38399, maxLength 28.13 of 673
Route object: none121.133.203.48/28No route object for it. A route object for 121.133.203.0/24 with origin AS38399 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS38399 in the RIR database for the space.13 of 673
ROA: none121.133.203.64/28No ROA covers it. Add a ROA for AS38399, maxLength 28.13 of 673
Route object: none121.133.203.64/28No route object for it. A route object for 121.133.203.0/24 with origin AS38399 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS38399 in the RIR database for the space.13 of 673
ROA: none121.133.203.80/28No ROA covers it. Add a ROA for AS38399, maxLength 28.13 of 673
Route object: none121.133.203.80/28No route object for it. A route object for 121.133.203.0/24 with origin AS38399 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS38399 in the RIR database for the space.13 of 673
ROA: none121.133.203.96/28No ROA covers it. Add a ROA for AS38399, maxLength 28.13 of 673
Route object: none121.133.203.96/28No route object for it. A route object for 121.133.203.0/24 with origin AS38399 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS38399 in the RIR database for the space.13 of 673
ROA: none121.133.203.112/28No ROA covers it. Add a ROA for AS38399, maxLength 28.13 of 673
Route object: none121.133.203.112/28No route object for it. A route object for 121.133.203.0/24 with origin AS38399 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS38399 in the RIR database for the space.13 of 673
ROA: none121.133.203.128/28No ROA covers it. Add a ROA for AS38399, maxLength 28.13 of 673
Route object: none121.133.203.128/28No route object for it. A route object for 121.133.203.0/24 with origin AS38399 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS38399 in the RIR database for the space.13 of 673
ROA: none121.133.203.144/28No ROA covers it. Add a ROA for AS38399, maxLength 28.13 of 673
Route object: none121.133.203.144/28No route object for it. A route object for 121.133.203.0/24 with origin AS38399 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS38399 in the RIR database for the space.13 of 673
ROA: none121.133.203.160/28No ROA covers it. Add a ROA for AS38399, maxLength 28.13 of 673
Route object: none121.133.203.160/28No route object for it. A route object for 121.133.203.0/24 with origin AS38399 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS38399 in the RIR database for the space.13 of 673
ROA: none121.133.203.176/28No ROA covers it. Add a ROA for AS38399, maxLength 28.13 of 673
Route object: none121.133.203.176/28No route object for it. A route object for 121.133.203.0/24 with origin AS38399 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS38399 in the RIR database for the space.13 of 673
ROA: none121.133.203.192/28No ROA covers it. Add a ROA for AS38399, maxLength 28.13 of 673
Route object: none121.133.203.192/28No route object for it. A route object for 121.133.203.0/24 with origin AS38399 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS38399 in the RIR database for the space.13 of 673
ROA: none121.133.203.208/28No ROA covers it. Add a ROA for AS38399, maxLength 28.13 of 673
Route object: none121.133.203.208/28No route object for it. A route object for 121.133.203.0/24 with origin AS38399 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS38399 in the RIR database for the space.13 of 673
ROA: none121.133.203.224/28No ROA covers it. Add a ROA for AS38399, maxLength 28.13 of 673
Route object: none121.133.203.224/28No route object for it. A route object for 121.133.203.0/24 with origin AS38399 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS38399 in the RIR database for the space.13 of 673
ROA: none121.133.203.240/28No ROA covers it. Add a ROA for AS38399, maxLength 28.13 of 673
Route object: none121.133.203.240/28No route object for it. A route object for 121.133.203.0/24 with origin AS38399 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS38399 in the RIR database for the space.13 of 673
ROA: none1.238.20.192/29No ROA covers it. Add a ROA for AS38399, maxLength 29.10 of 673
Route object: none1.238.20.192/29No route object for it. A route object for 1.238.20.0/24 with origin AS38399 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS38399 in the RIR database for the space.10 of 673
ROA: none1.238.20.0/24No ROA covers it. Add a ROA for AS38399, maxLength 24.673 of 673
Route object: RIR1.238.20.0/24Route object only in NTTCOM. Add it in the RIR database for the space.673 of 673
ROA: none1.238.21.0/24No ROA covers it. Add a ROA for AS38399, maxLength 24.673 of 673
Route object: RIR1.238.21.0/24Route object only in NTTCOM. Add it in the RIR database for the space.673 of 673
ROA: none121.133.203.0/24No ROA covers it. Add a ROA for AS38399, maxLength 24.673 of 673
Route object: RIR121.133.203.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none218.155.187.0/24No ROA covers it. Add a ROA for AS38399, maxLength 24.673 of 673
Route object: RIR218.155.187.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673

Route objects not announced

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

14.35.101.0/24NTTCOMNo ROA
14.35.102.0/24NTTCOMNo ROA
14.35.103.0/24NTTCOMNo ROA
14.35.104.0/24NTTCOMNo ROA
14.35.105.0/24NTTCOMNo ROA
14.35.106.0/24NTTCOMNo ROA
14.35.107.0/24NTTCOMNo ROA
14.35.108.0/24NTTCOMNo ROA
111.218.104.0/23NTTCOM, RADBNo ROA
111.218.104.0/24NTTCOMNo ROA
122.203.160.0/21RADBNo ROA
122.203.160.0/24NTTCOM, RADBNo ROA
122.203.161.0/24NTTCOM, RADBNo ROA
122.203.162.0/24NTTCOM, RADBNo ROA
122.203.163.0/24NTTCOM, RADBNo ROA
122.203.164.0/24NTTCOM, RADBNo ROA
122.203.165.0/24RADBNo ROA
122.203.166.0/24RADBNo ROA
122.203.167.0/24NTTCOM, RADBNo ROA
122.203.168.0/24NTTCOMNo ROA
122.203.169.0/24RADBNo ROA
122.203.224.0/24NTTCOMNo ROA
122.203.251.0/24NTTCOM, RADBNo ROA
124.138.208.0/24NTTCOM, RADBNo ROA
124.138.209.0/24NTTCOM, RADBNo ROA
124.138.210.0/24NTTCOM, RADBNo ROA
124.138.211.0/24NTTCOM, RADBNo ROA
124.138.212.0/24NTTCOM, RADBNo ROA
124.138.213.0/24NTTCOM, RADBNo ROA
124.138.214.0/24NTTCOM, RADBNo ROA
124.138.215.0/24NTTCOM, RADBNo ROA
124.138.216.0/24NTTCOMNo ROA
124.138.217.0/24NTTCOMNo ROA
125.246.233.0/24NTTCOM, RADBNo ROA
180.81.135.0/24NTTCOMNo ROA
180.81.136.0/24NTTCOMNo 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.