bgpreport

Network · data from 2026-11-12

AS38408 GOEAY-AS-KR-KR - GYEONGGI PROVINCIAL ANYANG OFFICE OF EDUCATION

Registry name: GOEAY-AS-KR-KR - GYEONGGI PROVINCIAL ANYANG OFFICE OF EDUCATION, KR · not in PeeringDB

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

Announced routes

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

116.122.186.0/25 No ROA None 16 2%low visibility 13
1.241.0.0/28 No ROA Nonecovered by 1.241.0.0/24 13 2%low visibility 13
61.77.19.0/28 No ROA Nonecovered by 61.77.19.0/24 13 2%low visibility 13
61.77.19.16/28 No ROA Nonecovered by 61.77.19.0/24 13 2%low visibility 13
61.77.19.32/28 No ROA Nonecovered by 61.77.19.0/24 13 2%low visibility 13
61.77.19.48/28 No ROA Nonecovered by 61.77.19.0/24 13 2%low visibility 13
61.77.19.64/28 No ROA Nonecovered by 61.77.19.0/24 13 2%low visibility 13
61.77.19.80/28 No ROA Nonecovered by 61.77.19.0/24 13 2%low visibility 13
61.77.19.96/28 No ROA Nonecovered by 61.77.19.0/24 13 2%low visibility 13
61.77.19.112/28 No ROA Nonecovered by 61.77.19.0/24 13 2%low visibility 13
61.77.19.128/28 No ROA Nonecovered by 61.77.19.0/24 13 2%low visibility 13
61.77.19.144/28 No ROA Nonecovered by 61.77.19.0/24 13 2%low visibility 13
61.77.19.160/28 No ROA Nonecovered by 61.77.19.0/24 13 2%low visibility 13
61.77.19.176/28 No ROA Nonecovered by 61.77.19.0/24 13 2%low visibility 13
61.77.19.192/28 No ROA Nonecovered by 61.77.19.0/24 13 2%low visibility 13
61.77.19.208/28 No ROA Nonecovered by 61.77.19.0/24 13 2%low visibility 13
61.77.19.224/28 No ROA Nonecovered by 61.77.19.0/24 13 2%low visibility 13
61.77.19.240/28 No ROA Nonecovered by 61.77.19.0/24 13 2%low visibility 13
1.241.0.0/24 No ROA Other IRR onlyNTTCOM 673 100% 67
1.241.1.0/24 No ROA Other IRR onlyNTTCOM 673 100% 67
61.77.19.0/24 No ROA Other IRR onlyRADB 673 100% 67
61.83.221.0/24 No ROA Other IRR onlyRADB 672 100% 67
122.203.98.0/24 No ROA Other IRR onlyNTTCOM, RADB 672 100% 67
125.246.138.0/24 No ROA Other IRR onlyNTTCOM, RADB 672 100% 67
175.118.239.0/24 No ROA Other IRR onlyNTTCOM 672 100% 67

AS-SET

AS38408 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 99 are in fix.csv.

  • ROA: none25
  • Route object: none18
  • Route object: RIR7
  • Route object: not announced49
