Gcore (gcorelabs) Japanese VPS simple test

Gcore (gcorelabs) Japanese VPS simple test

The tribe has shared G-core product information several times. Gcorelabs, a Luxembourg merchant founded in 2011, operates VPS hosts, CDN and independent server products in more than 30 data centers, including Khabarovsk, Vladivostok in Russia's Far East, Japan, South Korea, and Hong Kong, China, which have certain geographical advantages, and the price is cheap, starting from only 1.08 euros per month. There are fewer promotions recently, so I will conduct a simple test of the lowest package of the data center I am more interested in and post it for your reference.

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

Computer room and configuration

This time I purchased the lowest package in Japan, Tokyo: 1 core CPU + 512MB memory + 20GB hard disk + 50M bandwidth = €4.49/month, operating system is CentOS7.*

Basic Information

VPS Management Panel

The merchant provides an independent vmmanager panel. The host activation email contains information such as the panel address and login account password. The panel can be used to perform various functions such as restart, power on and off, reinstall, VNC, etc.

Disk IO test information

Bandwidth test

IO and bandwidth tests all use one-click packages. The local bandwidth is 50M, and tests in different areas are basically within the normal range.

Outbound Routing

First is the outbound routing. I tested the outbound routing through the telecom, Unicom and mobile networks in various regions. The figure below shows Shanghai Telecom and Sichuan Telecom. I also tried telecoms in several other regions and they were basically the same.

Let’s take a look at China Unicom’s outbound route. Just like China Telecom, it goes via NTT to Japan. It’s the same for all regions in China, so I only posted one.

Domestically, we tested three regions, namely Chengdu Mobile, Jiangsu Mobile and Shenyang Mobile. The north feels better than the south. The quality of Central China and South China Mobile is generally average, as it bypasses Hong Kong or the United States.

Backhaul Routing

The return line uses a one-click package and is copied directly (there are many areas tested, please scroll down to view).

 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 Test

Use IPIP.NET to test the results nationwide and in the Asia-Pacific region. After all, in Asia, the low ping in most areas is still good.

Next, I will try the data centers in Khabarovsk, Russia and the United States. I will slowly test all the data centers that I am interested in to see which area in my local area is more powerful. If you are interested, you can also check their official website directly: https://gcorelabs.com

<<:  DiyVM: Hong Kong/Japan/US VPS discounts up to 50%, 2G memory package starting at 69 yuan per month

>>:  Gcore (gcorelabs) Russian Khabarovsk VPS simple test

Recommend

SD-WAN in 2019: A conundrum for service providers

It’s that time of year again when analysts and ex...

Using machine learning to disrupt the traditional experience of the Tour de France is not the only ambition of Dimension Data!

[51CTO.com original article] The general public&#...

Verizon expands 5G enterprise network to 24 cities in the U.S.

Beijing time, April 16th morning news, the larges...

How to effectively manage network communication data? Egress traffic monitoring can reduce the burden on the network

Informatization has gradually penetrated into all...

How do IDC, CDN, and cloud service providers upgrade to IPv6?

With the rapid development of the Internet, IPv4 ...

Inventory of common Ul Ol lists and common list marker icons in HTML

[[402167]] 1. Concept The CSS list properties are...

Gcore: KVM host from €1.08/month, 26 data centers available in Russia/Asia Pacific/Europe and America

G-core (gcorelabs) is a foreign hosting company f...

Yecao Cloud: Hong Kong dedicated server from 199 yuan/month, Hong Kong cloud server from 139 yuan/year

Yecao Cloud has launched the latest promotion. Th...

Network Lifecycle Management Guide

The network lifecycle management process helps ne...

Manually implement UDP and TCP communication

[[336022]] UDP UDP is a connectionless protocol, ...

In 2017, the wireless and mobile sectors welcomed multiple favorable factors and the pace of industrial development accelerated.

[[180647]] The bell of 2017 has rung. Facing the ...

What is the relationship between the Internet of Things and the Internet, when will the explosion occur and what are their uses?

Name Explanation The Internet of Things is an imp...

Five minutes to help you understand the difference between Http and Https protocols?

In the Internet world, HTTP and HTTPS are the two...

Mixed ownership reform and restructuring: what are the three major operators doing?

The most eye-catching thing in the communications...

5G is not yet popular, but 6G is coming? Key technologies are still being explored

5G is not yet popular, but the United States clai...