Gcore(gcorelabs)日本VPS简单测试

时间:21-02-25 栏目:VPS评测 作者:赵 容 点击: 510 次

腾讯云,腾讯云服务器,腾讯云促销

部落分享过几次G-core的产品信息,成立于2011年的卢森堡商家gcorelabs运营超过30个机房的VPS主机、CDN和独立服务器产品,其中俄罗斯远东地区伯力、海参崴、亚洲地区日本、韩国、中国香港等都有一定的地理位置优势,而且价格便宜,最低每月仅1.08欧元起。最近促销活动较少,我将下单部分比较感兴趣的机房最低套餐进行一个简单的测试并贴出来以便大家参考。

官方网站:https://gcorelabs.com/cn/hosting/vds/

机房及配置

本次购买的是日本机房(Japan,Tokyo)最低套餐:1核心CPU+512MB内存+20GB硬盘+50M带宽=€4.49/月,操作系统为CentOS7.*

gcore-jp-1

基本信息

VPS管理面板

商家提供了独立的vmmanager面板,主机开通邮件里面有面板地址和登录账户密码等信息,在面板中可以进行重启、开关机、重装、VNC等等各项功能。

gcore-jp-2

磁盘IO测试信息

gcore-jp-io

带宽测试

IO和带宽测试等均使用一键包,本机带宽为50M,不同区域测试基本正常范畴。

gcore-jp-get

去程路由

首先是去程路由,通过各个地区的电信、联通和移动网络去程测试,下图为上海电信和四川电信,同时我也试了其他几个区域电信,基本上差不多。

gcore-jp-from-shdx

gcore-jp-from-scdx

再来看看联通去程线路,与电信一样,走NTT去日本,国内各地区一样,所以我只贴了一张。

gcore-jp-from-shlt

国内移动,分别为成都移动、江苏移动和沈阳移动三个区域测试,感觉北方好于南方,华中和华南移动一般绕香港或者美国质量一般。

gcore-jp-from-cdyd

gcore-jp-from-jsyd

gcore-jp-from-syyd

回程路由

回程线路使用一键包,直接复制上来(所试地区较多,请下拉查看)。

Traceroute to China, Beijing CU (TCP Mode, Max 30 Hop)
============================================================
traceroute to 123.125.99.1 (123.125.99.1), 30 hops max, 60 byte packets
 1  92.38.178.1  0.25 ms  http: json  http: json
 2  10.255.16.182  0.27 ms  http: json  http: json
 3  10.255.16.188  0.34 ms  http: json  http: json
 4  61.200.80.169  1.26 ms  http: json  http: json
 5  129.250.2.100  1.33 ms  http: json  http: json
 6  129.250.7.81  9.14 ms  http: json  http: json
 7  129.250.7.31  8.95 ms  http: json  http: json
 8  219.158.32.33  170.86 ms  http: json  http: json
 9  219.158.16.81  167.80 ms  http: json  http: json
10  219.158.4.169  206.95 ms  http: json  http: json
11  *
12  219.232.11.134  84.17 ms  http: json  http: json
13  61.148.158.106  76.04 ms  http: json  http: json
14  61.135.113.158  75.45 ms  http: json  http: json
15  *
16  *
17  123.125.99.1  78.01 ms  http: json  http: json


Traceroute to China, Beijing CT (TCP Mode, Max 30 Hop)
============================================================
traceroute to 180.149.128.9 (180.149.128.9), 30 hops max, 60 byte packets
 1  92.38.178.1  0.33 ms  http: json  http: json
 2  10.255.16.181  0.35 ms  http: json  http: json
 3  10.255.16.187  0.35 ms  http: json  http: json
 4  61.200.80.169  1.18 ms  http: json  http: json
 5  *
 6  129.250.3.28  1.83 ms  http: json  http: json
 7  129.250.66.54  89.39 ms  http: json  http: json
 8  202.97.62.137  90.04 ms  http: json  http: json
 9  *
10  218.30.28.30  88.94 ms  http: json  http: json
11  218.30.25.226  216.51 ms  http: json  http: json
12  180.149.128.9  88.70 ms  http: json  http: json


