edgeNAT韩国原生VPS测评:韩国CN2+BGP,国内延迟低,速度稳定

本文目录
隐藏
1
一、方案介绍
2
二、整体测评
3
三、速度测试
4
四、延迟测试
5
五、丢包测试
6
六、路由测试
7
七、测评总结

edgeNAT前段时间推出了韩国原生VPS系列,价格是月付100元起,可选2Mbps-4Mbps带宽,不限流量,可选Windows系统。今天VSP GO给大家分享下edgeNAT韩国原生VPS测评信息,韩国LG机房,CN2线路,低丢包,国内速度不错。

一、方案介绍

edgeNAT官网:https://www.edgenat.com

edgeNAT优惠码:origin(限时8折)

edgeNAT韩国原生IP套餐位于韩国首尔LG机房,CN2直连线路,电信联通访问非常优异,E5v4+DDR4配置,固态硬盘阵列及热备,适合外贸,建站用途。所有套餐均为无限流量,带宽有限制,2Mbps-4Mbps,2G内存以上的套餐可选Windows系统。

CPU 内存 SSD IPv4/峰值带宽/流量 折后价格 链接
1核 1G 20G 1个IP/2Mbps/无限 月付80 点击直达
2核 2G 20G 1个IP/2Mbps/无限 月付96 点击直达
4核 4G 50G 1个IP/3Mbps/无限 月付176 点击直达
4核 8G 100G 1个IP/4Mbps/无限 月付256 点击直达

本文测试机器为4M带宽的服务器,测试IP:112.196.222.42

二、整体测评

先看下bench测试,IO做了限制,200MB/s不到点,上传带宽限制了4Mbps(峰值带宽),下载带宽则是30Mbps。

这款套餐提供韩国原生IP,可以解锁常见的流媒体服务,包括Netflix,但是这种低带宽好像也没意思:

三、速度测试

首先看下全国速度测试,4Mbps峰值带宽,下载速度限制了30Mbps,全国的速度都比较稳定:

四、延迟测试

韩国机房,直连机房,国内延迟还是比较低的:

线路 最快节点 最慢节点 平均响应
电信 上海26ms 新疆哈密113ms 54.3ms
多线 浙江杭州27ms 河南新乡156ms 70.8ms
联通 福建福州43ms 湖南长沙150ms 89.4ms
移动 江苏镇江74ms 江苏徐州86ms 79.8ms
海外 韩国CN2<1ms 德国268ms 92.0ms

五、丢包测试

韩国CN2+BGP,国内和国际都基本没有丢包:

六、路由测试

韩国CN2+BGP直连,电信双向CN2,联通双向直连,移动绕香港NTT,电信和联通都非常不错。

电信去程路由:

联通去程路由:

移动去程路由:

广州电信回程路由:

traceroute to 113.108.209.1 (113.108.209.1), 30 hops max, 32 byte packets
 1  112.196.222.1  37.61 ms  AS133441  Republic of Korea, Seoul, itk.kr
 2  10.1.254.6  4.87 ms  *  LAN Address
 3  10.1.254.2  2.17 ms  *  LAN Address
 4  10.1.255.2  1.64 ms  *  LAN Address
 5  172.20.15.8  1.14 ms  *  LAN Address
 6  10.6.100.73  5.18 ms  *  LAN Address
 7  10.6.100.41  1.85 ms  *  LAN Address
 8  10.6.100.66  2.12 ms  *  LAN Address
 9  203.195.115.21  1.92 ms  AS4809  Republic of Korea, Seoul, ChinaTelecom
10  59.43.250.33  30.80 ms  *  China, Shanghai, ChinaTelecom
11  59.43.187.77  31.76 ms  *  China, Shanghai, ChinaTelecom
12  59.43.130.213  24.83 ms  *  China, Shanghai, ChinaTelecom
13  59.43.80.145  40.49 ms  *  China, Shanghai, ChinaTelecom
14  202.97.82.94  63.61 ms  AS4134  China, Guangdong, Guangzhou, ChinaTelecom
15  113.96.0.93  69.73 ms  AS58466  China, Guangdong, Guangzhou, ChinaTelecom
16  113.108.209.1  50.45 ms  AS58466  China, Guangdong, Guangzhou, ChinaTelecom

上海电信回程路由:

traceroute to 180.153.28.5 (180.153.28.5), 30 hops max, 32 byte packets
 1  112.196.222.1  3.80 ms  AS133441  Republic of Korea, Seoul, itk.kr
 2  10.1.254.6  4.10 ms  *  LAN Address
 3  10.1.254.2  1.64 ms  *  LAN Address
 4  10.1.255.2  1.97 ms  *  LAN Address
 5  172.20.15.8  1.05 ms  *  LAN Address
 6  10.6.100.73  1.51 ms  *  LAN Address
 7  10.6.100.41  2.68 ms  *  LAN Address
 8  10.6.100.66  1.74 ms  *  LAN Address
 9  203.195.115.21  2.01 ms  AS4809  Republic of Korea, Seoul, ChinaTelecom
10  59.43.247.41  30.83 ms  *  China, Shanghai, ChinaTelecom
11  59.43.187.57  24.13 ms  *  China, Shanghai, ChinaTelecom
12  59.43.138.45  32.84 ms  *  China, Shanghai, ChinaTelecom
13  101.95.88.58  48.89 ms  AS4812  China, Shanghai, ChinaTelecom
14  124.74.166.146  29.31 ms  AS4812  China, Shanghai, ChinaTelecom
15  101.95.225.206  29.35 ms  AS4811  China, Shanghai, ChinaTelecom
16  101.227.255.34  32.69 ms  AS4812  China, Shanghai, ChinaTelecom
17  180.153.28.5  33.06 ms  AS4812  China, Shanghai, ChinaTelecom

北京电信回程路由:

traceroute to 180.149.128.9 (180.149.128.9), 30 hops max, 32 byte packets
 1  112.196.222.1  5.28 ms  AS133441  Republic of Korea, Seoul, itk.kr
 2  10.1.254.6  4.77 ms  *  LAN Address
 3  10.1.254.2  1.76 ms  *  LAN Address
 4  10.1.255.2  34.04 ms  *  LAN Address
 5  172.20.15.6  1.45 ms  *  LAN Address
 6  10.6.100.73  1.40 ms  *  LAN Address
 7  10.6.100.41  2.49 ms  *  LAN Address
 8  10.6.100.66  5.56 ms  *  LAN Address
 9  203.195.115.21  2.08 ms  AS4809  Republic of Korea, Seoul, ChinaTelecom
10  59.43.247.41  30.73 ms  *  China, Shanghai, ChinaTelecom
11  59.43.182.225  47.80 ms  *  China, Beijing, ChinaTelecom
12  *
13  59.43.132.13  51.17 ms  *  China, Beijing, ChinaTelecom
14  *
15  36.110.244.46  52.01 ms  AS23724  China, Beijing, ChinaTelecom
16  36.110.246.198  62.05 ms  AS23724  China, Beijing, ChinaTelecom
17  180.149.128.9  66.73 ms  AS23724  China, Beijing, ChinaTelecom

北京联通回程路由:

traceroute to 123.125.99.1 (123.125.99.1), 30 hops max, 32 byte packets
 1  112.196.222.1  1.72 ms  AS133441  Republic of Korea, Seoul, itk.kr
 2  10.1.254.6  4.87 ms  *  LAN Address
 3  10.1.254.2  1.68 ms  *  LAN Address
 4  10.1.255.4  49.37 ms  *  LAN Address
 5  172.20.15.6  1.13 ms  *  LAN Address
 6  121.189.3.73  1.35 ms  AS4766  Republic of Korea, Seoul, kt.com
 7  112.174.89.94  9.22 ms  AS4766  kt.com
 8  219.158.40.85  55.52 ms  AS4837  China, Shanghai, ChinaUnicom
 9  219.158.6.157  45.46 ms  AS4837  China, Shanghai, ChinaUnicom
10  219.158.7.129  87.16 ms  AS4837  China, Shanghai, ChinaUnicom
11  *
12  *
13  125.33.187.222  46.95 ms  AS4808  China, Beijing, ChinaUnicom
14  124.65.194.138  227.45 ms  AS4808  China, Beijing, ChinaUnicom
15  61.135.113.158  48.01 ms  AS4808  China, Beijing, ChinaUnicom
16  *
17  123.125.99.1  46.79 ms  AS4808  China, Beijing, ChinaUnicom

上海联通回程路由:

traceroute to 58.247.8.158 (58.247.8.158), 30 hops max, 32 byte packets
 1  112.196.222.1  1.78 ms  AS133441  Republic of Korea, Seoul, itk.kr
 2  10.1.254.6  4.04 ms  *  LAN Address
 3  10.1.254.2  1.64 ms  *  LAN Address
 4  10.1.255.4  2.08 ms  *  LAN Address
 5  172.20.15.6  0.99 ms  *  LAN Address
 6  121.189.3.73  1.33 ms  AS4766  Republic of Korea, Seoul, kt.com
 7  219.158.33.237  31.88 ms  AS4837  China, Shanghai, ChinaUnicom
 8  219.158.8.181  43.28 ms  AS4837  China, Guangdong, Guangzhou, ChinaUnicom
 9  *
