80VPS新平台洛杉矶Cera机房(联通CUVIP线路)KVM简单测试

作者:VPSok 发布时间:2021年02月27日 分类:VPS评测 No Comments

前段时间分享过80VPS新上平台及推出洛杉矶Cera机房联通CUVIP线路主机的消息,采用AMD Ryzen系列CPU NVMe磁盘组合,刚好下了个最低配年付套餐,所以贴一下部分测试信息,给大家参考。关于联通CUVIP线路,最近炒得挺凶的斯巴达(SpartanHost)就是走这个线路的,2月份Cera从上海联通了拉了2条100G的AS4837,三网走自有线路去程,回程走上海联通AS4837。

产品信息:https://www.vpsok.net/24696.html

主机配置

关于机房在文章头部说明了,本次所涉VPS配置为双核CPU,1GB内存,20GB系统盘 10GB数据盘,1TB月流量,操作系统我安装的是CentOS7.6

80-cera-1

基本信息

新的平台采用了魔方的系统(旧平台为云谷系统),在账户和产品管理方面都是差不多的,VPS管理的各项功能都很全面,使用上没有什么不适感,资源使用图表更加直观,vnc功能更稳定。

IO和带宽测试

使用了2个一键包分别测试,下面是第一张,SuperSpeed全面测试脚本,线路带宽充裕,是200Mbps带宽。

80-cera-get02

下面是第二个脚本测试,包括了IO信息。

80-cera-get

去程路由

去程路由我在不同的运营商不同的地区进行了多次的测试,就不全部贴上来了,三网自有线路去程,总体上是电信走AS4134去程,联通走AS4837去程,移动走AS9808去程。

电信去程

80-cera-from-hbdx

80-cera-from-fsdx

联通去程

80-cera-from-sdlt

80-cera-from-tjlt

移动去程

80-cera-from-hnyd

80-cera-from-scyd

回程路由

回程路由就使用脚本测试,直接贴上执行结果,三网回程走上海联通AS4837

----------------------------------------------------------------------
广州电信
traceroute to 14.215.116.1 (14.215.116.1), 30 hops max, 60 byte packets
 1  10.0.2.1  0.13 ms  http: json  http: json
 2  154.208.11.129  3.60 ms  http: json  http: json
 3  23.224.21.54  1.64 ms  http: json  http: json
 4  *
 5  192.168.101.62  1.74 ms  http: json  http: json
 6  *
 7  23.225.225.65  136.77 ms  http: json  http: json
 8  219.158.116.233  166.40 ms  http: json  http: json
 9  219.158.113.118  187.10 ms  http: json  http: json
10  219.158.113.101  165.81 ms  http: json  http: json
11  219.158.107.30  195.55 ms  http: json  http: json
12  219.158.9.38  191.14 ms  http: json  http: json
13  202.97.17.145  207.66 ms  http: json  http: json
14  *
15  *
16  *
17  183.56.128.2  199.68 ms  http: json  http: json
18  14.215.116.1  200.59 ms  http: json  http: json

----------------------------------------------------------------------
上海电信
traceroute to 101.95.120.109 (101.95.120.109), 30 hops max, 60 byte packets
 1  10.0.2.1  0.10 ms  http: json  http: json
 2  154.208.11.129  4.00 ms  http: json  http: json
 3  23.224.21.54  1.61 ms  http: json  http: json
 4  192.168.101.201  1.94 ms  http: json  http: json
 5  192.168.101.62  1.81 ms  http: json  http: json
 6  *
 7  23.225.225.65  140.20 ms  http: json  http: json
 8  219.158.97.181  135.81 ms  http: json  http: json
 9  219.158.113.138  137.09 ms  http: json  http: json
10  *
11  219.158.109.174  164.51 ms  http: json  http: json
12  202.97.17.189  135.15 ms  http: json  http: json
13  *
14  61.152.25.197  163.93 ms  http: json  http: json
15  101.95.120.109  134.18 ms  http: json  http: json

----------------------------------------------------------------------
厦门电信
traceroute to 117.28.254.129 (117.28.254.129), 30 hops max, 60 byte packets
 1  10.0.2.1  0.13 ms  http: json  http: json
 2  154.208.11.129  6.04 ms  http: json  http: json
 3  23.224.21.54  1.63 ms  http: json  http: json
 4  *
 5  192.168.101.62  2.05 ms  http: json  http: json
 6  *
 7  23.225.225.65  135.28 ms  http: json  http: json
 8  219.158.97.177  161.14 ms  http: json  http: json
 9  219.158.113.122  165.83 ms  http: json  http: json
10  219.158.113.101  150.55 ms  http: json  http: json
11  219.158.18.150  166.42 ms  http: json  http: json
12  219.158.12.46  168.35 ms  http: json  http: json
13  *
14  *
15  27.159.81.22  174.98 ms  http: json  http: json
16  27.148.195.90  173.29 ms  http: json  http: json
17  117.25.141.106  192.99 ms  http: json  http: json
18  117.28.254.129  185.67 ms  http: json  http: json

----------------------------------------------------------------------
重庆联通
traceroute to 113.207.25.138 (113.207.25.138), 30 hops max, 60 byte packets
 1  10.0.2.1  0.09 ms  http: json  http: json
 2  154.208.11.129  3.27 ms  http: json  http: json
 3  23.224.21.54  1.65 ms  http: json  http: json
 4  *
 5  192.168.101.62  1.70 ms  http: json  http: json
 6  *
 7  23.225.225.65  135.29 ms  http: json  http: json
 8  219.158.116.237  143.04 ms  http: json  http: json
 9  219.158.113.134  143.82 ms  http: json  http: json
10  219.158.113.101  144.06 ms  http: json  http: json
11  219.158.106.254  186.33 ms  http: json  http: json
12  113.207.25.138  181.06 ms  http: json  http: json

----------------------------------------------------------------------
成都联通
traceroute to 119.6.6.6 (119.6.6.6), 30 hops max, 60 byte packets
 1  10.0.2.1  0.09 ms  http: json  http: json
 2  154.208.11.129  4.21 ms  http: json  http: json
 3  23.224.21.54  2.40 ms  http: json  http: json
 4  192.168.101.201  1.93 ms  http: json  http: json
 5  192.168.101.62  1.47 ms  http: json  http: json
 6  *
 7  23.225.225.65  139.82 ms  http: json  http: json
 8  219.158.97.177  157.86 ms  http: json  http: json
 9  219.158.19.86  155.60 ms  http: json  http: json
10  219.158.19.69  160.95 ms  http: json  http: json
11  219.158.104.126  195.56 ms  http: json  http: json
12  119.6.197.170  195.56 ms  http: json  http: json
13  119.7.220.226  255.53 ms  http: json  http: json
14  119.6.6.6  196.19 ms  http: json  http: json

----------------------------------------------------------------------
上海移动
traceroute to 183.192.160.3 (183.192.160.3), 30 hops max, 60 byte packets
 1  10.0.2.1  0.12 ms  http: json  http: json
 2  154.208.11.129  3.09 ms  http: json  http: json
 3  23.224.21.54  1.61 ms  http: json  http: json
 4  *
 5  192.168.101.62  1.55 ms  http: json  http: json
 6  *
 7  23.225.225.65  141.30 ms  http: json  http: json
 8  219.158.116.245  132.93 ms  http: json  http: json
 9  219.158.113.138  133.80 ms  http: json  http: json
10  219.158.113.109  159.29 ms  http: json  http: json
11  219.158.9.98  135.04 ms  http: json  http: json
12  219.158.35.22  153.98 ms  http: json  http: json
13  221.176.17.165  158.90 ms  http: json  http: json
14  *
15  117.143.13.202  163.50 ms  http: json  http: json
16  120.204.194.14  160.55 ms  http: json  http: json
17  120.204.197.126  180.43 ms  http: json  http: json
18  120.204.197.126  163.44 ms  http: json  http: json
19  *
30  *