Traceroute to China, Beijing CM (TCP Mode, Max 30 Hop)
============================================================
traceroute to 211.136.25.153 (211.136.25.153), 30 hops max, 60 byte packets
 1  92.38.178.1  0.33 ms  http: json  http: json
 2  10.255.16.181  0.30 ms  http: json  http: json
 3  10.255.16.187  0.34 ms  http: json  http: json
 4  61.200.80.169  1.16 ms  http: json  http: json
 5  *
 6  129.250.7.79  8.58 ms  http: json  http: json
 7  129.250.6.98  50.01 ms  http: json  http: json
 8  *
 9  129.250.6.98  50.89 ms  http: json  http: json
10  *
11  223.120.2.53  52.15 ms  http: json  http: json
12  *
13  *
14  *
15  111.24.2.241  107.83 ms  http: json  http: json
16  *
17  *
18  211.136.67.166  90.69 ms  http: json  http: json
19  *
20  *
21  211.136.95.226  106.00 ms  http: json  http: json
22  211.136.95.226  100.94 ms  http: json  http: json
23  211.136.25.153  91.27 ms  http: json  http: json


Traceroute to China, Shanghai CU (TCP Mode, Max 30 Hop)
============================================================
traceroute to 58.247.8.158 (58.247.8.158), 30 hops max, 60 byte packets
 1  92.38.178.1  0.32 ms  http: json  http: json
 2  10.255.16.181  0.33 ms  http: json  http: json
 3  10.255.16.187  0.35 ms  http: json  http: json
 4  61.200.80.169  1.20 ms  http: json  http: json
 5  *
 6  129.250.7.81  9.18 ms  http: json  http: json
 7  129.250.2.40  9.15 ms  http: json  http: json
 8  129.250.66.86  39.36 ms  http: json  http: json
 9  219.158.19.86  44.50 ms  http: json  http: json
10  219.158.19.69  189.61 ms  http: json  http: json
11  *
12  139.226.228.46  197.64 ms  http: json  http: json
13  139.226.225.22  77.42 ms  http: json  http: json
14  58.247.8.153  191.85 ms  http: json  http: json

30  *


Traceroute to China, Shanghai CT (TCP Mode, Max 30 Hop)
============================================================
traceroute to 180.153.28.5 (180.153.28.5), 30 hops max, 60 byte packets
 1  92.38.178.1  0.34 ms  http: json  http: json
 2  10.255.16.181  0.44 ms  http: json  http: json
 3  10.255.16.188  0.44 ms  http: json  http: json
 4  63.222.57.173  1.32 ms  http: json  http: json
 5  129.250.6.128  3.40 ms  http: json  http: json
 6  218.30.53.84  212.71 ms  http: json  http: json
 7  202.97.51.61  137.82 ms  http: json  http: json
 8  202.97.50.194  117.24 ms  http: json  http: json
 9  202.97.94.238  128.72 ms  http: json  http: json
10  *
11  *
12  101.95.207.226  340.17 ms  http: json  http: json
13  *
14  180.153.28.5  110.09 ms  http: 503  http: 503


Traceroute to China, Shanghai CM (TCP Mode, Max 30 Hop)
============================================================
traceroute to 221.183.55.22 (221.183.55.22), 30 hops max, 60 byte packets
 1  92.38.178.1  0.31 ms  http: 503  http: 503
 2  10.255.16.182  0.32 ms  http: 503  http: 503
 3  10.255.16.187  0.40 ms  http: 503  http: 503
 4  61.200.80.169  1.29 ms  http: 503  http: 503
 5  63.218.164.66  99.80 ms  http: 503  http: 503
 6  129.250.7.79  8.69 ms  http: 503  http: 503
 7  129.250.2.43  54.84 ms  http: 503  http: 503
 8  129.250.5.28  54.50 ms  http: 503  http: 503
 9  223.118.3.249  51.79 ms  http: 503  http: 503
10  *
11  221.183.55.22  227.69 ms  http: 503  http: 503


