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

Gcore(gcorelabs)日本VPS简单测试 之聚分享过几次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.*基本信息VPS管理面板商家提供了独立的vmmanager面板，主机开通邮件里面有面板地址和登录账户密码等信息，在面板中可以进行重启、开关机、重装、VNC等等各项功能。磁盘IO测试信息带宽测试IO和带宽测试等均使用一键包，本机带宽为50M，不同区域测试基本正常范畴。去程路由首先是去程路由，通过各个地区的电信、联通和移动网络去程测试，下图为上海电信和四川电信，同时我也试了其他几个区域电信，基本上差不多。再来看看联通去程线路，与电信一样，走NTT去日本，国内各地区一样，所以我只贴了一张。国内移动，分别为成都移动、江苏移动和沈阳移动三个区域测试，感觉北方好于南方，华中和华南移动一般绕香港或者美国质量一般。回程路由回程线路使用一键包，直接复制上来(所试地区较多，请下拉查看)。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: 403Ping测试使用IPIP.NET在全国和亚太地区测试结果，毕竟亚洲地区，绝大多数地区的低ping还是不错的。 接下来我还将试试这个商家的俄罗斯伯力和美国的机房，慢慢把感兴趣的都测试一遍看看我本地哪个区域给力些，感兴趣的也可以直接在他们的官网查看：https://gcorelabs.com

Gcore：KVM主机€1.08/月起,俄罗斯/亚太/欧美等26个机房可选 G-core(gcorelabs)是一家成立于2011年的国外主机商，总部位于卢森堡，主要提供VPS主机和独立服务器租用等，数据中心包括俄罗斯、美国、日本、韩国、新加坡、荷兰、中国(香港)等多个国家和地区的十几个机房。商家VPS就要KVM架构，目前可选全球26个不同地区机房，部分机房不限制流量，其中相当一部分中国大陆访问速度不错，最低每月1.08欧元起(RU.Vladivostok)，支持PayPal或者支付宝等付款方式。下面列出不同机房不同套餐配置信息。 俄罗斯,伯力/海参崴 CPU：1core 内存：488MB 硬盘：8GB 流量：288GB/188Mbps 架构：KVM IPv4：1个 价格：€1.08/月购买链接 俄罗斯,伯力/海参崴 CPU：1core 内存：512MB 硬盘：20GB 流量：1TB/200Mbps 架构：KVM IPv4：1个 价格：€4.99/月购买链接 俄罗斯,伯力/海参崴 CPU：1core 内存：1GB 硬盘：30GB 流量：2TB/200Mbps 架构：KVM IPv4：1个 价格：€7.99/月购买链接 香港/新加坡/日本 CPU：1core 内存：512MB 硬盘：20GB 流量：500GB/50Mbps 架构：KVM IPv4：1个 价格：€4.49/月购买链接 香港/新加坡/日本 CPU：1core 内存：1GB 硬盘：30GB 流量：1TB/50Mbps 架构：KVM IPv4：1个 价格：€7.19/月购买链接 香港/新加坡/日本 CPU：2cores 内存：2GB 硬盘：50GB 流量：2TB/50Mbps 架构：KVM IPv4：1个 价格：€13.49/月购买链接 美国, SantaClara CPU：1core 内存：512MB 硬盘：20GB 流量：200M无限 架构：KVM IPv4：1个 价格：€3.25/月购买链接 美国, SantaClara CPU：1core 内存：1GB 硬盘：30GB 流量：200M无限 架构：KVM IPv4：1个 价格：€4.95/月购买链接 美国, SantaClara CPU：2cores 内存：2GB 硬盘：50GB 流量：200M无限 架构：KVM IPv4：1个 价格：€8.99/月购买链接 俄罗斯,Moscow CPU：1core 内存：512MB 硬盘：20GB 流量：200Mbps无限 架构：KVM IPv4：1个 价格：€3.25/月购买链接 俄罗斯,Moscow CPU：1core 内存：1GB 硬盘：30GB 流量：200Mbps无限 架构：KVM IPv4：1个 价格：€4.95/月购买链接 俄罗斯,Moscow CPU：2cores 内存：2GB 硬盘：50GB 流量：200Mbps无限 架构：KVM IPv4：1个 价格：€8.99/月购买链接    测试地址：https://lg.gcorelabs.com/prefix_detail/请留意低价套餐仅部分节点有货，大家尽量根据测试IP本地测试选择，比如亚洲我本地对新加坡ping不错，还有俄罗斯的部分机房如伯力，海参崴等，关于如何在测试页面查看测试IP也可以参考我之前专门的一篇文章：https://www.vpsok.net/VPS_help/article_7036.html，文尾我贴几个机房测试信息。俄罗斯Khabarovsk(伯力) 92.223.110.64俄罗斯Vladivostok(海参崴) 185.101.137.64俄罗斯Moscow(莫斯科) 92.223.122.64新加坡Singapore 92.223.116.64中国香港HongKong 45.135.231.64日本Tokyo 92.223.63.66韩国Seoul 92.223.61.64美国SantaClara 92.223.120.70荷兰Amsterdam 92.223.126.65英国London 92.223.58.66卢森堡Luxembourg 92.223.112.68

