arkecx怎么样？arkecx或者叫Ark Edge Cloud是大名鼎鼎的边缘云服务提供商Zenlayer搞的云服务器品牌，主打中高端企业客户（阿里云、腾讯云、UCloud等云服务商基本都在用他家节点），目前arkecx已拥有全球24个国家和地区机房（其中包括了欧洲西班牙马德里），未来计划拓展到80个。那么Ark Edge Cloud西班牙马德里云服务器性能如何？站长这里作了简单测评供参考：1Gbps大带宽，适合跑国际业务，解锁美区TIKTOK流媒体，具体如下：
Ark Edge Cloud官方网站：门户首页 - Ark Edge Cloud (arkecx.com)（可选中文版本）
Ark Edge Cloud优惠码：Q11NTEH40Q，9折优惠
看下Ark Edge Cloud西班牙马德里云服务器配置信息：站长没开启BBR，zenlayer自己的IP，当前硬盘I/O在234.7MB/s左右；流媒体方面，解锁美区TIKTOK。
看下Ark Edge Cloud西班牙马德里云服务器speedtest.net国内外节点测速：
再来看看部分跨区域流媒体解锁测试结果：
Ark Edge Cloud西班牙马德里云服务器三网Ping测试：
Ark Edge Cloud西班牙马德里云服务器IP不是原生IP，为荷兰阿姆斯特丹广播IP：
Ark Edge Cloud西班牙马德里云服务器丢包率情况：国际不丢包，国内差强人意
FIO再次测试Ark Edge Cloud西班牙马德里云服务器硬盘的读写数据的情况：
Ark Edge Cloud西班牙马德里云服务器iperf3针对欧美的节点的数据测试：
Ark Edge Cloud西班牙马德里云服务器去程路由追踪测试：
电信去程，骨干网对接cogent从美国西海岸横穿东海岸然后去欧洲
联通去程，骨干网对接twelve99直接去欧洲的德国然后过去...
移动去程，移动国际CMI对接cogent直接到英国过法国然后到西班牙
Ark Edge Cloud西班牙马德里云服务器回程路由追踪测试：
1、回程，到国内电信：走cogent从西班牙出来经过法国、英国，从电信英国节点回国；
2、回程，到国内联通：走cogent从西班牙出来经过法国、德国再对接联通骨干回来；
3、回程，到国内移动：北京方向：走telia经过法国到美国洛杉矶，然后走移动洛杉矶节点回来，上海方向：走cogent经过法国、英国对接移动骨干回国，广州方向：走telia经过法国、英国，然后到美国东海岸，再到西海岸的西雅图，从移动西雅图节点回国
Traceroute to China, Guangzhou CT (TCP Mode, Max 30 Hop)
============================================================
traceroute to 113.108.209.1 (113.108.209.1), 30 hops max, 32 byte packets
1 23.90.191.137 32.19 ms AS21859 Spain, Comunidad de Madrid, Madrid, zenlayer.com
2 107.155.19.122 0.87 ms AS21859 Spain, Comunidad de Madrid, Madrid, zenlayer.com
3 107.155.19.102 0.69 ms AS21859 Spain, Comunidad de Madrid, Madrid, zenlayer.com
4 *
5 154.54.61.129 5.62 ms AS174 Spain, Euskadi, Bilbao, cogentco.com
6 62.115.122.139 31.01 ms AS1299 TELIA.COM 骨干网, telia.com
7 *
8 202.97.58.149 33.53 ms AS4134 Germany, Hesse, Frankfurt, ChinaTelecom
9 149.14.81.226 78.20 ms AS174 United Kingdom, London, cogentco.com
10 *
11 *
12 202.97.94.129 319.75 ms AS4134 China, Guangdong, Guangzhou, ChinaTelecom
13 113.108.209.1 273.86 ms AS4134 China, Guangdong, Guangzhou, ChinaTelecom
Traceroute to China, Shanghai CT (TCP Mode, Max 30 Hop)
============================================================
traceroute to 180.153.28.5 (180.153.28.5), 30 hops max, 32 byte packets
1 23.90.191.137 2.14 ms AS21859 Spain, Comunidad de Madrid, Madrid, zenlayer.com
2 107.155.19.122 0.95 ms AS21859 Spain, Comunidad de Madrid, Madrid, zenlayer.com
3 107.155.19.98 0.58 ms AS21859 Spain, Comunidad de Madrid, Madrid, zenlayer.com
4 *
5 154.54.61.129 5.61 ms AS174 Spain, Euskadi, Bilbao, cogentco.com
6 62.115.123.12 31.88 ms AS1299 Germany, Hesse, Frankfurt, telia.com
7 62.115.114.91 30.23 ms AS1299 Germany, Hesse, Frankfurt, telia.com
8 202.97.58.149 33.95 ms AS4134 Germany, Hesse, Frankfurt, ChinaTelecom
9 *
10 202.97.39.6 259.49 ms AS4134 China, Shanghai, ChinaTelecom
11 *
12 61.152.24.213 267.55 ms AS4812 China, Shanghai, ChinaTelecom
13 61.152.25.73 299.26 ms AS4812 China, Shanghai, ChinaTelecom
14 101.95.225.34 285.57 ms AS4811 China, Shanghai, ChinaTelecom
15 101.227.255.46 254.93 ms AS4812 China, Shanghai, ChinaTelecom
16 101.227.255.34 301.31 ms AS4812 China, Shanghai, ChinaTelecom
17 *
18 *
19 *
20 *
21 *
22 *
23 *
24 *
25 *
26 *
27 *
28 *
29 *
30 *
Traceroute to China, Beijing CT (TCP Mode, Max 30 Hop)
============================================================
traceroute to 180.149.128.9 (180.149.128.9), 30 hops max, 32 byte packets
1 23.90.191.137 50.32 ms AS21859 Spain, Comunidad de Madrid, Madrid, zenlayer.com
2 107.155.19.120 0.89 ms AS21859 Spain, Comunidad de Madrid, Madrid, zenlayer.com
3 107.155.19.98 0.42 ms AS21859 Spain, Comunidad de Madrid, Madrid, zenlayer.com
4 *
5 62.115.123.220 23.18 ms AS1299 France, Ile-de-France, Paris, telia.com
6 154.54.61.114 18.04 ms AS174 France, Ile-de-France, Paris, cogentco.com
7 154.54.56.129 24.89 ms AS174 United Kingdom, London, cogentco.com
8 154.54.61.158 24.94 ms AS174 United Kingdom, London, cogentco.com
9 149.14.81.226 26.98 ms AS174 United Kingdom, London, cogentco.com
10 *
11 202.97.12.125 241.25 ms AS4134 China, Beijing, ChinaTelecom
12 *
13 *
14 *
15 *
16 *
17 *
18 *
19 *
20 *
21 *
22 *
23 *
24 *
25 *
26 *
27 *
28 *
29 *
30 *
Traceroute to China, Guangzhou CU (TCP Mode, Max 30 Hop)
============================================================
traceroute to 210.21.4.130 (210.21.4.130), 30 hops max, 32 byte packets
1 23.90.191.137 2.84 ms AS21859 Spain, Comunidad de Madrid, Madrid, zenlayer.com
2 107.155.19.122 0.81 ms AS21859 Spain, Comunidad de Madrid, Madrid, zenlayer.com
3 107.155.19.98 0.60 ms AS21859 Spain, Comunidad de Madrid, Madrid, zenlayer.com
4 *
5 62.115.123.220 23.24 ms AS1299 France, Ile-de-France, Paris, telia.com
6 62.115.123.12 31.77 ms AS1299 Germany, Hesse, Frankfurt, telia.com
7 154.54.58.233 27.11 ms AS174 Germany, Hesse, Frankfurt, cogentco.com
8 *
9 219.158.14.153 221.35 ms AS4837 China, Guangdong, Guangzhou, ChinaUnicom
10 154.25.14.78 27.53 ms AS174 Germany, Hesse, Frankfurt, cogentco.com
11 *
12 219.158.3.237 216.30 ms AS4837 China, Guangdong, Guangzhou, ChinaUnicom
13 219.158.103.33 185.53 ms AS4837 China, Guangdong, Guangzhou, ChinaUnicom
14 219.158.103.217 181.81 ms AS4837 China, Guangdong, Guangzhou, ChinaUnicom
15 *
16 120.80.170.250 186.63 ms AS17622 China, Guangdong, Guangzhou, ChinaUnicom
17 *
18 *
19 *
20 *
21 *
22 *
23 *
24 *
25 *
26 *
27 *
28 *
29 *
30 *
Traceroute to China, Shanghai CU (TCP Mode, Max 30 Hop)
============================================================
traceroute to 58.247.8.158 (58.247.8.158), 30 hops max, 32 byte packets
1 23.90.191.137 35.94 ms AS21859 Spain, Comunidad de Madrid, Madrid, zenlayer.com
2 107.155.19.120 0.84 ms AS21859 Spain, Comunidad de Madrid, Madrid, zenlayer.com
3 107.155.19.96 0.48 ms AS21859 Spain, Comunidad de Madrid, Madrid, zenlayer.com
4 *
5 154.54.61.129 5.53 ms AS174 Spain, Euskadi, Bilbao, cogentco.com
6 62.115.114.99 30.18 ms AS1299 Germany, Hesse, Frankfurt, telia.com
7 154.54.58.233 27.19 ms AS174 Germany, Hesse, Frankfurt, cogentco.com
8 154.54.56.190 27.54 ms AS174 Germany, Hesse, Frankfurt, cogentco.com
9 130.117.0.30 27.42 ms AS174 Germany, Hesse, Frankfurt, cogentco.com
10 219.158.111.137 203.97 ms AS4837 China, Shanghai, ChinaUnicom
11 219.158.19.74 242.73 ms AS4837 China, Shanghai, ChinaUnicom
12 *
13 219.158.115.125 249.04 ms AS4837 China, Shanghai, ChinaUnicom
14 58.247.221.178 237.26 ms AS17621 China, Shanghai, ChinaUnicom
15 139.226.225.22 232.78 ms AS17621 China, Shanghai, ChinaUnicom
16 58.247.8.153 219.75 ms AS17621 China, Shanghai, ChinaUnicom
17 139.226.228.46 205.89 ms AS17621 China, Shanghai, ChinaUnicom
18 *
19 *
20 *
21 *
22 *
23 *
24 *
25 *
26 *
27 *
28 *
29 *
30 *
Traceroute to China, Beijing CU (TCP Mode, Max 30 Hop)
============================================================
traceroute to 123.125.99.1 (123.125.99.1), 30 hops max, 32 byte packets
1 23.90.191.137 1.04 ms AS21859 Spain, Comunidad de Madrid, Madrid, zenlayer.com
2 107.155.19.120 0.97 ms AS21859 Spain, Comunidad de Madrid, Madrid, zenlayer.com
3 107.155.19.98 0.66 ms AS21859 Spain, Comunidad de Madrid, Madrid, zenlayer.com
4 *
5 154.54.61.129 5.35 ms AS174 Spain, Euskadi, Bilbao, cogentco.com
6 62.115.123.12 32.90 ms AS1299 Germany, Hesse, Frankfurt, telia.com
7 *
8 130.117.0.2 27.08 ms AS174 Germany, Hesse, Frankfurt, cogentco.com
9 219.158.5.141 190.37 ms AS4837 China, Guangdong, Guangzhou, ChinaUnicom
10 219.158.15.161 195.44 ms AS4837 China, Beijing, ChinaUnicom
11 219.158.3.181 204.57 ms AS4837 China, Beijing, ChinaUnicom
12 219.158.18.69 196.43 ms AS4837 China, Beijing, ChinaUnicom
13 125.33.186.138 262.15 ms AS4808 China, Beijing, ChinaUnicom
14 61.51.169.174 266.02 ms AS4808 China, Beijing, ChinaUnicom
15 *
16 *
17 123.125.99.1 192.26 ms AS4808 China, Beijing, ChinaUnicom
Traceroute to China, Guangzhou CM (TCP Mode, Max 30 Hop)
============================================================
traceroute to 120.196.212.25 (120.196.212.25), 30 hops max, 32 byte packets
1 23.90.191.137 0.93 ms AS21859 Spain, Comunidad de Madrid, Madrid, zenlayer.com
2 107.155.19.120 1.02 ms AS21859 Spain, Comunidad de Madrid, Madrid, zenlayer.com
3 107.155.19.100 0.55 ms AS21859 Spain, Comunidad de Madrid, Madrid, zenlayer.com
4 *
5 62.115.123.218 25.22 ms AS1299 France, Ile-de-France, Paris, telia.com
6 154.54.85.241 75.93 ms AS174 United States, Virginia, Arlington, cogentco.com
7 154.54.7.158 92.15 ms AS174 United States, Georgia, Atlanta, cogentco.com
8 62.115.47.45 33.38 ms AS1299 Germany, Hesse, Frankfurt, telia.com
9 223.120.10.85 34.46 ms AS58453 Germany, Hesse, Frankfurt, ChinaMobile
10 *
11 *
12 154.54.27.118 150.42 ms AS174 United States, California, Los Angeles, cogentco.com
13 221.176.22.237 260.50 ms AS9808 China, Guangdong, Guangzhou, ChinaMobile
14 111.24.4.249 262.03 ms AS9808 China, Guangdong, Guangzhou, ChinaMobile
15 111.24.5.30 250.25 ms AS9808 China, Guangdong, Guangzhou, ChinaMobile
16 221.183.25.118 273.34 ms AS9808 China, Guangdong, Guangzhou, ChinaMobile
17 211.136.196.198 263.15 ms AS56040 China, Guangdong, Guangzhou, ChinaMobile
18 111.24.5.165 300.48 ms AS9808 China, Guangdong, Guangzhou, ChinaMobile
19 111.24.5.34 328.48 ms AS9808 China, Guangdong, Shenzhen, ChinaMobile
20 *
21 120.196.212.25 261.00 ms AS56040 China, Guangdong, Guangzhou, ChinaMobile
Traceroute to China, Shanghai CM (TCP Mode, Max 30 Hop)
============================================================
traceroute to 221.183.55.22 (221.183.55.22), 30 hops max, 32 byte packets
1 23.90.191.137 24.22 ms AS21859 Spain, Comunidad de Madrid, Madrid, zenlayer.com
2 107.155.19.122 1.01 ms AS21859 Spain, Comunidad de Madrid, Madrid, zenlayer.com
3 107.155.19.102 0.53 ms AS21859 Spain, Comunidad de Madrid, Madrid, zenlayer.com
4 *
5 62.115.123.220 23.40 ms AS1299 France, Ile-de-France, Paris, telia.com
6 154.54.85.241 76.25 ms AS174 United States, Virginia, Arlington, cogentco.com
7 62.115.114.89 31.87 ms AS1299 Germany, Hesse, Frankfurt, telia.com
8 154.54.6.221 94.41 ms AS174 United States, Illinois, Chicago, cogentco.com
9 154.54.42.165 106.10 ms AS174 United States, Missouri, Kansas City, cogentco.com
10 223.120.16.178 267.49 ms AS58453 China, Shanghai, ChinaMobile
11 154.54.41.145 128.25 ms AS174 United States, Utah, Salt Lake City, cogentco.com
12 221.183.55.22 262.41 ms AS9808 China, Shanghai, ChinaMobile
Traceroute to China, Beijing CM (TCP Mode, Max 30 Hop)
============================================================
traceroute to 211.136.25.153 (211.136.25.153), 30 hops max, 32 byte packets
1 23.90.191.137 89.57 ms AS21859 Spain, Comunidad de Madrid, Madrid, zenlayer.com
2 107.155.19.122 15.49 ms AS21859 Spain, Comunidad de Madrid, Madrid, zenlayer.com
3 107.155.19.96 0.51 ms AS21859 Spain, Comunidad de Madrid, Madrid, zenlayer.com
4 *
5 *
6 62.115.123.218 25.08 ms AS1299 France, Ile-de-France, Paris, telia.com
7 62.115.112.242 110.76 ms AS1299 United States, Virginia, Ashburn, telia.com
8 62.115.171.219 174.22 ms AS1299 United States, California, Los Angeles, telia.com
9 62.115.171.219 168.32 ms AS1299 United States, California, Los Angeles, telia.com
10 223.120.6.17 168.40 ms AS58453 United States, California, Los Angeles, ChinaMobile
11 *
12 *
13 221.183.46.250 327.68 ms AS9808 China, Beijing, ChinaMobile
14 *
15 111.24.2.245 305.68 ms AS9808 China, Beijing, ChinaMobile
16 *
17 *
18 *
19 211.136.95.226 335.63 ms AS56048 China, Beijing, ChinaMobile
20 *
21 211.136.25.153 331.44 ms AS56048 China, Beijing, ChinaMobile
Traceroute to China, Beijing Dr.Peng Network IDC Network (TCP Mode, Max 30 Hop)
============================================================
traceroute to 211.167.230.100 (211.167.230.100), 30 hops max, 32 byte packets
1 23.90.191.137 4.83 ms AS21859 Spain, Comunidad de Madrid, Madrid, zenlayer.com
2 107.155.19.120 0.95 ms AS21859 Spain, Comunidad de Madrid, Madrid, zenlayer.com
3 107.155.19.100 0.56 ms AS21859 Spain, Comunidad de Madrid, Madrid, zenlayer.com
4 *
5 62.115.123.220 23.05 ms AS1299 France, Ile-de-France, Paris, telia.com
6 154.54.61.114 17.80 ms AS174 France, Ile-de-France, Paris, cogentco.com
7 154.54.58.233 27.05 ms AS174 Germany, Hesse, Frankfurt, cogentco.com
8 130.117.0.2 27.35 ms AS174 Germany, Hesse, Frankfurt, cogentco.com
9 149.14.89.2 30.21 ms AS174 Germany, Hesse, Frankfurt, cogentco.com
10 219.158.115.121 235.34 ms AS4837 China, Beijing, ChinaUnicom
11 219.158.3.181 202.10 ms AS4837 China, Beijing, ChinaUnicom
12 219.158.9.201 203.95 ms AS4837 China, Beijing, ChinaUnicom
13 61.49.214.26 214.36 ms AS4808 China, Beijing, ChinaUnicom
14 202.106.192.94 224.15 ms AS4808 China, Beijing, ChinaUnicom
15 61.149.212.242 229.93 ms AS4808 China, Beijing, ChinaUnicom
16 202.99.1.234 237.36 ms AS4808 China, Beijing, ChinaUnicom
17 *
18 218.241.253.130 213.80 ms AS4808 China, Beijing, DRPENG
19 211.167.230.100 214.33 ms AS17964 China, Beijing, DRPENG
----------------------------------------------------------------------------------
Ark Edge Cloud西班牙马德里云服务器Geekbench跑分：
Geekbench 5 Benchmark Test:
---------------------------------
Test | Value
|
Single Core | 669
Multi Core | 1172
Full Test | https://browser.geekbench.com/v5/cpu/17034920
arkecx怎么样？Ark Edge Cloud西班牙马德里云服务器测评总结：性能方面还是够用的，对于中小型企业足够了；网络方面，这就适合跑国际业务，不适合针对中国国内，线路基本上都是从欧洲回国或者绕道美国回来，延迟等方面都较高...
最后列下这次测评的机器配置信息和购买入口：
Ark Edge Cloud 24个全球机房-云服务器，标红为此次测评机器。
常规网络，非CN2 GIA，最低1Gbps带宽；季付9.5折、半年9折、年付8.5折
| 内存 | CPU | SSD | 流量 | 价格 | 购买 |
| 1G | 1核 | 25G | 1T/月 | $108/年 | 链接 |
| 2G | 2核 | 75G | 3T/月 | $18/月 | 链接 |
| 4G | 2核 | 100G | 4T/月 | $22/月 | 链接 |
| 4G | 4核 | 100G | 4T/月 | $36/月 | 链接 |
| 8G | 4核 | 160G | 5T/月 | $40/月 | 链接 |
| 8G | 8核 | 200G | 6T/月 | $72/月 | 链接 |
| 16G | 8核 | 300G | 8T/月 | $90/月 | 链接 |
| 32G | 6核 | 600G | 12T/月 | $144/月 | 链接 |
arkecx其他机房测评见：
arkecx怎么样？Ark Edge Cloud美国洛杉矶云服务器测评分享，三网高速直连，值得推荐！
arkecx怎么样？Ark Edge Cloud马来西亚吉隆坡云服务器测评分享，1Gbps大带宽，移动好于联通，联通好于电信
推荐阅读
- arkecx怎么样？Ark Edge Cloud印度孟买云服务器测评分享，电信和移动绕道欧美再回来，联通从印度经过新加坡再回来
- arkecx怎么样？Ark Edge Cloud印度金奈云服务器测评分享，硬盘I/O、CPU性能不错，电信回程绕美，解锁菲律宾区TikTok