Traceroute to China, Guangzhou CU (TCP Mode, Max 30 Hop)
============================================================
traceroute to 210.21.4.130 (210.21.4.130), 30 hops max, 60 byte packets
 1  92.38.178.1  0.31 ms  http: 503  http: 503
 2  10.255.16.181  0.30 ms  http: 503  http: 503
 3  10.255.16.187  0.39 ms  http: 503  http: 503
 4  61.200.80.173  1.47 ms  http: 503  http: 503
 5  *
 6  129.250.3.33  1.84 ms  http: 503  http: 503
 7  219.158.42.5  168.71 ms  http: 503  http: 503
 8  219.158.103.33  80.55 ms  http: 503  http: 503
 9  219.158.103.217  111.14 ms  http: 503  http: 503
10  120.83.0.62  223.80 ms  http: 503  http: 503
11  120.80.175.78  116.35 ms  http: 503  http: 503

30  *


Traceroute to China, Guangzhou CT (TCP Mode, Max 30 Hop)
============================================================
traceroute to 113.108.209.1 (113.108.209.1), 30 hops max, 60 byte packets
 1  92.38.178.1  0.35 ms  http: 503  http: 503
 2  10.255.16.181  0.32 ms  http: 503  http: 503
 3  10.255.16.188  0.35 ms  http: 503  http: 503
 4  61.200.80.169  1.28 ms  http: 503  http: 503
 5  129.250.6.128  1.46 ms  http: 503  http: 503
 6  129.250.3.22  1.80 ms  http: 503  http: 503
 7  202.97.86.178  208.01 ms  http: 503  http: 503
 8  *
 9  202.97.94.125  66.60 ms  http: 503  http: 503
10  *
11  *
12  113.108.209.1  70.41 ms  http: 503  http: 503


Traceroute to China, Guangzhou CM (TCP Mode, Max 30 Hop)
============================================================
traceroute to 120.196.212.25 (120.196.212.25), 30 hops max, 60 byte packets
 1  92.38.178.1  0.39 ms  http: 503  http: 503
 2  10.255.16.181  0.25 ms  http: 503  http: 503
 3  10.255.16.187  0.40 ms  http: 503  http: 503
 4  61.200.80.173  1.51 ms  http: 503  http: 503
 5  129.250.2.100  1.45 ms  http: 503  http: 503
 6  129.250.7.79  8.48 ms  http: 503  http: 503
 7  129.250.2.43  57.53 ms  http: 503  http: 503
 8  *
 9  223.120.2.53  48.26 ms  http: 503  http: 503
10  *
11  223.120.2.53  51.83 ms  http: 503  http: 503
12  221.183.52.85  58.22 ms  http: 503  http: 503
13  221.183.55.78  65.04 ms  http: 503  http: 503
14  111.24.4.237  56.06 ms  http: 503  http: 503
15  221.176.22.105  168.29 ms  http: 503  http: 503
16  211.136.196.246  72.04 ms  http: 503  http: 503
17  111.24.5.22  66.66 ms  http: 503  http: 503
18  211.136.249.117  158.72 ms  http: 503  http: 503
19  *
20  *
21  120.196.212.25  61.05 ms  http: 503  http: 503


Traceroute to China, Shanghai CU AS9929 (TCP Mode, Max 30 Hop)
============================================================
traceroute to 210.13.66.238 (210.13.66.238), 30 hops max, 60 byte packets
 1  92.38.178.1  0.44 ms  http: 503  http: 503
 2  10.255.16.181  0.36 ms  http: 503  http: 503
 3  10.255.16.187  0.52 ms  http: 503  http: 503
 4  10.255.16.160  0.39 ms  http: 503  http: 503
 5  61.200.80.169  1.16 ms  http: 503  http: 503
 6  129.250.6.126  2.26 ms  http: 503  http: 503
 7  129.250.8.54  33.28 ms  http: 503  http: 503
 8  129.250.8.54  34.79 ms  http: 503  http: 503
 9  218.105.2.205  32.54 ms  http: 503  http: 503
10  218.105.2.210  50.54 ms  http: 503  http: 503
11  210.13.116.82  33.53 ms  http: 503  http: 503
12  210.13.66.237  89.76 ms  http: 503  http: 503
13  210.13.66.238  37.32 ms  http: 503  http: 503