Gcore：伯力/海参崴KVM每月1.08欧元起,488M内存/8G硬盘/288G月流量 G-core(gcorelabs)在之聚分享过几次，这是一家规模比较大的国外主机商，总部位于卢森堡，主要提供VPS和独立服务器租用等，其中VPS基于KVM架构，数据中心包括俄罗斯、美国、日本、韩国、新加坡、荷兰等多个国家的十几个机房。商家支持PayPal或者支付宝等付款方式，在数据中心上还有国内物理距离较近的香港、日本、新加坡，以及俄罗斯远东地区机房，比如伯力、海参崴等等。目前商家针对俄罗斯伯力/海参崴上架了一款低配套餐，价格仅每月1.08欧元起。CPU：1 core内存：488MB硬盘：8GB SSD流量：288GB/月带宽：188Mbps【Order】购买链接   测试地址：https://lg.gcorelabs.com/prefix_detail/注意测试地址我提供了一个链接，该链接提供了商家所有节点，直接在页面左上部分Nodes选择即可。上面的这个低配套餐只有在伯力(Russia, Khabarovsk)和海参崴(Russia, Vladivostok)提供，下单的时候留意机房信息。除了这两个低配套餐之外，其他机房的常规套餐价格也不贵，最低每月3.25欧元起，除了我在文章第一段列出的那些亚洲地区外，像USA SantaClara(测试IP：92.38.148.1)，Russia Moscow(测试IP：92.223.103.1)等也还是不错的。

Gcore：€125/月-E3 1270v5/32GB/2x2TB/俄罗斯(伯力)/支持支付宝 G-core(gcorelabs)是一家总部位于卢森堡的国外主机商，主要提供基于KVM架构的VPS主机和独立服务器租用等，数据中心包括俄罗斯、美国、日本、韩国、新加坡、荷兰等多个国家的十几个机房。今年初商家加入了支付宝付款支持，甚至提供了中文的知识库，国内用户购买和支付更加方便了。最近收到商家的促销信息，表示对部分独立服务器升级到无限流量的价格进行了优惠，譬如标题这款俄罗斯伯力机房的机器升级到60TB月流量后价格为200美元。 下面列几款不同机房的独立服务器配置信息。 配置一   €125/月 CPU：E3-1270v5 内存：32GB 硬盘：2x2TB SATA 月流量：20TB/1Gbps IP：1IPv4+1IPv6 机房：俄罗斯.伯力 【Order】购买链接 备注：商家邮件表示升级到60TB后仅200美元，但是没说怎么优惠(订购链接直接选价格较高)，确有需要的话建议先工单。   配置二   €187/月 CPU：E-2136 内存：64GB 硬盘：2x480GB SSD 月流量：20TB/1Gbps IP：1IPv4+1IPv6 机房：美国.圣克拉拉 【Order】购买链接 备注：商家邮件表示升级到150TB后仅190美元，无限流量290美元，同上不清楚怎么优惠，建议工单确认好再下单。测试IP：92.223.80.1(伯力)   92.38.148.1(圣克拉拉)商家邮件还提供了一款圣克拉拉的机器信息，不过在会员中心产品列表未找到该款就不贴出了。俄罗斯伯力在远东地区，距离上离黑龙江不远，目前ping国内三网速度都不错，另外圣克拉拉也是美国对国内访问速度较好的地区。以上机器默认只有1个IP，可以在订购链接升级到最多15个IP；主机支持Windows或者Linux操作系统。

