搜索到
1
篇与
gcorelabs伯力VPS
的结果
-
![Gcore(gcorelabs)俄罗斯伯力VPS简单测试]()
Gcore(gcorelabs)俄罗斯伯力VPS简单测试 上一篇分享了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基本信息商家所有机房VPS均提供了一样的vmmanager面板，独立控制，产品信息邮件中有面板信息，也可以通过会员中心来一键登陆到面板，面板提供了VPS主机所有的常用管理功能，这里就不再贴图。IO和带宽信息这里采用了2个不同的一键命令，所以贴出2条命令的结果。两个测试结果差距不大，可以结合来看，相对于上一次测试的日本VPS来说IO低了一些，但是带宽高了很多，考虑到这个套餐本身的配置和价格也算是物有所值。去程路由同样在国内电信、联通和移动网络访问VPS来查看线路情况。从上面三个地区电信来看，总体线路一致，起点→北京→天津→俄罗斯，实际上我还在更多区域电信测试也一样，比较稳；联通也是如此，下面是联通测试结果。无论是电信还是联通，线路都非常稳定，各个地区都一样。移动宽带测试去程路线也比较一致，但是相对于电信联通来说就比较差了，均从起点到北京，然后到德国再到俄罗斯，绕了一个圈子。回程路由回程测试在主机中运行脚本，与去程一样，整体来说电信、联通线路较好，移动不推荐。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: 503Ping测试也是用IPIP.NET在全国和亚太地区测试结果，国内延迟电信/联通优秀，移动较高。 总的来说，伯力机房在国内访问线路质量还是不错的，电信/联通用户推荐，但是移动宽带用户请尽量考虑其他区域，毕竟商家有30多个机房可选(比如新加坡/中国香港等)，可以直接在官网查看测试IP信息：https://gcorelabs.com