----------------------------------------------------------------------
成都移动
traceroute to 183.221.253.100 (183.221.253.100), 30 hops max, 60 byte packets
 1  10.0.2.1  0.09 ms  http: json  http: json
 2  154.208.11.129  3.19 ms  http: json  http: json
 3  23.224.21.54  1.59 ms  http: json  http: json
 4  192.168.101.201  1.87 ms  http: json  http: json
 5  192.168.101.62  1.64 ms  http: json  http: json
 6  *
 7  23.225.225.65  137.06 ms  http: json  http: json
 8  219.158.116.233  166.48 ms  http: json  http: json
 9  219.158.113.118  190.19 ms  http: json  http: json
10  219.158.113.101  166.35 ms  http: json  http: json
11  219.158.110.222  212.08 ms  http: json  http: json
12  219.158.9.250  214.58 ms  http: json  http: json
13  219.158.45.226  211.18 ms  http: json  http: json
14  221.176.20.225  205.67 ms  http: json  http: json
15  111.24.8.122  214.59 ms  http: json  http: json
16  111.9.130.38  208.91 ms  http: json  http: json
17  223.87.85.50  214.77 ms  http: json  http: json
18  183.221.253.100  214.52 ms  http: json  http: json

----------------------------------------------------------------------
成都教育网
traceroute to 202.112.14.151 (202.112.14.151), 30 hops max, 60 byte packets
 1  10.0.2.1  0.11 ms  http: json  http: json
 2  154.208.11.129  7.37 ms  http: json  http: json
 3  23.224.21.54  1.45 ms  http: json  http: json
 4  *
 5  192.168.101.62  1.55 ms  http: json  http: json
 6  *
 7  23.225.225.65  137.30 ms  http: json  http: json
 8  219.158.116.233  165.75 ms  http: json  http: json
 9  219.158.19.86  176.48 ms  http: json  http: json
10  219.158.19.81  171.68 ms  http: json  http: json
11  219.158.6.197  203.95 ms  http: json  http: json
12  219.158.5.130  223.64 ms  http: json  http: json
13  219.158.39.54  205.65 ms  http: json  http: json
14  101.4.116.65  200.24 ms  http: json  http: json
15  101.4.116.158  229.48 ms  http: json  http: json
16  202.115.255.2  244.84 ms  http: json  http: json
17  202.115.254.246  226.01 ms  http: json  http: json
18  *
19  202.112.14.151  232.49 ms  http: json  http: json

Ping测试

通过IPIP.NET在中国大陆和港澳台多个节点ping测试结果

80-cera-ping

总的来说联通CUVIP虽然称不上精品线路,但是也算优秀线路了,去程电信走AS4134,联通走AS4837,移动走AS9808,回程均走上海联通AS4837,而且带宽充裕,机器配置也很强,目前商家有常规套餐5折优惠,促销年付套餐349元/年起,感兴趣的可以到商家网站:www.80vps.com

标签: 80VPS, Cera机房, 洛杉矶cera, 80vps测试, CUVIP, CUVIP测试, 联通VIP, 联通VIP线路测试

RackNerd:$16.5/年KVM-1.5GB/20GB/3TB/洛杉矶MC机房

作者:VPSok 发布时间:2021年02月26日 分类:VPS优惠动态 No Comments

前几天分享过一个LET的榜单,RackNerd榜上有名,这里分享下最近商家的促销信息以及近期发布目前仍能购买的产品套餐。商家最近针对洛杉矶MC机房VPS进行了促销,仍然是年付系列,基于KVM架构,其中1.5G内存套餐年付16.5美元起;除此之外,洛杉矶MC机房AMD Ryzen9+NVMe系列有货在售,历史活动最低年付11.95美元起,可选多个地区机房,支持PayPal、信用卡或者支付宝等付款方式。

洛杉矶MC促销VPS

  • CPU:1core
  • 内存:1.5GB
  • 硬盘:20GB
  • 流量:3TB/1Gbps
  • 架构:KVM
  • IP/面板:1IPv4/SolusVM
  • 价格:$16.5/年购买链接
  • CPU:2cores
  • 内存:3GB
  • 硬盘:35GB
  • 流量:5TB/1Gbps
  • 架构:KVM
  • IP/面板:1IPv4/SolusVM
  • 价格:$29.99/年购买链接
  • CPU:3cores
  • 内存:4GB
  • 硬盘:50GB
  • 流量:10TB/1Gbps
  • 架构:KVM
  • IP/面板:1IPv4/SolusVM
  • 价格:$45.89/年购买链接

洛杉矶AMD Ryzen 9+NVMe(Linux系列)

  • CPU:1core
  • 内存:1GB
  • 硬盘:15GB
  • 流量:3TB/1Gbps
  • 架构:KVM
  • IP/面板:1IPv4/SolusVM
  • 价格:$30.88/年购买链接
  • CPU:1core
  • 内存:1GB
  • 硬盘:20GB
  • 流量:2TB/1Gbps
  • 架构:KVM
  • IP/面板:1IPv4/SolusVM
  • 价格:$32.55/年购买链接
  • CPU:1core
  • 内存:1.5GB
  • 硬盘:22GB
  • 流量:3TB/1Gbps
  • 架构:KVM
  • IP/面板:1IPv4/SolusVM
  • 价格:$35.59/年购买链接

洛杉矶AMD Ryzen 9+NVMe(Windows系列)

  • CPU:1core
  • 内存:2GB
  • 硬盘:35GB
  • 流量:2TB/1Gbps
  • 架构:KVM
  • IP/面板:1IPv4/SolusVM
  • 价格:$60/年购买链接
  • CPU:2cores
  • 内存:3.5GB
  • 硬盘:60GB
  • 流量:3.5TB/1Gbps
  • 架构:KVM
  • IP/面板:1IPv4/SolusVM
  • 价格:$99/年购买链接
  • CPU:3cores
  • 内存:8GB
  • 硬盘:150GB
  • 流量:10TB/1Gbps
  • 架构:KVM
  • IP/面板:1IPv4/SolusVM
  • 价格:$219/年购买链接

可用促销套餐

CPU 内存 硬盘 流量 IPv4 系统 价格
单核 1GB 20GB 2TB/1Gbps 1个 $11.95/年
双核 1.5GB 20GB 4TB/1Gbps 1个 $16.5/年
双核 2GB 20GB 4TB/1Gbps 1个 $18.88/年
双核 2GB 50GB 4TB/1Gbps 1个 $19.95/年
双核 3GB 32GB 4TB/1Gbps 1个 $24.68/年
三核 2.5GB 40GB 6.5TB/1Gbps 1个 $25.8/年
三核 3GB 45GB 6TB/1Gbps 1个 $31.5/年
三核 4GB 55GB 8TB/1Gbps 1个 $33.25/年
四核 4.5GB 60GB 8TB/1Gbps 1个 $55.89/年
   测试IP:192.210.207.88(圣何塞) 192.3.81.88(纽约) 23.94.101.88(荷兰) 107.173.164.160(亚特兰大)
204.13.154.3(洛杉矶DC02)   198.23.249.100(达拉斯)   198.23.228.15(芝加哥)

上述主机为当前在售的促销套餐,均为年付,价格方面有一定优势。RackNerd是一家成立于2019年的国外VPS主机商,提供包括虚拟主机、VPS、Hybrid Dedicated Servers和独立服务器租用等产品,数据中心在美国洛杉矶、达拉斯、圣何塞、纽约、芝加哥和荷兰阿姆斯特丹等。