ChangePrefix or setDetailFull-table peers
ROA: none116.122.186.0/25No ROA covers it. Add a ROA for AS38408, maxLength 25.16 of 673
Route object: none116.122.186.0/25No route object for it. Add a route object with origin AS38408 in the RIR database for the space.16 of 673
ROA: none1.241.0.0/28No ROA covers it. Add a ROA for AS38408, maxLength 28.13 of 673
Route object: none1.241.0.0/28No route object for it. A route object for 1.241.0.0/24 with origin AS38408 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS38408 in the RIR database for the space.13 of 673
ROA: none61.77.19.0/28No ROA covers it. Add a ROA for AS38408, maxLength 28.13 of 673
Route object: none61.77.19.0/28No route object for it. A route object for 61.77.19.0/24 with origin AS38408 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS38408 in the RIR database for the space.13 of 673
ROA: none61.77.19.16/28No ROA covers it. Add a ROA for AS38408, maxLength 28.13 of 673
Route object: none61.77.19.16/28No route object for it. A route object for 61.77.19.0/24 with origin AS38408 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS38408 in the RIR database for the space.13 of 673
ROA: none61.77.19.32/28No ROA covers it. Add a ROA for AS38408, maxLength 28.13 of 673
Route object: none61.77.19.32/28No route object for it. A route object for 61.77.19.0/24 with origin AS38408 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS38408 in the RIR database for the space.13 of 673
ROA: none61.77.19.48/28No ROA covers it. Add a ROA for AS38408, maxLength 28.13 of 673
Route object: none61.77.19.48/28No route object for it. A route object for 61.77.19.0/24 with origin AS38408 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS38408 in the RIR database for the space.13 of 673
ROA: none61.77.19.64/28No ROA covers it. Add a ROA for AS38408, maxLength 28.13 of 673
Route object: none61.77.19.64/28No route object for it. A route object for 61.77.19.0/24 with origin AS38408 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS38408 in the RIR database for the space.13 of 673
ROA: none61.77.19.80/28No ROA covers it. Add a ROA for AS38408, maxLength 28.13 of 673
Route object: none61.77.19.80/28No route object for it. A route object for 61.77.19.0/24 with origin AS38408 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS38408 in the RIR database for the space.13 of 673
ROA: none61.77.19.96/28No ROA covers it. Add a ROA for AS38408, maxLength 28.13 of 673
Route object: none61.77.19.96/28No route object for it. A route object for 61.77.19.0/24 with origin AS38408 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS38408 in the RIR database for the space.13 of 673
ROA: none61.77.19.112/28No ROA covers it. Add a ROA for AS38408, maxLength 28.13 of 673
Route object: none61.77.19.112/28No route object for it. A route object for 61.77.19.0/24 with origin AS38408 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS38408 in the RIR database for the space.13 of 673
ROA: none61.77.19.128/28No ROA covers it. Add a ROA for AS38408, maxLength 28.13 of 673
Route object: none61.77.19.128/28No route object for it. A route object for 61.77.19.0/24 with origin AS38408 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS38408 in the RIR database for the space.13 of 673
ROA: none61.77.19.144/28No ROA covers it. Add a ROA for AS38408, maxLength 28.13 of 673
Route object: none61.77.19.144/28No route object for it. A route object for 61.77.19.0/24 with origin AS38408 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS38408 in the RIR database for the space.13 of 673
ROA: none61.77.19.160/28No ROA covers it. Add a ROA for AS38408, maxLength 28.13 of 673
Route object: none61.77.19.160/28No route object for it. A route object for 61.77.19.0/24 with origin AS38408 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS38408 in the RIR database for the space.13 of 673
ROA: none61.77.19.176/28No ROA covers it. Add a ROA for AS38408, maxLength 28.13 of 673
Route object: none61.77.19.176/28No route object for it. A route object for 61.77.19.0/24 with origin AS38408 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS38408 in the RIR database for the space.13 of 673
ROA: none61.77.19.192/28No ROA covers it. Add a ROA for AS38408, maxLength 28.13 of 673
Route object: none61.77.19.192/28No route object for it. A route object for 61.77.19.0/24 with origin AS38408 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS38408 in the RIR database for the space.13 of 673
ROA: none61.77.19.208/28No ROA covers it. Add a ROA for AS38408, maxLength 28.13 of 673
Route object: none61.77.19.208/28No route object for it. A route object for 61.77.19.0/24 with origin AS38408 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS38408 in the RIR database for the space.13 of 673
ROA: none61.77.19.224/28No ROA covers it. Add a ROA for AS38408, maxLength 28.13 of 673
Route object: none61.77.19.224/28No route object for it. A route object for 61.77.19.0/24 with origin AS38408 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS38408 in the RIR database for the space.13 of 673
ROA: none61.77.19.240/28No ROA covers it. Add a ROA for AS38408, maxLength 28.13 of 673
Route object: none61.77.19.240/28No route object for it. A route object for 61.77.19.0/24 with origin AS38408 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS38408 in the RIR database for the space.13 of 673
ROA: none1.241.0.0/24No ROA covers it. Add a ROA for AS38408, maxLength 24.673 of 673
Route object: RIR1.241.0.0/24Route object only in NTTCOM. Add it in the RIR database for the space.673 of 673
ROA: none1.241.1.0/24No ROA covers it. Add a ROA for AS38408, maxLength 24.673 of 673
Route object: RIR1.241.1.0/24Route object only in NTTCOM. Add it in the RIR database for the space.673 of 673
ROA: none61.77.19.0/24No ROA covers it. Add a ROA for AS38408, maxLength 24.673 of 673
Route object: RIR61.77.19.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none61.83.221.0/24No ROA covers it. Add a ROA for AS38408, maxLength 24.672 of 673
Route object: RIR61.83.221.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none122.203.98.0/24No ROA covers it. Add a ROA for AS38408, maxLength 24.672 of 673
Route object: RIR122.203.98.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.672 of 673
ROA: none125.246.138.0/24No ROA covers it. Add a ROA for AS38408, maxLength 24.672 of 673
Route object: RIR125.246.138.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.672 of 673
ROA: none175.118.239.0/24No ROA covers it. Add a ROA for AS38408, maxLength 24.672 of 673
Route object: RIR175.118.239.0/24Route object only in NTTCOM. Add it in the RIR database for the space.672 of 673