Traceroute to China, Shanghai CT CN2 (TCP Mode, Max 30 Hop)
============================================================
traceroute to 58.32.0.1 (58.32.0.1), 30 hops max, 60 byte packets
 1  92.38.178.1  0.36 ms  http: 503  http: 503
 2  10.255.16.182  0.39 ms  http: 503  http: 503
 3  10.255.16.188  0.37 ms  http: 503  http: 503
 4  63.222.57.173  1.21 ms  http: 503  http: 503
 5  63.223.17.50  52.20 ms  http: 503  http: 503
 6  117.103.177.106  1.60 ms  http: 503  http: 503
 7  59.43.183.1  52.10 ms  http: 503  http: 503
 8  59.43.248.242  111.25 ms  http: 503  http: 503
 9  59.43.130.217  55.32 ms  http: 503  http: 503
10  *
11  101.95.88.226  60.84 ms  http: 503  http: 503
12  58.32.0.1  65.42 ms  http: 503  http: 503


Traceroute to China, Guangzhou CT CN2 Gaming Broadband (TCP Mode, Max 30 Hop)
============================================================
traceroute to 119.121.0.1 (119.121.0.1), 30 hops max, 60 byte packets
 1  92.38.178.1  0.34 ms  http: 503  http: 503
 2  10.255.16.182  0.32 ms  http: 503  http: 503
 3  10.255.16.188  0.41 ms  http: 503  http: 503
 4  61.200.80.169  1.30 ms  http: 503  http: 503
 5  129.250.2.130  1.51 ms  http: 503  http: 503
 6  117.103.177.106  1.56 ms  http: 503  http: 503
 7  59.43.247.114  53.74 ms  http: 503  http: 503
 8  *
 9  59.43.130.101  55.34 ms  http: 503  http: 503
10  59.43.144.210  57.61 ms  http: 503  http: 503
11  183.57.161.10  59.50 ms  http: 503  http: 503
12  119.121.0.1  65.88 ms  http: 503  http: 503


Traceroute to China, Beijing Dr.Peng Home Network (TCP Mode, Max 30 Hop)
============================================================
traceroute to 14.131.128.1 (14.131.128.1), 30 hops max, 60 byte packets
 1  92.38.178.1  0.37 ms  http: 503  http: 503
 2  10.255.16.182  0.32 ms  http: 503  http: 503
 3  10.255.16.187  0.33 ms  http: 503  http: 503
 4  61.200.80.173  1.57 ms  http: 503  http: 503
 5  129.250.6.126  2.45 ms  http: 503  http: 503
 6  129.250.7.81  9.47 ms  http: 503  http: 503
 7  129.250.7.33  9.20 ms  http: 503  http: 503
 8  129.250.8.26  84.55 ms  http: 503  http: 503
 9  219.158.3.141  54.48 ms  http: 503  http: 503
10  *
11  123.126.0.254  115.76 ms  http: 503  http: 503
12  61.148.153.238  116.91 ms  http: 503  http: 503

30  *


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, 60 byte packets
 1  92.38.178.1  0.37 ms  http: 503  http: 503
 2  10.255.16.181  0.34 ms  http: 503  http: 503
 3  10.255.16.188  0.33 ms  http: 503  http: 503
 4  61.200.80.173  1.43 ms  http: 503  http: 503
 5  129.250.6.128  1.38 ms  http: 503  http: 503
 6  129.250.7.79  10.42 ms  http: 503  http: 503
 7  129.250.7.31  8.64 ms  http: 503  http: 503
 8  129.250.9.186  150.80 ms  http: 503  http: 503
 9  219.158.16.77  58.64 ms  http: 503  http: 503
10  219.158.18.65  99.69 ms  http: 503  http: 503
11  *
12  202.106.193.2  213.14 ms  http: 503  http: 503
13  61.51.37.206  100.36 ms  http: 503  http: 503
14  218.241.244.18  207.89 ms  http: 503  http: 503
15  218.241.252.14  91.34 ms  http: 503  http: 503
16  218.241.253.134  199.12 ms  http: 503  http: 503
17  211.167.230.100  98.22 ms  http: 503  http: 503