标签: 洛杉矶VPS, KVM, 洛杉矶MC, 圣何塞VPS, RackNerd, RackNerd怎么样, RackNerd怎么用

V5.NET全场新客户首单7折,香港服务器月付385港元起

作者:VPSok 发布时间:2021年02月26日 分类:VPS优惠动态 No Comments

V5.NET是一家专业提供独立服务器租用商家,主要提供中国香港、台湾、日本等地区独立服务器租用业务,自有产权硬件,线路到中国大陆方向优化,是远端办公、跨境贸易及网站建设不错的选择。本月商家针对新客户首单优惠继续有效,用户的第一个订单产品可以享永久7折,譬如香港一区阿里云CN2线路E5 CPU机器优惠后最低仅385港元(≈324元人民币)起。

 

香港一区 - HKAli-A1

CPU:Intel E5-2630L 六核十二线程

内存:4GB ECC

硬盘:240GB SSD

带宽:5Mbps  阿里云专线CN2

IPv4:1个

价格:385港元/月

【Order】购买链接

 

香港二区 - HKTW-A1

CPU:Intel E5-2630L 六核十二线程

内存:8GB ECC

硬盘:240GB SSD

带宽:5Mbps  BGP+CN2

IPv4:1个

价格:385港元/月

【Order】购买链接

 

香港三区 - HKTPM-A1

CPU:Intel E3-1230 四核八线程

内存:4GB ECC

硬盘:120GB SSD

带宽:5Mbps  BGP+CN2

IPv4:5个

价格:455港元/月

【Order】购买链接

 

日本国际区 - JPOSA-A1

CPU:Intel E3-1230L 四核八线程

内存:8GB ECC

硬盘:240GB SSD

带宽:5Mbps  BGP+软银

IPv4:5个

价格:525港元/月

【Order】购买链接

 

台湾亚太区 - TWN-A1

CPU:Intel E5-2650 八核十六线程

内存:8GB ECC

硬盘:240GB SSD

带宽:5Mbps  BGP+CN2

IPv4:1个

价格:490港元/月

【Order】购买链接

   优惠码:new(新客7折)   10off(全场9折)
测速连接:
香港一区:http://hk1.speedtest.v5.net:8080/
香港二区:http://hk2.speedtest.v5.net:8080/
香港三区:http://hk3.speedtest.v5.net/
日本国际:http://jp.speedtest.v5.net/
台湾亚太:http://tw.speedtest.v5.net/

以上优惠码均为终身折扣,续费同价,新客户首单7折只可以使用一次,后续复购的话可使用9折优惠码,主机支持安装Linux或者Windows操作系统,一般工作时间内可快速上架,用户可以在产品管理页面对主机进行基本开关机、重启及自助重装等。

标签: 台湾服务器, 香港服务器, 日本服务器, 香港CN2, 香港阿里云, V5.NET, V5.NET优惠码, 台湾CN2

Gcore(gcorelabs)日本VPS简单测试

作者:VPSok 发布时间:2021年02月25日 分类:VPS优惠动态 No Comments

之聚分享过几次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

标签: KVM, 日本VPS, Gcore, gcorelabs, 日本VPS测试, gcorelabs怎么样, gcorelabs日本VPS, gcorelabs测试, gcorelabs评测

Gcore(gcorelabs)俄罗斯伯力VPS简单测试

作者:VPSok 发布时间:2021年02月25日 分类:VPS优惠动态 No Comments

上一篇分享了Gcore(gcorelabs)的日本VPS简单测试信息,这一次我们再来看看俄罗斯伯力机房,同样是基于KVM架构,但是这次我选择下单的配置和价格更低,为最近分享过的最低1.08欧元/月的488M内存款,同样做一个简单的测试贴出信息以便大家参考,这个套餐配置比较低,大家可以主要关注线路。gcorelabs提供的产品机房非常多,我将分批慢慢将比较感兴趣的部分机房最低套餐都下单测试下,对这家有兴趣的可以留意。

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

机房及配置

本文所述VPS为俄罗斯伯力机房(Khabarovsk),配置为1核心CPU 488MB内存 8GB硬盘 188M带宽=€1.08/月,操作系统同样为CentOS7.9

gcore-kh-1

基本信息

商家所有机房VPS均提供了一样的vmmanager面板,独立控制,产品信息邮件中有面板信息,也可以通过会员中心来一键登陆到面板,面板提供了VPS主机所有的常用管理功能,这里就不再贴图。

IO和带宽信息

这里采用了2个不同的一键命令,所以贴出2条命令的结果。

gcore-kh-get

两个测试结果差距不大,可以结合来看,相对于上一次测试的日本VPS来说IO低了一些,但是带宽高了很多,考虑到这个套餐本身的配置和价格也算是物有所值。

gcore-kh-get2

去程路由

同样在国内电信、联通和移动网络访问VPS来查看线路情况。

gcore-kh-from-shdx

gcore-kh-from-scdx

gcore-kh-from-szdx

从上面三个地区电信来看,总体线路一致,起点→北京→天津→俄罗斯,实际上我还在更多区域电信测试也一样,比较稳;联通也是如此,下面是联通测试结果。

gcore-kh-from-hnlt

gcore-kh-from-lnlt

gcore-kh-from-shlt

无论是电信还是联通,线路都非常稳定,各个地区都一样。移动宽带测试去程路线也比较一致,但是相对于电信联通来说就比较差了,均从起点到北京,然后到德国再到俄罗斯,绕了一个圈子。

gcore-kh-from-szyd

回程路由

回程测试在主机中运行脚本,与去程一样,整体来说电信、联通线路较好,移动不推荐。

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.131.1  0.69 ms  http: json  http: json
 2  10.255.10.181  1.42 ms  http: json  http: json
 3  10.255.10.178  0.24 ms  http: json  http: json
 4  10.255.10.160  1.34 ms  http: json  http: json
 5  188.254.90.105  0.35 ms  http: json  http: json
 6  95.167.20.254  44.48 ms  http: json  http: json
 7  219.158.16.81  57.01 ms  http: json  http: json
 8  219.158.16.81  53.44 ms  http: json  http: json
 9  219.158.18.69  76.20 ms  http: json  http: json
10  *
11  61.148.159.30  86.06 ms  http: json  http: json
12  124.65.194.42  80.24 ms  http: json  http: json
13  *
15  *
16  123.125.99.1  80.80 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.131.1  0.23 ms  http: json  http: json
 2  10.255.10.182  0.25 ms  http: json  http: json
 3  10.255.10.178  0.31 ms  http: json  http: json
 4  10.255.10.161  0.39 ms  http: json  http: json
 5  81.173.24.2  58.94 ms  http: json  http: json
 6  81.173.24.13  59.31 ms  http: json  http: json
 7  81.173.24.9  59.20 ms  http: json  http: json
 8  202.97.30.229  54.72 ms  http: json  http: json
 9  202.97.12.53  59.65 ms  http: json  http: json
10  *
11  180.149.128.9  73.90 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.131.1  0.24 ms  http: json  http: json
 2  10.255.10.181  0.84 ms  http: json  http: json
 3  10.255.10.177  0.26 ms  http: json  http: json
 4  78.25.77.164  0.64 ms  http: json  http: json
 5  83.169.204.50  141.96 ms  http: json  http: json
 6  80.81.195.121  139.65 ms  http: json  http: json
 7  223.120.10.41  142.08 ms  http: json  http: json
 8  *
