Gcore (gcorelabs) Hong Kong VPS simple test

A few days ago, we did a simple test of Gcore's (gcorelabs) Vladivostok VPS in Russia. In addition, at the beginning of the year, we tested the computer rooms in Khabarovsk, Russia, Santa Clara, USA, and Japan. Today, we will try Hong Kong, China. This is a foreign hosting company founded in 2011, headquartered in Luxembourg, mainly providing VPS hosting and independent server rental, etc. The data centers include more than a dozen computer rooms in Russia, the United States, Japan, South Korea, Singapore, the Netherlands, China (Hong Kong) and other countries and regions.

Official website: https://gcorelabs.com/cn/hosting/vds/

Computer room and configuration

The VPS involved in this article is in the Hong Kong data center, China, and the package is still the iron rule of the tribe test: minimum configuration, single-core CPU, 512MB memory, 20GB hard disk, 200Mbps port.

Basic test information

The merchant VPS platform hosts all provide an independent management panel, vmmanager. You can log in with one click in the member center product management, or you can log in by checking the VMmanager panel login information in the VPS host activation email. The functions provided by the panel are similar. The commonly used restart, power on and off, system reinstallation, VNC, snapshots, etc. are all provided, so I will not repeat the pictures here.

IO and bandwidth information

Using two different one-click packages for testing, the IO performance has been greatly enhanced compared to the Vladivostok test two days ago. However, since the line is not optimized for China, the bandwidth test mainly in various parts of mainland China is relatively average.

Here is another test command, which produces basically the same result as the previous one.

Outbound Routing

We tested the outbound routes of China Telecom, China Unicom and China Mobile on IPIP.NET respectively. Among the three networks, China Mobile performed the best, while China Telecom and China Unicom took detours.

Backhaul Routing

I used the one-key command to test it directly on the return trip, and posted the results below.

 -------------------------------------------------------------------------------
Guangzhou Telecom traceroute to 14.215.116.1 (14.215.116.1), 30 hops max, 32 byte packets
 1 gw.gcore.lu (5.188.230.1) 0.25 ms AS199524 China, Hong Kong, gcore.lu
 2 10.255.47.182 0.16 ms * LAN Address
 3 10.255.47.177 0.18 ms * LAN Address
 4 223.119.2.57 4.09 ms AS58453 China, Hong Kong, ChinaMobile
 5 221.183.30.153 158.34 ms AS9808 China, Guangdong, Guangzhou, ChinaMobile
 6 221.176.24.61 7.78 ms AS9808 China, Guangdong, Guangzhou, ChinaMobile
 7 221.176.24.181 7.67 ms AS9808 China, Guangdong, Guangzhou, ChinaMobile
 8 221.176.22.186 156.71 ms AS9808 China, Guangdong, Guangzhou, ChinaMobile
 9 *
10 *
11 113.96.4.46 58.68 ms AS58466 China, Guangdong, Guangzhou, ChinaTelecom
12 183.2.145.210 55.52 ms AS58466 China, Guangdong, Guangzhou, ChinaTelecom
13 183.56.128.2 171.30 ms AS58466 China, Guangdong, Guangzhou, ChinaTelecom
14 14.215.116.1 57.29 ms AS58466 China, Guangdong, Guangzhou, ChinaTelecom

-------------------------------------------------------------------------------
Shanghai Telecom traceroute to 101.95.120.109 (101.95.120.109), 30 hops max, 32 byte packets
 1 gw.gcore.lu (5.188.230.1) 0.18 ms AS199524 China, Hong Kong, gcore.lu
 2 10.255.47.182 0.17 ms * LAN Address
 3 10.255.47.177 0.20 ms * LAN Address
 4 10.255.14.195 1.08 ms * LAN Address
 5 203.131.242.169 1.88 ms AS2914 China, Hong Kong, ntt.com
 6 ae-6.r27.tkokhk01.hk.bb.gin.ntt.net (129.250.6.95) 2.43 ms AS2914 China, Hong Kong, ntt.com
 7 ae-7.r22.sngpsi07.sg.bb.gin.ntt.net (129.250.7.66) 38.29 ms AS2914 Singapore, ntt.com
 8 ae-0.a00.sngpsi07.sg.bb.gin.ntt.net (129.250.2.74) 38.57 ms AS2914 Singapore, ntt.com
 9 *
10 202.97.93.157 326.61 ms AS4134 China, Shanghai, ChinaTelecom
11 *
12 *
13 *
14 *
15 101.95.120.109 321.04 ms AS4812 China, Shanghai, ChinaTelecom