Route objects not announced

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

14.35.117.0/24NTTCOMNo ROA
14.35.118.0/24NTTCOMNo ROA
14.35.119.0/24NTTCOMNo ROA
14.35.120.0/24NTTCOMNo ROA
14.35.121.0/24NTTCOMNo ROA
14.35.122.0/24NTTCOMNo ROA
14.35.123.0/24NTTCOMNo ROA
14.35.124.0/24NTTCOMNo ROA
61.108.206.0/24RADBNo ROA
111.218.102.0/23NTTCOM, RADBNo ROA
122.203.96.0/21RADBNo ROA
122.203.96.0/24NTTCOM, RADBNo ROA
122.203.97.0/24NTTCOM, RADBNo ROA
122.203.99.0/24NTTCOM, RADBNo ROA
122.203.100.0/24NTTCOM, RADBNo ROA
122.203.101.0/24NTTCOM, RADBNo ROA
122.203.102.0/24NTTCOM, RADBNo ROA
122.203.103.0/24NTTCOM, RADBNo ROA
122.203.104.0/22RADBNo ROA
122.203.104.0/24NTTCOM, RADBNo ROA
122.203.105.0/24NTTCOM, RADBNo ROA
122.203.106.0/24NTTCOM, RADBNo ROA
122.203.107.0/24NTTCOM, RADBNo ROA
122.203.108.0/23RADBNo ROA
122.203.108.0/24NTTCOM, RADBNo ROA
122.203.109.0/24NTTCOM, RADBNo ROA
122.203.110.0/24NTTCOM, RADBNo ROA
122.203.142.0/24RADBNo ROA
122.203.173.0/24NTTCOM, RADBNo ROA
122.203.174.0/23RADBNo ROA
122.203.174.0/24NTTCOM, RADBNo ROA
122.203.175.0/24NTTCOM, RADBNo ROA
122.203.240.0/24NTTCOM, RADBNo ROA
124.1.13.0/24NTTCOMNo ROA
124.1.70.0/24RADBNo ROA
124.1.105.0/24NTTCOMNo ROA
124.138.232.0/24NTTCOM, RADBNo ROA
124.138.233.0/24NTTCOM, RADBNo ROA
125.246.34.0/24NTTCOM, RADBNo ROA
125.246.75.0/24NTTCOM, RADBNo ROA
125.246.77.0/24NTTCOM, RADBNo ROA
125.246.138.0/23RADBNo ROA
125.246.139.0/24NTTCOM, RADBNo ROA
125.246.227.0/24NTTCOM, RADBNo ROA
125.246.228.0/24NTTCOM, RADBNo ROA
125.247.31.0/24RADBNo ROA
125.251.14.0/24NTTCOM, RADBNo ROA
125.251.75.0/24NTTCOM, RADBNo ROA
125.251.76.0/24NTTCOM, RADBNo 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.