16  *
17  211.136.95.226  285.01 ms  http: json  http: json
18  211.136.95.226  285.78 ms  http: json  http: json
19  *
20  211.136.25.153  386.78 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.131.1  0.29 ms  http: json  http: json
 2  10.255.10.181  0.21 ms  http: json  http: json
 3  10.255.10.178  0.42 ms  http: json  http: json
 4  188.254.90.105  0.41 ms  http: json  http: json
 5  188.254.90.105  0.80 ms  http: json  http: json
 6  188.128.15.214  41.20 ms  http: json  http: json
 7  219.158.16.81  53.32 ms  http: json  http: json
 8  219.158.16.81  50.26 ms  http: json  http: json
 9  219.158.16.86  105.21 ms  http: json  http: json
10  *
11  58.247.221.178  105.93 ms  http: json  http: json
12  139.226.225.22  104.73 ms  http: json  http: json
13  58.247.8.153  110.19 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.131.1  0.39 ms  http: json  http: json
 2  10.255.10.182  0.23 ms  http: json  http: json
 3  10.255.10.177  0.35 ms  http: json  http: json
 4  10.255.10.161  23.54 ms  http: json  http: json
 5  217.150.56.138  2.19 ms  http: json  http: json
 6  81.173.24.9  60.21 ms  http: json  http: json
 7  202.97.30.225  79.88 ms  http: json  http: json
 8  202.97.30.225  73.39 ms  http: json  http: json
 9  *
12  *
13  124.74.166.14  92.53 ms  http: json  http: json
14  101.227.255.34  87.97 ms  http: json  http: json
15  180.153.28.5  87.65 ms  http: json  http: json


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.131.1  0.21 ms  http: json  http: json
 2  10.255.10.182  0.59 ms  http: json  http: json
 3  10.255.10.178  3.39 ms  http: json  http: json
 4  10.255.10.161  0.33 ms  http: json  http: json
 5  78.25.77.164  11.08 ms  http: json  http: json
 6  80.81.195.121  151.21 ms  http: json  http: json
 7  223.120.10.41  141.69 ms  http: json  http: json
 8  223.120.10.41  141.69 ms  http: json  http: json
 9  *
10  221.183.55.22  394.99 ms  http: json  http: json


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.131.1  0.24 ms  http: json  http: json
 2  10.255.10.181  0.26 ms  http: json  http: json
 3  10.255.10.177  0.30 ms  http: json  http: json
 4  188.254.90.105  6.62 ms  http: json  http: json
 5  188.254.90.105  6.18 ms  http: json  http: json
 6  188.128.106.113  0.95 ms  http: json  http: json
 7  219.158.3.177  57.15 ms  http: json  http: json
 8  219.158.3.177  55.17 ms  http: json  http: json
 9  219.158.5.153  110.41 ms  http: json  http: json
10  219.158.8.82  141.36 ms  http: json  http: json
11  120.83.0.58  141.87 ms  http: json  http: json
12  120.80.175.70  134.59 ms  http: json  http: json

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.131.1  0.47 ms  http: json  http: json
 2  10.255.10.182  0.51 ms  http: json  http: json
 3  10.255.10.178  0.26 ms  http: json  http: json
 4  217.150.56.138  0.98 ms  http: json  http: json
 5  *
 6  81.173.24.13  60.48 ms  http: json  http: json
 7  202.97.30.225  73.45 ms  http: json  http: json
 8  202.97.81.137  63.05 ms  http: json  http: json
 9  202.97.53.73  78.04 ms  http: json  http: json
10  202.97.65.50  100.48 ms  http: json  http: json
11  202.97.65.50  121.33 ms  http: json  http: json
12  113.108.209.1  102.19 ms  http: json  http: json


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.131.1  0.23 ms  http: json  http: json
 2  10.255.10.182  0.29 ms  http: json  http: json
 3  10.255.10.178  0.27 ms  http: json  http: json
 4  10.255.10.161  2.47 ms  http: json  http: json
 5  83.169.204.58  141.88 ms  http: json  http: json
 6  80.81.195.121  140.02 ms  http: json  http: json
 7  223.120.10.85  144.54 ms  http: json  http: json
 8  223.120.10.85  144.89 ms  http: json  http: json
 9  *
10  *
11  221.183.55.62  411.69 ms  http: json  http: json
12  221.183.52.85  480.28 ms  http: json  http: json
13  111.24.4.253  408.61 ms  http: json  http: json
14  111.24.14.86  369.94 ms  http: json  http: json
15  211.136.249.93  417.43 ms  http: json  http: json
16  211.139.180.106  464.90 ms  http: json  http: json
17  211.136.249.17  366.69 ms  http: json  http: json
18  *
19  120.196.212.25  469.21 ms  http: json  http: json


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.131.1  0.19 ms  http: json  http: json
 2  10.255.10.182  0.23 ms  http: json  http: json
 3  10.255.10.178  0.49 ms  http: json  http: json
 4  10.255.10.161  0.28 ms  http: json  http: json
 5  217.150.56.138  0.84 ms  http: json  http: json
 6  149.6.168.201  114.65 ms  http: json  http: json
 7  154.25.12.77  141.99 ms  http: json  http: json
 8  154.54.61.241  125.23 ms  http: json  http: json
 9  149.11.84.106  199.07 ms  http: json  http: json
10  154.54.58.225  136.14 ms  http: json  http: json
11  154.54.37.30  140.04 ms  http: json  http: json
12  218.105.2.198  195.69 ms  http: json  http: json
13  154.25.12.77  141.21 ms  http: json  http: json
14  210.13.66.238  208.27 ms  http: json  http: json


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.131.1  0.48 ms  http: json  http: json
 2  10.255.10.182  0.24 ms  http: json  http: json
 3  10.255.10.177  0.42 ms  http: json  http: json
 4  10.255.10.161  0.65 ms  http: json  http: json
 5  213.248.99.222  485.02 ms  http: json  http: json
 6  213.248.99.222  141.33 ms  http: json  http: json
 7  213.248.99.221  112.37 ms  http: json  http: json
 8  62.115.136.80  143.22 ms  http: json  http: json
 9  62.115.122.161  148.36 ms  http: json  http: json
10  80.91.249.10  155.03 ms  http: json  http: json
11  80.239.193.226  139.20 ms  http: json  http: json
12  *
15  *
16  58.32.0.1  217.05 ms  http: json  http: json


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.131.1  0.22 ms  http: json  http: json
 2  10.255.10.182  0.24 ms  http: json  http: json
 3  10.255.10.178  0.26 ms  http: json  http: json
 4  188.254.90.105  1.38 ms  http: json  http: json
 5  213.248.99.222  494.77 ms  http: json  http: json
 6  63.217.237.29  72.15 ms  http: json  http: json
 7  63.223.17.50  72.42 ms  http: json  http: json
 8  63.216.143.46  92.86 ms  http: json  http: json
 9  *
10  62.115.122.189  148.77 ms  http: json  http: json
11  80.239.193.226  140.40 ms  http: json  http: json
12  *
13  *
14  119.121.0.1  83.35 ms  http: json  http: json


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.131.1  0.67 ms  http: json  http: json
 2  10.255.10.181  0.23 ms  http: 503  http: 503
 3  10.255.10.177  1.81 ms  http: json  http: json
 4  188.254.90.105  0.36 ms  http: 503  http: 503
 5  188.128.106.115  1.02 ms  http: 503  http: 503
 6  188.128.106.115  0.99 ms  http: 503  http: 503
 7  219.158.3.141  53.83 ms  http: 503  http: 503
 8  219.158.5.149  109.01 ms  http: 503  http: 503
 9  219.158.5.149  106.48 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.131.1  0.34 ms  http: 503  http: 503
 2  10.255.10.181  0.25 ms  http: 503  http: 503
 3  10.255.10.178  0.22 ms  http: 503  http: 503
 4  188.254.90.105  0.50 ms  http: 503  http: 503
 5  188.254.90.105  7.47 ms  http: 503  http: 503
 6  188.128.106.113  1.06 ms  http: 503  http: 503
 7  188.128.15.214  39.60 ms  http: 503  http: 503
 8  219.158.3.133  53.81 ms  http: 503  http: 503
 9  61.149.203.46  88.87 ms  http: 503  http: 503