-------------------------------------------------------------------------------
Xiamen Telecom traceroute to 117.28.254.129 (117.28.254.129), 30 hops max, 32 byte packets
 1 gw.gcore.lu (5.188.230.1) 0.23 ms AS199524 China, Hong Kong, gcore.lu
 2 10.255.47.182 0.22 ms * LAN Address
 3 10.255.47.177 0.25 ms * LAN Address
 4 10.255.14.195 0.97 ms * LAN Address
 5 hutchcity11-100g.hkix.net (123.255.91.41) 2.40 ms * China, Hong Kong, hkix.net
 6 218.188.104.218 5.04 ms AS9304 China, Hong Kong, hgc.com.hk
 7 59.43.248.245 7.27 ms * China, Guangdong, Guangzhou, ChinaTelecom
 8 *
 9 59.43.130.149 9.78 ms * China, Guangdong, Guangzhou, ChinaTelecom
10 59.43.46.214 23.99 ms * China, Fujian, ChinaTelecom
11 *
12 27.148.195.98 68.69 ms AS133775 China, Fujian, Xiamen, ChinaTelecom
13 117.25.141.110 65.97 ms AS133775 China, Fujian, Xiamen, ChinaTelecom
14 117.28.254.129 24.13 ms AS4809 China, Fujian, Xiamen, ChinaTelecom

-------------------------------------------------------------------------------
Chongqing Unicom traceroute to 113.207.25.138 (113.207.25.138), 30 hops max, 32 byte packets
 1 gw.gcore.lu (5.188.230.1) 0.20 ms AS199524 China, Hong Kong, gcore.lu
 2 10.255.47.181 0.21 ms * LAN Address
 3 10.255.47.177 0.20 ms * LAN Address
 4 10.255.14.196 1.05 ms * LAN Address
 5 203.131.243.17 2.77 ms AS2914 China, Hong Kong, ntt.com
 6 ae-8.r26.tkokhk01.hk.bb.gin.ntt.net (129.250.6.99) 3.43 ms AS2914 China, Hong Kong, ntt.com
 7 ae-0.r27.tkokhk01.hk.bb.gin.ntt.net (129.250.5.29) 3.49 ms AS2914 China, Hong Kong, ntt.com
 8 ae-4.r26.osakjp02.jp.bb.gin.ntt.net (129.250.2.42) 45.92 ms AS2914 Japan, Osaka, ntt.com
 9 ae-5.r30.tokyjp05.jp.bb.gin.ntt.net (129.250.7.78) 49.14 ms AS2914 Japan, Tokyo, ntt.com
10 ae-2.r03.tokyjp05.jp.bb.gin.ntt.net (129.250.3.33) 53.75 ms AS2914 Japan, Tokyo, ntt.com
11 219.158.32.29 230.60 ms AS4837 China, Beijing, ChinaUnicom
12 219.158.9.226 239.37 ms AS4837 China, Beijing, ChinaUnicom
13 *
14 219.158.12.70 271.87 ms AS4837 China, Chongqing, ChinaUnicom
15 113.207.25.138 255.89 ms AS4837 China, Chongqing, ChinaUnicom

-------------------------------------------------------------------------------
Chengdu Unicom traceroute to 119.6.6.6 (119.6.6.6), 30 hops max, 32 byte packets
 1 gw.gcore.lu (5.188.230.1) 0.21 ms AS199524 China, Hong Kong, gcore.lu
 2 10.255.47.182 0.22 ms * LAN Address
 3 10.255.47.177 0.30 ms * LAN Address
 4 10.255.14.196 0.97 ms * LAN Address
 5 203.131.243.17 2.69 ms AS2914 China, Hong Kong, ntt.com
 6 ae-8.r26.tkokhk01.hk.bb.gin.ntt.net (129.250.6.99) 3.47 ms AS2914 China, Hong Kong, ntt.com
 7 ae-12.r30.tokyjp05.jp.bb.gin.ntt.net (129.250.2.50) 44.91 ms AS2914 Japan, Tokyo, ntt.com
 8 ae-2.r03.tokyjp05.jp.bb.gin.ntt.net (129.250.3.33) 49.45 ms AS2914 Japan, Tokyo, ntt.com
 9 *
10 219.158.16.65 218.91 ms AS4837 China, Beijing, ChinaUnicom
11 *
12 219.158.110.206 258.09 ms AS4837 China, Sichuan, Chengdu, ChinaUnicom
13 119.6.197.194 250.41 ms AS4837 China, Sichuan, Chengdu, ChinaUnicom
14 119.7.220.218 312.61 ms AS4837 China, Sichuan, Chengdu, ChinaUnicom
15 119.6.6.6 264.87 ms AS4837 China, Sichuan, Chengdu, ChinaUnicom