10  *
11  139.226.228.46  39.07 ms  AS17621  China, Shanghai, ChinaUnicom
12  139.226.225.22  38.61 ms  AS17621  China, Shanghai, ChinaUnicom
13  58.247.8.153  40.88 ms  AS17621  China, Shanghai, ChinaUnicom

广州移动回程路由:

 traceroute to 120.196.212.25 (120.196.212.25), 30 hops max, 32 byte packets
 1  112.196.222.1  1.72 ms  AS133441  Republic of Korea, Seoul, itk.kr
 2  10.1.254.6  4.02 ms  *  LAN Address
 3  10.1.254.2  1.54 ms  *  LAN Address
 4  10.1.255.4  1.83 ms  *  LAN Address
 5  172.20.15.6  1.20 ms  *  LAN Address
 6  182.54.128.98  31.17 ms  AS64050  Japan, Tokyo, bgp.net
 7  182.54.128.66  31.02 ms  AS64050  Japan, Tokyo, bgp.net
 8  103.198.146.50  74.76 ms  AS64050  China, Hong Kong, bgp.net
 9  203.131.242.9  74.85 ms  AS2914  China, Hong Kong, ntt.com
10  129.250.6.99  79.53 ms  AS2914  China, Hong Kong, ntt.com
11  129.250.5.33  78.38 ms  AS2914  ntt.com
12  *
13  223.120.2.53  81.14 ms  AS58453  China, Hong Kong, ChinaMobile
14  *
15  *
16  221.183.25.122  82.80 ms  AS9808  China, Guangdong, Guangzhou, ChinaMobile
17  221.183.68.138  81.16 ms  AS9808  China, Guangdong, Guangzhou, ChinaMobile
18  *
19  111.24.14.74  86.79 ms  AS9808  China, Guangdong, Guangzhou, ChinaMobile
20  211.136.196.234  85.59 ms  AS56040  China, Guangdong, Guangzhou, ChinaMobile
21  211.136.196.202  88.37 ms  AS56040  China, Guangdong, Guangzhou, ChinaMobile
22  211.139.180.110  84.16 ms  AS56040  China, Guangdong, Guangzhou, ChinaMobile
23  *
24  *
25  *
26  120.196.212.25  87.44 ms  AS56040  China, Guangdong, Guangzhou, ChinaMobile

北京移动回程路由:

traceroute to 211.136.25.153 (211.136.25.153), 30 hops max, 32 byte packets
 1  112.196.222.1  1.62 ms  AS133441  Republic of Korea, Seoul, itk.kr
 2  10.1.254.6  5.01 ms  *  LAN Address
 3  10.1.254.2  1.87 ms  *  LAN Address
 4  10.1.255.4  1.43 ms  *  LAN Address
 5  172.20.15.6  1.13 ms  *  LAN Address
 6  182.54.128.98  30.97 ms  AS64050  Japan, Tokyo, bgp.net
 7  182.54.128.66  31.03 ms  AS64050  Japan, Tokyo, bgp.net
 8  103.198.146.50  74.68 ms  AS64050  China, Hong Kong, bgp.net
 9  203.131.242.9  75.05 ms  AS2914  China, Hong Kong, ntt.com
10  129.250.6.99  80.04 ms  AS2914  China, Hong Kong, ntt.com
11  129.250.5.33  81.47 ms  AS2914  ntt.com
12  *
13  223.120.2.53  76.72 ms  AS58453  China, Hong Kong, ChinaMobile
14  *
15  *
16  *
17  *
18  *
19  111.24.2.109  123.21 ms  AS9808  China, Beijing, ChinaMobile
20  111.24.14.54  116.62 ms  AS9808  China, Beijing, ChinaMobile
21  *
22  211.136.63.66  117.30 ms  AS56048  China, Beijing, ChinaMobile
23  *
24  *
25  *
26  211.136.25.153  127.54 ms  AS56048  China, Beijing, ChinaMobile

七、测评总结

总的来看,edgeNAT这款韩国原生VPS还不错,国内延迟、速度、稳定性都还可以,适合建站使用,虽然是原生IP能解锁流媒体,但是带宽太小,解锁了也意义不大。