10  *
11  202.96.13.114  88.07 ms  http: 503  http: 503
12  218.241.244.22  87.22 ms  http: 503  http: 503
13  218.241.244.22  87.47 ms  http: 503  http: 503
14  124.205.97.138  88.59 ms  http: 503  http: 503
15  218.241.253.130  87.10 ms  http: 503  http: 503
16  *
17  211.167.230.100  87.33 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.131.1  1.39 ms  http: 503  http: 503
 2  10.255.10.182  0.21 ms  http: 503  http: 503
 3  10.255.10.177  0.19 ms  http: 503  http: 503
 4  10.255.10.161  0.27 ms  http: 503  http: 503
 5  212.188.2.57  9.58 ms  http: 503  http: 503
 6  195.34.59.248  69.89 ms  http: 503  http: 503
 7  123.255.91.118  76.31 ms  http: 503  http: 503
 8  *
 9  101.4.114.181  119.54 ms  http: 503  http: 503
10  101.4.114.58  112.52 ms  http: 503  http: 503
11  101.4.114.58  115.03 ms  http: 503  http: 503
12  101.4.116.81  110.17 ms  http: 503  http: 503
13  202.112.38.158  110.83 ms  http: 503  http: 503
14  202.112.38.158  110.60 ms  http: 503  http: 503
15  202.205.109.205  111.25 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.131.1  0.31 ms  http: 503  http: 503
 2  10.255.10.181  1.77 ms  http: 503  http: 503
 3  10.255.10.177  0.22 ms  http: 503  http: 503
 4  217.150.56.138  0.84 ms  http: 503  http: 503
 5  95.167.95.111  73.27 ms  http: 503  http: 503
 6  63.217.237.29  75.21 ms  http: 503  http: 503
 7  63.223.17.94  74.58 ms  http: 503  http: 503
 8  63.223.17.94  76.07 ms  http: 503  http: 503
 9  159.226.254.5  105.53 ms  http: 503  http: 503
10  159.226.254.1  108.49 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.131.1  0.22 ms  http: 503  http: 503
 2  10.255.10.181  0.27 ms  http: 503  http: 503
 3  10.255.10.178  1.25 ms  http: 503  http: 503
 4  217.150.56.138  1.08 ms  http: 503  http: 503
 5  217.150.56.138  0.92 ms  http: 503  http: 503
 6  81.173.24.2  58.96 ms  http: 503  http: 503
 7  202.97.30.225  74.31 ms  http: 503  http: 503
 8  202.97.12.49  59.41 ms  http: 503  http: 503
 9  *
10  219.141.147.229  86.90 ms  http: 503  http: 503
11  219.141.147.229  67.45 ms  http: 503  http: 503
12  60.247.93.254  65.13 ms  http: 503  http: 503
13  60.247.93.254  67.58 ms  http: 503  http: 503
14  211.156.128.198  87.66 ms  http: 503  http: 503
15  211.156.128.85  64.33 ms  http: 503  http: 503
16  *
17  211.156.140.17  69.32 ms  http: 503  http: 503

Ping测试

也是用IPIP.NET在全国和亚太地区测试结果,国内延迟电信/联通优秀,移动较高。

gcore-kh-ping

标签: KVM, 俄罗斯VPS, Gcore, gcorelabs, 伯力vps, gcorelabs怎么样, gcorelabs测试, gcorelabs评测, gcorelabs伯力VPS

Gcore(gcorelabs)俄罗斯伯力VPS简单测试

作者:VPSok 发布时间:2021年02月25日 分类:VPS评测 No Comments

上一篇分享了Gcore(gcorelabs)的日本VPS简单测试信息,这一次我们再来看看俄罗斯伯力机房,同样是基于KVM架构,但是这次我选择下单的配置和价格更低,为最近分享过的最低1.08欧元/月的488M内存款,同样做一个简单的测试贴出信息以便大家参考,这个套餐配置比较低,大家可以主要关注线路。gcorelabs提供的产品机房非常多,我将分批慢慢将比较感兴趣的部分机房最低套餐都下单测试下,对这家有兴趣的可以留意。

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

机房及配置

本文所述VPS为俄罗斯伯力机房(Khabarovsk),配置为1核心CPU+488MB内存+8GB硬盘+188M带宽=€1.08/月,操作系统同样为CentOS7.9

gcore-kh-1

基本信息

商家所有机房VPS均提供了一样的vmmanager面板,独立控制,产品信息邮件中有面板信息,也可以通过会员中心来一键登陆到面板,面板提供了VPS主机所有的常用管理功能,这里就不再贴图。

IO和带宽信息

这里采用了2个不同的一键命令,所以贴出2条命令的结果。

gcore-kh-get

两个测试结果差距不大,可以结合来看,相对于上一次测试的日本VPS来说IO低了一些,但是带宽高了很多,考虑到这个套餐本身的配置和价格也算是物有所值。

gcore-kh-get2

去程路由

同样在国内电信、联通和移动网络访问VPS来查看线路情况。

gcore-kh-from-shdx

gcore-kh-from-scdx

gcore-kh-from-szdx

从上面三个地区电信来看,总体线路一致,起点→北京→天津→俄罗斯,实际上我还在更多区域电信测试也一样,比较稳;联通也是如此,下面是联通测试结果。

gcore-kh-from-hnlt

gcore-kh-from-lnlt

gcore-kh-from-shlt

无论是电信还是联通,线路都非常稳定,各个地区都一样。移动宽带测试去程路线也比较一致,但是相对于电信联通来说就比较差了,均从起点到北京,然后到德国再到俄罗斯,绕了一个圈子。

gcore-kh-from-szyd

回程路由

回程测试在主机中运行脚本,与去程一样,整体来说电信、联通线路较好,移动不推荐。

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.131.1  0.69 ms  http: json  http: json
 2  10.255.10.181  1.42 ms  http: json  http: json
 3  10.255.10.178  0.24 ms  http: json  http: json
 4  10.255.10.160  1.34 ms  http: json  http: json
 5  188.254.90.105  0.35 ms  http: json  http: json
 6  95.167.20.254  44.48 ms  http: json  http: json
 7  219.158.16.81  57.01 ms  http: json  http: json
 8  219.158.16.81  53.44 ms  http: json  http: json
 9  219.158.18.69  76.20 ms  http: json  http: json
10  *
11  61.148.159.30  86.06 ms  http: json  http: json
12  124.65.194.42  80.24 ms  http: json  http: json
13  *
15  *
16  123.125.99.1  80.80 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.131.1  0.23 ms  http: json  http: json
 2  10.255.10.182  0.25 ms  http: json  http: json
 3  10.255.10.178  0.31 ms  http: json  http: json
 4  10.255.10.161  0.39 ms  http: json  http: json
 5  81.173.24.2  58.94 ms  http: json  http: json
 6  81.173.24.13  59.31 ms  http: json  http: json
 7  81.173.24.9  59.20 ms  http: json  http: json
 8  202.97.30.229  54.72 ms  http: json  http: json
 9  202.97.12.53  59.65 ms  http: json  http: json