-------------------------------------------------------------------------------
Shanghai Mobile traceroute to 120.204.197.126 (120.204.197.126), 30 hops max, 32 byte packets
 1 gw.gcore.lu (5.188.230.1) 0.25 ms AS199524 China, Hong Kong, gcore.lu
 2 10.255.47.182 0.21 ms * LAN Address
 3 10.255.47.177 0.27 ms * LAN Address
 4 223.119.2.57 5.47 ms AS58453 China, Hong Kong, ChinaMobile
 5 223.120.22.5 175.64 ms AS58453 China, Guangdong, Guangzhou, ChinaMobile
 6 221.183.55.30 54.78 ms AS9808 China, Shanghai, ChinaMobile
 7 221.183.25.189 175.71 ms AS9808 China, Shanghai, ChinaMobile
 8 221.176.17.217 54.69 ms AS9808 China, Shanghai, ChinaMobile
 9 111.24.3.85 176.89 ms AS9808 China, Shanghai, ChinaMobile
10 *
11 117.185.10.130 33.07 ms AS9808 China, Shanghai, ChinaMobile
12 120.204.194.14 35.81 ms AS9808 China, Shanghai, ChinaMobile
13 120.204.197.126 33.91 ms AS9808 China, Shanghai, ChinaMobile

-------------------------------------------------------------------------------
Chengdu Mobile traceroute to 183.221.253.100 (183.221.253.100), 30 hops max, 32 byte packets
 1 gw.gcore.lu (5.188.230.1) 0.23 ms AS199524 China, Hong Kong, gcore.lu
 2 10.255.47.181 0.15 ms * LAN Address
 3 10.255.47.177 0.21 ms * LAN Address
 4 223.119.2.57 4.43 ms AS58453 China, Hong Kong, ChinaMobile
 5 223.120.2.6 52.83 ms AS58453 China, Guangdong, Guangzhou, ChinaMobile
 6 221.183.55.54 159.86 ms AS9808 China, Guangdong, Guangzhou, ChinaMobile
 7 221.176.19.41 6.86 ms AS9808 China, Guangdong, Guangzhou, ChinaMobile
 8 221.176.22.157 9.48 ms AS9808 China, Guangdong, Guangzhou, ChinaMobile
 9 111.24.5.165 158.84 ms AS9808 China, Guangdong, Guangzhou, ChinaMobile
10 111.24.2.145 187.67 ms AS9808 China, Beijing, ChinaMobile
11 221.176.21.202 188.87 ms AS9808 China, Beijing, ChinaMobile
12 *
13 183.221.253.100 186.43 ms AS9808 China, Sichuan, Chengdu, ChinaMobile

-------------------------------------------------------------------------------
Chengdu Education Network traceroute to 202.112.14.151 (202.112.14.151), 30 hops max, 32 byte packets
 1 gw.gcore.lu (5.188.230.1) 0.21 ms AS199524 China, Hong Kong, gcore.lu
 2 10.255.47.181 0.22 ms * LAN Address
 3 10.255.47.177 0.19 ms * LAN Address
 4 223.119.2.57 5.78 ms AS58453 China, Hong Kong, ChinaMobile
 5 221.183.30.153 158.35 ms AS9808 China, Guangdong, Guangzhou, ChinaMobile
 6 221.176.24.61 7.28 ms http: 403 http: 403
 7 221.176.22.237 53.64 ms http: 403 http: 403
 8 111.24.5.1 8.25 ms http: 403 http: 403
 9 111.24.4.130 83.38 ms http: 403 http: 403
10 *
11 221.183.20.122 63.39 ms http: 403 http: 403
12 101.4.115.122 56.10 ms http: 403 http: 403
13 *
14 202.115.255.2 913.80 ms http: 403 http: 403
15 *
16 *
17 202.112.14.151 55.92 ms http: 403 http: 403

Ping Test

The same test was conducted using IPIP.NET, with only nodes in mainland China, Hong Kong, Macau, Taiwan, and Asia selected.

In general, Hong Kong has optimized lines outside of China, and mobile broadband is optional. Telecom and Unicom users are recommended to choose other regions, such as Khabarovsk, Russia, Santa Clara, USA, etc. The merchant has more than 30 computer rooms, and you can choose according to your actual situation.
Official website: https://gcorelabs.com