2021 Vultr Los Angeles Data Center Evaluation: Mainland China has good speeds, but China Unicom has serious packet loss

I haven’t reviewed the Vultr Los Angeles data center since Telecom expanded its capacity. I just had time today, so I bought a Vultr Los Angeles data center instance and ran some test scripts. I will share with you the latest Vultr Los Angeles data center review in 2021. Information, judging from the results, the Vultr Los Angeles data center speed is good regardless of whether it is during the day or evening peak, but China Unicom users suffer from serious packet loss.

1. Introduction to data center

Vultr new user discount (new user registration will get $50): https://www.vultr.com/promo/try50/

The price of Vultr's Los Angeles data center starts at US$5 per month. It is located in the Los Angeles Data Center in the United States. It has an ordinary 163 direct connection route, 1 core 1G, 25GB SSD storage, and 1000GB traffic per month.

Vultr Los Angeles node test information:

• Test IP: 108.61.219.200
• Speed ​​test file: 100MB

2. Overall evaluation

Let’s take a look at the overall benchmark evaluation first. The IO of the Vultr machine is still good, and the bandwidth is also sufficient, almost 2Gbps:

3. Speed ​​test

This website conducted speed tests on the three networks in mainland China at the Vultr Los Angeles data center during the daytime and evening peak hours. Except for the unsatisfactory speeds of some telecommunications nodes, the speeds of the three networks were all good.

Daytime speed test:

Evening rush hour speed test:

4. Delay test

The latency of Vultr’s Los Angeles data center is around 180ms, slightly lower for telecommunications, and highest for mobile:

5. Packet loss test

China Unicom's packet loss is relatively serious, China Mobile has no packet loss, and China Telecom's packet loss is also very low. However, Alibaba Cloud and Tencent Cloud's node packet loss is very serious:

6. Routing test

The Vultr Los Angeles data center is an ordinary route 163, which has not been optimized by mainland China. The test results show that China Telecom will bypass Europe (I don’t know if it is a problem of IP ownership or it will indeed be bypassed, but the speed is indeed not fast), China Mobile and China Unicom Direct connection.

Telecom outbound route:

China Unicom outbound route:

Mobile outbound route:

Guangzhou Telecom return route:

traceroute to 113.108.209.1 (113.108.209.1), 30 hops max, 32 byte packets 1 * 2 * 3* 4* 5 76.74.41.89 0.67 ms AS286,AS3257 United States, gtt.net 6 89.149.180.78 8.19 ms AS286,AS3257 Germany, gtt.net 7 218.30.54.100 13.53 ms AS4134 United States, California, Los Angeles, ChinaTelecom 8 202.97.86.186 15.42 ms AS4134 China, ChinaTelecom 9 202.97.86.186 13.16 ms AS4134 China, ChinaTelecom 10* 11 202.97.94.125 183.45 ms AS4134 China, ChinaTelecom 12* 13 113.108.209.1 189.42 ms AS58466 China, Guangdong, Guangzhou, ChinaTelecom

Shanghai Telecom return route:

traceroute to 180.153.28.5 (180.153.28.5), 30 hops max, 32 byte packets 1 * 2 * 3* 4* 5* 6 218.30.54.72 2.32 ms AS4134 United States, California, Los Angeles, ChinaTelecom 7 218.30.54.72 4.01 ms AS4134 United States, California, Los Angeles, ChinaTelecom 8 202.97.27.217 147.33 ms AS4134 China, ChinaTelecom 9 202.97.27.217 147.11 ms AS4134 China, ChinaTelecom 10 202.97.62.157 161.04 ms AS4134 China, ChinaTelecom 11 202.97.49.33 163.42 ms AS4134 China, ChinaTelecom 12* 13 101.95.225.222 175.49 ms AS4811 China, Shanghai, ChinaTelecom 14* 15 101.227.255.34 173.87 ms AS4812 China, Shanghai, ChinaTelecom 16 180.153.28.5 172.41 ms AS4812 China, Shanghai, ChinaTelecom

Beijing Telecom return route:

traceroute to 180.149.128.9 (180.149.128.9), 30 hops max, 32 byte packets 1 * 2 * 3* 4* 5* 6 76.74.41.89 11.53 ms AS286,AS3257 United States, gtt.net 7 218.30.54.72 2.28 ms AS4134 United States, California, Los Angeles, ChinaTelecom 8 202.97.50.25 1.59 ms AS4134 China, ChinaTelecom 9 202.97.12.61 153.93 ms AS4134 China, ChinaTelecom 10* 11* 12 180.149.128.9 167.24 ms AS23724 China, Beijing, ChinaTelecom

Beijing Unicom return route:

traceroute to 123.125.99.1 (123.125.99.1), 30 hops max, 32 byte packets 1 * 2 * 3* 4* 5* 6 129.250.3.23 2.16 ms AS2914 United States, ntt.com 7 129.250.3.23 3.19 ms AS2914 United States, ntt.com 8 129.250.7.33 8.81 ms AS2914 United States, ntt.com 9 219.158.32.33 104.70 ms AS4837 China, ChinaUnicom 10 219.158.16.77 182.71 ms AS4837 China, ChinaUnicom 11 219.158.16.77 176.98 ms AS4837 China, ChinaUnicom 12 202.96.12.182 118.56 ms AS4808 China, Beijing, ChinaUnicom 13 61.148.157.170 124.44 ms AS4808 China, Beijing, ChinaUnicom 14 124.65.194.122 170.61 ms AS4808 China, Beijing, ChinaUnicom 15 61.135.113.158 157.62 ms AS4808 China, Beijing, ChinaUnicom 16* 17* 18* 19 123.125.99.1 113.27 ms AS4808 China, Beijing, ChinaUnicom

Shanghai Unicom return route:

traceroute to 123.125.99.1 (123.125.99.1), 30 hops max, 32 byte packets 1 * 2 * 3* 4* 5 76.74.41.89 1.51 ms AS286,AS3257 United States, gtt.net 6 62.115.125.163 12.25 ms AS1299 Sweden, Stockholm County, Stockholm, telia.com 7 173.241.128.50 4.12 ms AS286,AS3257 United States, California, Los Angeles, gtt.net 8 219.158.97.209 174.97 ms AS4837 China, ChinaUnicom 9 219.158.98.17 166.28 ms AS4837 China, ChinaUnicom 10 219.158.3.133 166.47 ms AS4837 China, ChinaUnicom 11* 12 202.96.12.6 231.63 ms AS4808 China, Beijing, ChinaUnicom 13 61.148.7.110 226.99 ms AS4808 China, Beijing, ChinaUnicom 14 124.65.194.50 188.10 ms AS4808 China, Beijing, ChinaUnicom 15 61.135.113.158 208.19 ms AS4808 China, Beijing, ChinaUnicom 16* 17 123.125.99.1 224.27 ms AS4808 China, Beijing, ChinaUnicom

Guangzhou Mobile return route:

traceroute to 120.196.212.25 (120.196.212.25), 30 hops max, 32 byte packets 1 * 2 * 3* 4* 5* 6 223.120.6.17 8.68 ms AS58453 China, ChinaMobile 7 223.120.32.5 185.52 ms AS58453 China, ChinaMobile 8 221.183.55.86 175.87 ms AS9808 China, ChinaMobile 9 221.183.55.90 150.47 ms AS9808 China, ChinaMobile 10 221.176.18.109 154.75 ms AS9808 China, ChinaMobile 11 221.183.52.85 164.72 ms AS9808 China, ChinaMobile 12 111.24.5.189 168.97 ms AS9808 China, ChinaMobile 13 183.235.226.161 166.17 ms AS56040 China, Guangdong, Guangzhou, ChinaMobile 14 211.136.203.18 157.32 ms AS56040 China, Guangdong, Guangzhou, ChinaMobile 15 211.136.203.6 162.69 ms AS56040 China, Guangdong, Guangzhou, ChinaMobile 16* 17* 18* 19 120.196.212.25 160.47 ms AS56040 China, Guangdong, Guangzhou, ChinaMobile

Beijing Mobile backhaul route:

traceroute to 211.136.25.153 (211.136.25.153), 30 hops max, 32 byte packets 1 * 2 * 3* 4* 5 206.72.210.219 8.81 ms AS7713,AS9009 United States, California, Los Angeles, coresite.com 6 206.72.210.219 8.94 ms AS7713,AS9009 United States, California, Los Angeles, coresite.com 7 223.120.6.17 8.78 ms AS58453 China, ChinaMobile 8 * 9 * 10 221.176.27.253 194.41 ms AS9808 China, ChinaMobile 11 111.24.2.237 189.93 ms AS9808 China, ChinaMobile 12 111.24.2.249 188.61 ms AS9808 China, ChinaMobile 13* 14 211.136.67.166 199.43 ms AS56048 China, Beijing, ChinaMobile 15* 16* 17* 18* 19* 20 211.136.25.153 192.39 ms AS56048 China, Beijing, ChinaMobile

7. Evaluation summary

The speed of the Vultr Los Angeles data center has indeed improved after the telecom expansion. Even during the evening rush hour, the speed in mainland China is not too slow. However, the disadvantage is that packet loss is still unstable. This is still not as good as the CN2 GIA route. , of course, Vultr’s price and hourly charging feature are its advantages, and everyone can choose according to their needs. You can also compare it with the previously introduced American CN2 GIA VPS: "Compilation and Recommendation of American CN2 GIA VPS Hosting Businesses"

Recommended site search: Hong Kong server rental, registered domain name, Zhengzhou server hosting, online registration query, Korean virtual host, icp website registration, virtual host evaluation, registration query Ministry of Industry and Information Technology, US server, independent ip virtual host,

p>