10  *
11  180.149.128.9  73.90 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.131.1  0.24 ms  http: json  http: json
 2  10.255.10.181  0.84 ms  http: json  http: json
 3  10.255.10.177  0.26 ms  http: json  http: json
 4  78.25.77.164  0.64 ms  http: json  http: json
 5  83.169.204.50  141.96 ms  http: json  http: json
 6  80.81.195.121  139.65 ms  http: json  http: json
 7  223.120.10.41  142.08 ms  http: json  http: json
 8  *
16  *
17  211.136.95.226  285.01 ms  http: json  http: json
18  211.136.95.226  285.78 ms  http: json  http: json
19  *
20  211.136.25.153  386.78 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.131.1  0.29 ms  http: json  http: json
 2  10.255.10.181  0.21 ms  http: json  http: json
 3  10.255.10.178  0.42 ms  http: json  http: json
 4  188.254.90.105  0.41 ms  http: json  http: json
 5  188.254.90.105  0.80 ms  http: json  http: json
 6  188.128.15.214  41.20 ms  http: json  http: json
 7  219.158.16.81  53.32 ms  http: json  http: json
 8  219.158.16.81  50.26 ms  http: json  http: json
 9  219.158.16.86  105.21 ms  http: json  http: json
10  *
11  58.247.221.178  105.93 ms  http: json  http: json
12  139.226.225.22  104.73 ms  http: json  http: json
13  58.247.8.153  110.19 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.131.1  0.39 ms  http: json  http: json
 2  10.255.10.182  0.23 ms  http: json  http: json
 3  10.255.10.177  0.35 ms  http: json  http: json
 4  10.255.10.161  23.54 ms  http: json  http: json
 5  217.150.56.138  2.19 ms  http: json  http: json
 6  81.173.24.9  60.21 ms  http: json  http: json
 7  202.97.30.225  79.88 ms  http: json  http: json
 8  202.97.30.225  73.39 ms  http: json  http: json
 9  *
12  *
13  124.74.166.14  92.53 ms  http: json  http: json
14  101.227.255.34  87.97 ms  http: json  http: json
15  180.153.28.5  87.65 ms  http: json  http: json


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.131.1  0.21 ms  http: json  http: json
 2  10.255.10.182  0.59 ms  http: json  http: json
 3  10.255.10.178  3.39 ms  http: json  http: json
 4  10.255.10.161  0.33 ms  http: json  http: json
 5  78.25.77.164  11.08 ms  http: json  http: json
 6  80.81.195.121  151.21 ms  http: json  http: json
 7  223.120.10.41  141.69 ms  http: json  http: json
 8  223.120.10.41  141.69 ms  http: json  http: json
 9  *
10  221.183.55.22  394.99 ms  http: json  http: json


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.131.1  0.24 ms  http: json  http: json
 2  10.255.10.181  0.26 ms  http: json  http: json
 3  10.255.10.177  0.30 ms  http: json  http: json
 4  188.254.90.105  6.62 ms  http: json  http: json
 5  188.254.90.105  6.18 ms  http: json  http: json
 6  188.128.106.113  0.95 ms  http: json  http: json
 7  219.158.3.177  57.15 ms  http: json  http: json
 8  219.158.3.177  55.17 ms  http: json  http: json
 9  219.158.5.153  110.41 ms  http: json  http: json
10  219.158.8.82  141.36 ms  http: json  http: json
11  120.83.0.58  141.87 ms  http: json  http: json
12  120.80.175.70  134.59 ms  http: json  http: json

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.131.1  0.47 ms  http: json  http: json
 2  10.255.10.182  0.51 ms  http: json  http: json
 3  10.255.10.178  0.26 ms  http: json  http: json
 4  217.150.56.138  0.98 ms  http: json  http: json
 5  *
 6  81.173.24.13  60.48 ms  http: json  http: json
 7  202.97.30.225  73.45 ms  http: json  http: json
 8  202.97.81.137  63.05 ms  http: json  http: json
 9  202.97.53.73  78.04 ms  http: json  http: json
10  202.97.65.50  100.48 ms  http: json  http: json
11  202.97.65.50  121.33 ms  http: json  http: json
12  113.108.209.1  102.19 ms  http: json  http: json


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.131.1  0.23 ms  http: json  http: json
 2  10.255.10.182  0.29 ms  http: json  http: json
 3  10.255.10.178  0.27 ms  http: json  http: json
 4  10.255.10.161  2.47 ms  http: json  http: json
 5  83.169.204.58  141.88 ms  http: json  http: json
 6  80.81.195.121  140.02 ms  http: json  http: json
 7  223.120.10.85  144.54 ms  http: json  http: json
 8  223.120.10.85  144.89 ms  http: json  http: json
 9  *
10  *
11  221.183.55.62  411.69 ms  http: json  http: json
12  221.183.52.85  480.28 ms  http: json  http: json
13  111.24.4.253  408.61 ms  http: json  http: json
14  111.24.14.86  369.94 ms  http: json  http: json
15  211.136.249.93  417.43 ms  http: json  http: json
16  211.139.180.106  464.90 ms  http: json  http: json
17  211.136.249.17  366.69 ms  http: json  http: json
18  *
19  120.196.212.25  469.21 ms  http: json  http: json


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.131.1  0.19 ms  http: json  http: json
 2  10.255.10.182  0.23 ms  http: json  http: json
 3  10.255.10.178  0.49 ms  http: json  http: json
 4  10.255.10.161  0.28 ms  http: json  http: json
 5  217.150.56.138  0.84 ms  http: json  http: json
 6  149.6.168.201  114.65 ms  http: json  http: json
 7  154.25.12.77  141.99 ms  http: json  http: json
 8  154.54.61.241  125.23 ms  http: json  http: json
 9  149.11.84.106  199.07 ms  http: json  http: json
10  154.54.58.225  136.14 ms  http: json  http: json
11  154.54.37.30  140.04 ms  http: json  http: json
12  218.105.2.198  195.69 ms  http: json  http: json
13  154.25.12.77  141.21 ms  http: json  http: json
14  210.13.66.238  208.27 ms  http: json  http: json


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.131.1  0.48 ms  http: json  http: json
 2  10.255.10.182  0.24 ms  http: json  http: json
 3  10.255.10.177  0.42 ms  http: json  http: json
 4  10.255.10.161  0.65 ms  http: json  http: json
 5  213.248.99.222  485.02 ms  http: json  http: json
 6  213.248.99.222  141.33 ms  http: json  http: json
 7  213.248.99.221  112.37 ms  http: json  http: json
 8  62.115.136.80  143.22 ms  http: json  http: json
 9  62.115.122.161  148.36 ms  http: json  http: json
10  80.91.249.10  155.03 ms  http: json  http: json
11  80.239.193.226  139.20 ms  http: json  http: json
12  *
15  *
16  58.32.0.1  217.05 ms  http: json  http: json


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.131.1  0.22 ms  http: json  http: json
 2  10.255.10.182  0.24 ms  http: json  http: json
 3  10.255.10.178  0.26 ms  http: json  http: json
 4  188.254.90.105  1.38 ms  http: json  http: json
 5  213.248.99.222  494.77 ms  http: json  http: json
 6  63.217.237.29  72.15 ms  http: json  http: json
 7  63.223.17.50  72.42 ms  http: json  http: json
 8  63.216.143.46  92.86 ms  http: json  http: json
 9  *