Traceroute to China, Beijing CERNET (TCP Mode, Max 30 Hop)
============================================================
traceroute to 202.205.109.205 (202.205.109.205), 30 hops max, 60 byte packets
 1  92.38.178.1  0.45 ms  http: 503  http: 503
 2  10.255.16.181  0.31 ms  http: 503  http: 503
 3  10.255.16.188  0.34 ms  http: 503  http: 503
 4  10.255.16.161  0.46 ms  http: 503  http: 503
 5  63.222.57.173  1.21 ms  http: 503  http: 503
 6  63.223.33.197  1.19 ms  http: 503  http: 503
 7  120.29.217.109  0.94 ms  http: 503  http: 503
 8  120.29.217.109  0.94 ms  http: 503  http: 503
 9  180.87.180.13  3.31 ms  http: 503  http: 503
10  209.58.86.142  112.20 ms  http: 503  http: 503
11  63.243.251.1  105.61 ms  http: 503  http: 503
12  66.110.59.182  174.29 ms  http: 503  http: 503
13  101.4.117.213  169.59 ms  http: 503  http: 503
14  101.4.117.101  171.83 ms  http: 503  http: 503
15  101.4.117.101  169.50 ms  http: 503  http: 503
16  202.112.38.82  169.92 ms  http: 503  http: 503
17  202.112.38.158  166.39 ms  http: 503  http: 503
18  202.205.109.205  169.83 ms  http: 503  http: 503


Traceroute to China, Beijing CSTNET (TCP Mode, Max 30 Hop)
============================================================
traceroute to 159.226.254.1 (159.226.254.1), 30 hops max, 60 byte packets
 1  92.38.178.1  0.36 ms  http: 503  http: 503
 2  10.255.16.181  0.40 ms  http: 503  http: 503
 3  10.255.16.187  0.32 ms  http: 503  http: 503
 4  10.255.16.161  0.45 ms  http: 503  http: 503
 5  63.222.57.173  0.82 ms  http: 503  http: 503
 6  63.223.15.70  50.90 ms  http: 503  http: 503
 7  63.223.17.94  52.79 ms  http: 503  http: 503
 8  159.226.254.1  89.15 ms  http: 503  http: 503


Traceroute to China, Beijing GCable (TCP Mode, Max 30 Hop)
============================================================
traceroute to 211.156.140.17 (211.156.140.17), 30 hops max, 60 byte packets
 1  92.38.178.1  0.31 ms  http: 503  http: 503
 2  10.255.16.182  0.38 ms  http: 503  http: 503
 3  10.255.16.187  0.35 ms  http: 503  http: 403
 4  61.200.80.169  1.62 ms  http: 503  http: 403
 5  129.250.6.128  15.77 ms  http: 503  http: 403
 6  218.30.53.84  214.91 ms  http: 503  http: 403
 7  129.250.66.54  90.67 ms  http: 503  http: 403
 8  *
 9  202.97.34.157  93.39 ms  http: 403  http: 403
10  219.141.142.121  91.15 ms  http: 403  http: 403
11  *
12  106.120.252.158  256.15 ms  http: 403  http: 403
13  *
14  211.156.128.225  203.82 ms  http: 403  http: 403
15  211.156.128.85  89.14 ms  http: 403  http: 403
16  211.156.140.17  93.13 ms  http: 403  http: 403

Ping测试

使用IPIP.NET在全国和亚太地区测试结果,毕竟亚洲地区,绝大多数地区的低ping还是不错的。

gcore-jp-ping

 

接下来我还将试试这个商家的俄罗斯伯力和美国的机房,慢慢把感兴趣的都测试一遍看看我本地哪个区域给力些,感兴趣的也可以直接在他们的官网查看:https://gcorelabs.com

香港/美国/国内高速VPS

声明: 博客仅为分享信息绝非推荐,网站不参与交易绝非中介,内容均仅代表个人观点绝非权威,读者请自行考虑后入手并自担风险!一分钱一分货仍是恒久不变之真理,未成年读者(包括生理和心理)请在监护人陪同下访问本站!本文由( 赵 容 )原创编译,转载请保留链接: Gcore(gcorelabs)日本VPS简单测试鄙视无耻复制行为!
关于使用: 本站主要分享服务器及VPS信息,不提供任何产品销售或代购,读者请在国家法律法规许可范围内购买和使用产品,欢迎加入QQ群:683851361讨论.
关于安全: 任何IDC都有倒闭和跑路的可能,主机线路更不可控,月付和备份是您的最佳选择,请保持良好的、有规则的备份习惯.

海星云主机

广而告之