bgpreport

Network · data from 2026-11-12

AS10037 NEXEYE

Registry name: EGFS-AS-KR-KR - EUGENE INVESTMENT FUTURES Co.,Ltd., KR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS10037, 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.
175.113.167.0/24 No ROA Other IRR onlyRADB 670 100% 66

AS-SET

AS10037's PeeringDB record names no 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 86 are in fix.csv.

  • ROA: none1
  • Route object: RIR1
  • Route object: not announced84
ChangePrefix or setDetailFull-table peers
ROA: none175.113.167.0/24No ROA covers it. Add a ROA for AS10037, maxLength 24.670 of 673
Route object: RIR175.113.167.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673

Route objects not announced

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

1.177.128.0/22NTTCOMNo ROA
1.177.132.0/22NTTCOMNo ROA
1.177.136.0/22NTTCOMNo ROA
1.177.140.0/22NTTCOMNo ROA
1.177.144.0/22NTTCOMNo ROA
1.177.148.0/22NTTCOMNo ROA
1.177.152.0/22NTTCOMNo ROA
1.177.156.0/22NTTCOMNo ROA
1.177.212.0/22RADBNo ROA
1.177.216.0/22RADBNo ROA
36.38.128.0/21RADBNo ROA
36.38.136.0/21RADBNo ROA
36.38.144.0/21RADBNo ROA
36.38.152.0/21RADBNo ROA
36.38.160.0/21RADBNo ROA
42.82.0.0/21RADBNo ROA
42.82.8.0/21RADBNo ROA
42.82.16.0/21RADBNo ROA
42.82.24.0/21RADBNo ROA
42.82.96.0/19RADBNo ROA
42.82.96.0/22NTTCOMNo ROA
42.82.100.0/22NTTCOMNo ROA
42.82.104.0/22NTTCOMNo ROA
42.82.108.0/22NTTCOMNo ROA
42.82.112.0/22NTTCOMNo ROA
42.82.116.0/22NTTCOMNo ROA
42.82.120.0/22NTTCOMNo ROA
42.82.124.0/22NTTCOMNo ROA
42.82.224.0/20RADBNo ROA
61.100.64.0/22RADBNo ROA
61.100.68.0/24RADBNo ROA
61.103.132.0/24RADBNo ROA
61.103.133.0/24RADBNo ROA
61.103.134.0/24RADBNo ROA
61.103.136.0/24RADBNo ROA
61.103.137.0/24RADBNo ROA
61.103.138.0/24RADBNo ROA
61.103.139.0/24RADBNo ROA
61.103.140.0/24RADBNo ROA
61.103.141.0/24RADBNo ROA
61.103.142.0/24RADBNo ROA
61.103.143.0/24RADBNo ROA
61.107.187.0/24NTTCOM, RADBNo ROA
113.131.0.0/21NTTCOMNo ROA
113.131.8.0/21NTTCOMNo ROA
113.131.16.0/21NTTCOMNo ROA
113.131.24.0/21NTTCOMNo ROA
113.131.32.0/21NTTCOMNo ROA
113.131.40.0/21NTTCOMNo ROA
113.131.47.0/24RADBNo ROA
113.131.48.0/21NTTCOMNo ROA
113.131.56.0/21NTTCOMNo ROA
113.131.64.0/21NTTCOMNo ROA
113.131.72.0/21NTTCOMNo ROA
113.131.80.0/21NTTCOMNo ROA
113.131.88.0/21NTTCOMNo ROA
113.131.96.0/21NTTCOMNo ROA
113.131.104.0/21NTTCOMNo ROA
113.131.112.0/21NTTCOMNo ROA
113.131.120.0/21RADBNo ROA
113.131.123.0/24RADBNo ROA
125.57.200.0/24RADBNo ROA
125.57.201.0/24RADBNo ROA
125.57.202.0/24RADBNo ROA
125.57.203.0/24NTTCOM, RADBNo ROA
180.182.208.0/20RADBNo ROA
180.182.208.0/21RADBNo ROA
180.182.208.0/24NTTCOMNo ROA
180.182.209.0/24NTTCOMNo ROA
180.182.210.0/24NTTCOMNo ROA
180.182.211.0/24NTTCOMNo ROA
180.182.212.0/24NTTCOMNo ROA
180.182.213.0/24NTTCOMNo ROA
180.182.214.0/24NTTCOMNo ROA
180.182.215.0/24NTTCOMNo ROA
180.182.216.0/21RADBNo ROA
203.255.148.0/22RADBNo ROA
203.255.152.0/21RADBNo ROA
203.255.154.0/24RADBNo ROA
203.255.159.0/24RADBNo ROA
210.109.112.0/21RADBNo ROA
210.109.112.0/22RADBNo ROA
210.109.118.0/23RADBNo ROA
210.122.88.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.