10  62.115.122.189  148.77 ms  http: json  http: json
11  80.239.193.226  140.40 ms  http: json  http: json
12  *
13  *
14  119.121.0.1  83.35 ms  http: json  http: json


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.131.1  0.67 ms  http: json  http: json
 2  10.255.10.181  0.23 ms  http: 503  http: 503
 3  10.255.10.177  1.81 ms  http: json  http: json
 4  188.254.90.105  0.36 ms  http: 503  http: 503
 5  188.128.106.115  1.02 ms  http: 503  http: 503
 6  188.128.106.115  0.99 ms  http: 503  http: 503
 7  219.158.3.141  53.83 ms  http: 503  http: 503
 8  219.158.5.149  109.01 ms  http: 503  http: 503
 9  219.158.5.149  106.48 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.131.1  0.34 ms  http: 503  http: 503
 2  10.255.10.181  0.25 ms  http: 503  http: 503
 3  10.255.10.178  0.22 ms  http: 503  http: 503
 4  188.254.90.105  0.50 ms  http: 503  http: 503
 5  188.254.90.105  7.47 ms  http: 503  http: 503
 6  188.128.106.113  1.06 ms  http: 503  http: 503
 7  188.128.15.214  39.60 ms  http: 503  http: 503
 8  219.158.3.133  53.81 ms  http: 503  http: 503
 9  61.149.203.46  88.87 ms  http: 503  http: 503
10  *
11  202.96.13.114  88.07 ms  http: 503  http: 503
12  218.241.244.22  87.22 ms  http: 503  http: 503
13  218.241.244.22  87.47 ms  http: 503  http: 503
14  124.205.97.138  88.59 ms  http: 503  http: 503
15  218.241.253.130  87.10 ms  http: 503  http: 503
16  *
17  211.167.230.100  87.33 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.131.1  1.39 ms  http: 503  http: 503
 2  10.255.10.182  0.21 ms  http: 503  http: 503
 3  10.255.10.177  0.19 ms  http: 503  http: 503
 4  10.255.10.161  0.27 ms  http: 503  http: 503
 5  212.188.2.57  9.58 ms  http: 503  http: 503
 6  195.34.59.248  69.89 ms  http: 503  http: 503
 7  123.255.91.118  76.31 ms  http: 503  http: 503
 8  *
 9  101.4.114.181  119.54 ms  http: 503  http: 503
10  101.4.114.58  112.52 ms  http: 503  http: 503
11  101.4.114.58  115.03 ms  http: 503  http: 503
12  101.4.116.81  110.17 ms  http: 503  http: 503
13  202.112.38.158  110.83 ms  http: 503  http: 503
14  202.112.38.158  110.60 ms  http: 503  http: 503
15  202.205.109.205  111.25 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.131.1  0.31 ms  http: 503  http: 503
 2  10.255.10.181  1.77 ms  http: 503  http: 503
 3  10.255.10.177  0.22 ms  http: 503  http: 503
 4  217.150.56.138  0.84 ms  http: 503  http: 503
 5  95.167.95.111  73.27 ms  http: 503  http: 503
 6  63.217.237.29  75.21 ms  http: 503  http: 503
 7  63.223.17.94  74.58 ms  http: 503  http: 503
 8  63.223.17.94  76.07 ms  http: 503  http: 503
 9  159.226.254.5  105.53 ms  http: 503  http: 503
10  159.226.254.1  108.49 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.131.1  0.22 ms  http: 503  http: 503
 2  10.255.10.181  0.27 ms  http: 503  http: 503
 3  10.255.10.178  1.25 ms  http: 503  http: 503
 4  217.150.56.138  1.08 ms  http: 503  http: 503
 5  217.150.56.138  0.92 ms  http: 503  http: 503
 6  81.173.24.2  58.96 ms  http: 503  http: 503
 7  202.97.30.225  74.31 ms  http: 503  http: 503
 8  202.97.12.49  59.41 ms  http: 503  http: 503
 9  *
10  219.141.147.229  86.90 ms  http: 503  http: 503
11  219.141.147.229  67.45 ms  http: 503  http: 503
12  60.247.93.254  65.13 ms  http: 503  http: 503
13  60.247.93.254  67.58 ms  http: 503  http: 503
14  211.156.128.198  87.66 ms  http: 503  http: 503
15  211.156.128.85  64.33 ms  http: 503  http: 503
16  *
17  211.156.140.17  69.32 ms  http: 503  http: 503

Ping测试

也是用IPIP.NET在全国和亚太地区测试结果,国内延迟电信/联通优秀,移动较高。

gcore-kh-ping

 

总的来说,伯力机房在国内访问线路质量还是不错的,电信/联通用户推荐,但是移动宽带用户请尽量考虑其他区域,毕竟商家有30多个机房可选(比如新加坡/中国香港等),可以直接在官网查看测试IP信息:https://gcorelabs.com

标签: KVM, 俄罗斯VPS, Gcore, gcorelabs, 伯力vps, gcorelabs怎么样, gcorelabs测试, gcorelabs评测, gcorelabs伯力VPS

Gcore(gcorelabs)日本VPS简单测试

作者:VPSok 发布时间:2021年02月25日 分类:VPS评测 No Comments

之聚分享过几次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

标签: KVM, 日本VPS, Gcore, gcorelabs, 日本VPS测试, gcorelabs怎么样, gcorelabs日本VPS, gcorelabs测试, gcorelabs评测

DiyVM:香港/日本/美国VPS低至5折,2G内存套餐月付69元起

作者:VPSok 发布时间:2021年02月24日 分类:VPS优惠动态 No Comments

好久没有分享过DiyVM的信息了,这是一家成立于2009年的国人主机商,提供VPS主机、独立服务器和香港高防IP租用等,产品数据中心包括日本大阪、香港沙田和美国洛杉矶等,其中VPS主机基于XEN架构,香港和洛杉矶机房为CN2线路,日本国内直连,主机均可提供内网IP功能,支持异地备份与自定义镜像。商家针对VPS提供5折到6.9折优惠码,最低配置2G内存起步每月69元起。

下面列出部分套餐配置信息,不同地区的VPS除了带宽不同,其他配置和价格是一样的。

洛杉矶VPS

  • CPU:2cores
  • 内存:2GB
  • 硬盘:50GB/RAID10
  • 带宽:8M无限
  • 架构:XEN
  • IP/面板:1IPv4/Xensystem
  • 优惠码:FEB
  • 价格:69元/月购买链接
  • CPU:4cores
  • 内存:4GB
  • 硬盘:60GB/RAID10
  • 带宽:10M无限
  • 架构:XEN
  • IP/面板:1IPv4/Xensystem
  • 优惠码:OFF50
  • 价格:100元/月购买链接
  • CPU:4cores
  • 内存:8GB
  • 硬盘:70GB/RAID10
  • 带宽:15M无限
  • 架构:XEN
  • IP/面板:4IPv4/Xensystem
  • 优惠码:OFF50
  • 价格:200元/月购买链接

香港VPS

  • CPU:2cores
  • 内存:2GB
  • 硬盘:50GB/RAID10
  • 带宽:2M无限
  • 架构:XEN
  • IP/面板:1IPv4/Xensystem
  • 优惠码:FEB
  • 价格:69元/月购买链接
  • CPU:4cores
  • 内存:4GB
  • 硬盘:60GB/RAID10
  • 带宽:3M无限
  • 架构:XEN
  • IP/面板:1IPv4/Xensystem
  • 优惠码:OFF50
  • 价格:100元/月购买链接
  • CPU:4cores
  • 内存:8GB
  • 硬盘:70GB/RAID10
  • 带宽:3M无限
  • 架构:XEN
  • IP/面板:4IPv4/Xensystem
  • 优惠码:OFF50
  • 价格:200元/月购买链接