Gcore如何查看测试IP信息 有读者找到我问这个Gcore的测试IP怎么看，我看了下之聚关于gcore文章页面测试信息提供的是官方的测试页面，其实这种测试页面也很直观，使用的商家也有一些，闲来无事跟大家一起看看这个测试ip怎么看，要是中文页面的话那就无压力了。 商家测试页面(Looking Glass)为：lg.gcorelabs.com 我们访问这个页面，可以看到如下图所示，我用箭头和框选标注了部分关键信息，左上交的Nodes后面可选择不同的数据中心。 比如我们选择Khabarovsk(伯力)，Command默认是show route for，下图椭圆框选的2个IP都可以测试，都是该机房的IP，其他节点依此类推。 关于G-CORE LABSgcorelabs是一家成立于2013年的国外主机商，提供的VPS和独立服务器遍布全球十几个国家和地区，其中俄罗斯哈巴罗夫斯克(又称伯力)、日本、韩国、新加坡等地区在国内访问速度都不错，而且，商家在今年还开始提供支付宝付款支持，中国客户购买无压力。我把他测试页面的绝大多数地区都ping了下，除了上面说的俄罗斯伯力(Khabarovsk)、日本(Tokyo)、韩国(Seoul)、新加坡(Singapore)四个地区ping值较低外，另外俄罗斯莫斯科(Moscow)、美国圣何塞(SantaClara)、俄罗斯克拉斯诺亚尔斯克(Krasnoyarsk)这几个也是ping较低的节点，在200ms左右或者以下(仅本地成都电信测试结果)，大家也可以自行测试下。 官方网站：https://gcorelabs.com/

Gcore：3.25欧元起/KVM/无限流量/支持支付宝/可选美国/日本/俄罗斯/波兰/韩国等 查了下之聚对于Gcore的上一次信息还停留在一年前，商家在今年2月份加入了支付宝付款支持，当时也忘了分享，现在补充下。这是一家俄罗斯主机商，提供虚拟主机、VPS、CDN和独立服务器租用等，可选数据中心较多，包括俄罗斯莫斯科、新西伯利亚、日本、韩国、波兰、美国迈阿密、芝加哥、圣克拉拉、卢森堡、荷兰等等，部分节点无限流量，月付最低3.25欧元起。下面就以新上的波兰机房为例，分享几款套餐配置信息。 CPU：1core 内存：512MB 硬盘：20G SSD 流量：无限/200Mbps 架构：KVM IP/面板：1IPv4/自有面板 价格：€3.25/月购买链接 CPU：1core 内存：1GB 硬盘：30G SSD 流量：无限/200Mbps 架构：KVM IP/面板：1IPv4/自有面板 价格：€4.95/月购买链接 CPU：2cores 内存：2GB 硬盘：50G SSD 流量：无限/200Mbps 架构：KVM IP/面板：1IPv4/自有面板 价格：€8.99/月购买链接 测试IP(Looking Glass)：lg.gcorelabs.com访问上面的Looking Glass，左上角的nodes可以选择各个不同机房然后查看测试IP信息，商家的机房比较多，部分机房国内访问速度尚可，比如俄罗斯Khabarovsk，日本，美国圣克拉拉等，VPS主机基于KVM架构，操作系统方面均为Linux系统。

Gcore：3.25欧元起/KVM/无限流量/支持支付宝/可选美国/日本/俄罗斯/波兰/韩国等 查了下之聚对于Gcore的上一次信息还停留在一年前，商家在今年2月份加入了支付宝付款支持，当时也忘了分享，现在补充下。这是一家俄罗斯主机商，提供虚拟主机、VPS、CDN和独立服务器租用等，可选数据中心较多，包括俄罗斯莫斯科、新西伯利亚、日本、韩国、波兰、美国迈阿密、芝加哥、圣克拉拉、卢森堡、荷兰等等，部分节点无限流量，月付最低3.25欧元起。下面就以新上的波兰机房为例，分享几款套餐配置信息。 CPU：1core 内存：512MB 硬盘：20G SSD 流量：无限/200Mbps 架构：KVM IP/面板：1IPv4/自有面板 价格：€3.25/月购买链接 CPU：1core 内存：1GB 硬盘：30G SSD 流量：无限/200Mbps 架构：KVM IP/面板：1IPv4/自有面板 价格：€4.95/月购买链接 CPU：2cores 内存：2GB 硬盘：50G SSD 流量：无限/200Mbps 架构：KVM IP/面板：1IPv4/自有面板 价格：€8.99/月购买链接 测试IP(Looking Glass)：lg.gcorelabs.com访问上面的Looking Glass，左上角的nodes可以选择各个不同机房然后查看测试IP信息，商家的机房比较多，部分机房国内访问速度尚可，比如俄罗斯Khabarovsk，日本，美国圣克拉拉等，VPS主机基于KVM架构，操作系统方面均为Linux系统。