bgpreport

Network · data from 2026-11-12

AS38426 KREI-AS-KR-KR - KOREA RURAL ECONOMIC INSTITUTE

Registry name: KREI-AS-KR-KR - KOREA RURAL ECONOMIC INSTITUTE, KR · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS38426, 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.
203.247.167.40/30 Invalid: origin None 2 0%low visibility 2
203.255.237.192/26 No ROA Nonecovered by 203.255.237.0/24 21 3%low visibility 19
211.181.123.0/25 No ROA None 21 3%low visibility 17
59.0.115.104/29 No ROA None 15 2%low visibility 16
203.255.239.252/30 No ROA Nonecovered by 203.255.239.0/24 5 1%low visibility 8
203.255.236.0/22 No ROA Other IRR onlyRADB 672 100% 67
203.255.236.0/24 No ROA Other IRR onlyRADB 672 100% 67
203.255.237.0/24 No ROA Other IRR onlyRADB 672 100% 67
203.255.238.0/24 No ROA Other IRR onlyRADB 672 100% 67
203.255.239.0/24 No ROA Other IRR onlyRADB 672 100% 67

AS-SET

AS38426 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 49 are in fix.csv.

  • ROA: origin1
  • ROA: none9
  • Route object: none5
  • Route object: RIR5
  • Route object: not announced29
ChangePrefix or setDetailFull-table peers
ROA: origin203.247.167.40/30ROAs covering it name AS1237, not AS38426. If AS38426 should announce it, add a ROA for AS38426.2 of 673
Route object: none203.247.167.40/30No route object for it. Add a route object with origin AS38426 in the RIR database for the space.2 of 673
ROA: none203.255.237.192/26No ROA covers it. Add a ROA for AS38426, maxLength 26.21 of 673
Route object: none203.255.237.192/26No route object for it. A route object for 203.255.237.0/24 with origin AS38426 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS38426 in the RIR database for the space.21 of 673
ROA: none211.181.123.0/25No ROA covers it. Add a ROA for AS38426, maxLength 25.21 of 673
Route object: none211.181.123.0/25No route object for it. Add a route object with origin AS38426 in the RIR database for the space.21 of 673
ROA: none59.0.115.104/29No ROA covers it. Add a ROA for AS38426, maxLength 29.15 of 673
Route object: none59.0.115.104/29No route object for it. Add a route object with origin AS38426 in the RIR database for the space.15 of 673
ROA: none203.255.239.252/30No ROA covers it. Add a ROA for AS38426, maxLength 30.5 of 673
Route object: none203.255.239.252/30No route object for it. A route object for 203.255.239.0/24 with origin AS38426 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS38426 in the RIR database for the space.5 of 673
ROA: none203.255.236.0/22No ROA covers it. Add a ROA for AS38426, maxLength 22.672 of 673
Route object: RIR203.255.236.0/22Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none203.255.236.0/24No ROA covers it. Add a ROA for AS38426, maxLength 24.672 of 673
Route object: RIR203.255.236.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none203.255.237.0/24No ROA covers it. Add a ROA for AS38426, maxLength 24.672 of 673
Route object: RIR203.255.237.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none203.255.238.0/24No ROA covers it. Add a ROA for AS38426, maxLength 24.672 of 673
Route object: RIR203.255.238.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none203.255.239.0/24No ROA covers it. Add a ROA for AS38426, maxLength 24.672 of 673
Route object: RIR203.255.239.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673

Route objects not announced

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

27.117.64.0/18NTTCOM, RADBNo ROA
59.150.136.0/24RADBNo ROA
59.150.157.0/24RADBNo ROA
59.150.158.0/24RADBNo ROA
59.150.159.0/24RADBNo ROA
61.96.7.0/24RADBNo ROA
61.103.128.0/24RADBNo ROA
61.103.129.0/24RADBNo ROA
61.103.135.0/24RADBNo ROA
61.103.144.0/24RADBNo ROA
61.103.145.0/24RADBNo ROA
61.103.146.0/24RADBNo ROA
61.103.154.0/24RADBNo ROA
61.103.155.0/24RADBNo ROA
61.103.159.0/24RADBNo ROA
61.103.189.0/24RADBNo ROA
61.103.190.0/24RADBNo ROA
61.103.191.0/24RADBNo ROA
116.93.192.0/18RADBNo ROA
116.93.192.0/19RADBNo ROA
116.93.192.0/20NTTCOM, RADBNo ROA
116.93.208.0/20NTTCOM, RADBNo ROA
116.93.224.0/19RADBNo ROA
116.93.224.0/20NTTCOM, RADBNo ROA
116.93.240.0/20NTTCOM, RADBNo ROA
125.57.156.0/24RADBNo ROA
125.57.157.0/24RADBNo ROA
125.57.158.0/24RADBNo ROA
211.183.183.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.