日本VPS

  • CPU:2cores
  • 内存:2GB
  • 硬盘:50GB/RAID10
  • 带宽:5M无限
  • 架构:XEN
  • IP/面板:1IPv4/Xensystem
  • 优惠码:FEB
  • 价格:69元/月购买链接
  • CPU:4cores
  • 内存:4GB
  • 硬盘:60GB/RAID10
  • 带宽:8M无限
  • 架构:XEN
  • IP/面板:1IPv4/Xensystem
  • 优惠码:OFF50
  • 价格:100元/月购买链接
  • CPU:4cores
  • 内存:8GB
  • 硬盘:70GB/RAID10
  • 带宽:10M无限
  • 架构:XEN
  • IP/面板:4IPv4/Xensystem
  • 优惠码:OFF50
  • 价格:200元/月购买链接
   测试IP:154.205.11.2(日本)  118.193.215.249(香港)   103.50.254.130(洛杉矶)

以上优惠码为终身折扣,续费同价,请留意产品列表中的优惠码信息。商家主机支持安装Windows或者Linux操作系统,所有套餐均为限制带宽不限流量的方式,不同套餐和机房的带宽不同。除了VPS外,商家也提供香港独立服务器租用,开设在沙田机房,支持内网IP,最低每月499元起。

  • CPU:L5630*2
  • 内存:16GB
  • 硬盘:120G SSD
  • 带宽:5M
  • IPv4:3个
  • 其他:自助重启/开机/重装
  • 价格:499元/月购买链接
  • CPU:E5-2630L*2
  • 内存:32GB
  • 硬盘:480G SSD
  • 带宽:5M
  • IPv4:3个
  • 其他:自助重启/开机/重装
  • 价格:699元/月购买链接
  • CPU:E5-2630L*2
  • 内存:32GB
  • 硬盘:480G SSD+1TB HDD
  • 带宽:5M
  • IPv4:3个
  • 其他:自助重启/开机/重装
  • 价格:799元/月购买链接

除了以上产品,商家还可购买香港高防IP,可提供100Gbps DDoS防御,演示地址就是商家官网主页,有这方面需求的可以关注下。

标签: XEN, 香港VPS, 日本VPS, DiyVM, 洛杉矶CN2, CN2线路, DiyVM优惠码, 香港CN2, CN2 VPS

ZJI:台湾CN2/香港高主频服务器7折每月595元起,其他全场8折

作者:VPSok 发布时间:2021年02月23日 分类:独立服务器 No Comments

ZJI原名维翔主机,是原来Wordpress圈知名主机商家,成立于2011年,2018年9月更名为ZJI,提供香港、日本、美国独立服务器(自营/数据中心直营)租用及VDS、虚拟主机空间、域名注册业务。ZJI今年全新上架了台湾CN2线路服务器,本月针对香港高主频服务器和台湾CN2服务器提供7折优惠码,其他机房及产品提供8折优惠码,优惠后台湾CN2线路E5服务器月付595元起。

台湾一型

CPU:Intel E5-2650 八核十六线程

内存:16GB ECC

硬盘:480GB SSD

带宽:5Mbps CN2+BGP

IPv4:2个

价格:595元/月(优惠码:tw30off)

订购:点击直达

 

台湾二型

CPU:Intel E5-2650 八核十六线程

内存:32GB ECC

硬盘:480GB SSD

带宽:10Mbps CN2+BGP

IPv4:2个

价格:665元/月(优惠码:tw30off)

订购:点击直达

 

香港阿里五型

CPU:Intel E3-1270v2 四核八线程

内存:32GB ECC

硬盘:1TB SSD

带宽:10Mbps CN2+BGP

IPv4:1个

价格:700元/月(优惠码:3.5Ghz)

订购:点击直达

 

香港葵湾五型

CPU:Intel E5-2637v2 四核八线程

内存:16GB ECC

硬盘:1TB SSD

带宽:10Mbps CN2+BGP

IPv4:2个

价格:700元/月(优惠码:3.5Ghz)

订购:点击直达

 

香港葵湾六型

CPU:Intel E3-1270v2 四核八线程

内存:32GB ECC

硬盘:1TB SSD

带宽:10Mbps CN2+BGP

IPv4:2个

价格:700元/月(优惠码:3.5Ghz )

订购:点击直达

   优惠码:tw30off(台湾适用) 3.5Ghz(香港高主频适用)   zji(全场8折)  
测试地址:
台湾:http://tw.speedtest.zji.net/
香港阿里:http://hkali.speedtest.zji.net:8080/
香港葵湾(普通):http://hkkw.speedtest.zji.net/
香港葵湾(防御):http://hkkwfw.speedtest.zji.net:8080/

商家主机支持安装Linux或者Windows操作系统,提供IPMI,优惠码均为终身折扣,续费同价,除了香港、台湾服务器外,美国洛杉矶、日本、韩国等多个国家和地区机房机器均有在售,可以使用8折优惠码,长期有效可用的。

标签: 美国服务器, 台湾服务器, 香港服务器, 维翔主机, 日本服务器, 香港CN2, ZJI, ZJI优惠码, 台湾CN2

HostKvm开年促销:香港国际/美国洛杉矶VPS七折,其他机房八折

作者:VPSok 发布时间:2021年02月22日 分类:VPS优惠动态 No Comments

HostKvm也发布了开年促销方案,针对香港国际和美国洛杉矶两个机房的VPS主机提供7折优惠码,其他机房业务提供8折优惠码。商家成立于2013年,提供基于KVM架构的VPS主机,可选数据中心包括日本、新加坡、韩国、美国、中国香港等多个地区机房,均为国内直连或优化线路,延迟较低,适合建站或者远程办公等。

下面列出几款主机配置信息。

美国洛杉矶

  • 套餐:美国 US-Plan1
  • CPU:1core
  • 内存:2GB
  • 硬盘:25GB/RAID10
  • 流量:1TB/40Mbps
  • 架构:KVM
  • IP/面板:1IPv4/SolusVM
  • 价格:$6.65/月购买链接
  • 套餐:美国 US-Plan2
  • CPU:2cores
  • 内存:4GB
  • 硬盘:50GB/RAID10
  • 流量:1.5TB/50Mbps
  • 架构:KVM
  • IP/面板:1IPv4/SolusVM
  • 价格:$7.35/月购买链接
  • 套餐:美国 US-Plan3
  • CPU:2cores
  • 内存:4GB
  • 硬盘:60GB/RAID10
  • 流量:2.5TB/50Mbps
  • 架构:KVM
  • IP/面板:1IPv4/SolusVM
  • 价格:$10.5/月购买链接

香港国际

  • 套餐:香港HKGL-Plan1
  • CPU:1core
  • 内存:2GB
  • 硬盘:20GB/RAID10
  • 流量:600GB/20Mbps
  • 架构:KVM
  • IP/面板:1IPv4/SolusVM
  • 价格:$6.65/月购买链接
  • 套餐:香港HKGL-Plan2
  • CPU:2cores
  • 内存:4GB
  • 硬盘:30GB/RAID10
  • 流量:1TB/20Mbps
  • 架构:KVM
  • IP/面板:1IPv4/SolusVM
  • 价格:$7.35/月购买链接
  • 套餐:香港HKGL-Plan3
  • CPU:2cores
  • 内存:4GB
  • 硬盘:40GB/RAID10
  • 流量:1.5TB/20Mbps
  • 架构:KVM
  • IP/面板:1IPv4/SolusVM
  • 价格:$10.5/月购买链接
   优惠码:hkglus30off(7折)   2021(全场8折) 
测试IP:usmc.speedtest.hostkvm.com(洛杉矶) hkcdglobal.speedtest.hostkvm.com(香港国际)

以上优惠码均为终身折扣,续费同价,其中7折优惠码均适用于所述的两个机房,每个客户限用3次。商家采用PayPal或者支付宝等付款方式,主机支持安装Windows或者Linux操作系统。

标签: 香港VPS, 洛杉矶VPS, KVM, 日本VPS, HostKvm, 洛杉矶CN2, HostKVM优惠码