Last update at ：2024-03-17，Edit by888u
Recently, I have seen several people praising the performance of Vultr Japan data center in mainland China after Telecom’s expansion. So we bought one at our own expense and ran the test script. Judging from the results, after Telecom’s expansion, Vultr Japan’s data center performed very well. The center has indeed become a lot faster, but the packet loss in mainland China is still relatively high, especially for China Mobile. The packet loss is so high that it is not useful at all.
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 Japanese data center starts at US$5 per month. It is located in Tokyo, Japan, on the Japanese NTT route, with 1 core and 1G, 25GB SSD storage, and 1,000GB of traffic per month.
Vultr Japanese node test information:
- Test IP: 108.61.201.151
- Speed test file: 100MB
2. Overall evaluation
Let’s take a look at the overall benchmark evaluation first. The IO of Vultr Japan VPS is really powerful, up to 1.6GB/s. The bandwidth test upload speed is 6Gbps and the download speed is 3Gbps. The speeds in mainland China and international countries are also good:
3. Speed test
Similarly, we conducted speed tests on the three networks in mainland China on the Vultr Japanese data center during the daytime and evening peaks. The speed performance was indeed good, and the speeds of China Telecom, China Mobile and China Unicom were all acceptable.
Daytime speed test:
Evening rush hour speed test:
Tested the move again:
4. Delay test
The latency of Vultr’s Japanese data center is even higher than that of the US data center, with an average of 250ms across multiple lines:
5. Packet loss test
The packet loss is very high, especially for mobile. The packet loss rate is nearly 90, which is not useful at all:
6. Routing test
The Vultr Japanese data center should be the Japanese NTT route, but due to the problem of IP ownership, the routing test results are very strange, so just take a look.
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 62.115.41.150 0.50 ms AS1299 Sweden, Stockholm County, Stockholm, telia.com 6 62.115.41.150 0.90 ms AS1299 Sweden, Stockholm County, Stockholm, telia.com 7 62.115.123.140 106.83 ms AS1299 Sweden, Stockholm County, Stockholm, telia.com 8 202.97.81.85 108.00 ms AS4134 China, ChinaTelecom 9 202.97.81.85 107.37 ms AS4134 China, ChinaTelecom 10 202.97.94.117 165.83 ms AS4134 China, ChinaTelecom 11 202.97.94.149 163.91 ms AS4134 China, ChinaTelecom 12 113.108.208.218 168.01 ms AS58466 China, Guangdong, Guangzhou, ChinaTelecom 13* 14 113.108.209.1 160.81 ms AS58466 China, Guangdong, Guangzhou, ChinaTelecomShanghai Telecom return route:
traceroute to 180.153.28.5 (180.153.28.5), 30 hops max, 32 byte packets 1 * 2 * 3* 4* 5 62.115.41.150 0.48 ms AS1299 Sweden, Stockholm County, Stockholm, telia.com 6 62.115.123.140 106.41 ms AS1299 Sweden, Stockholm County, Stockholm, telia.com 7* 8 202.97.83.25 110.91 ms AS4134 China, ChinaTelecom 9 61.152.25.133 153.18 ms AS4812 China, Shanghai, ChinaTelecom 10 101.95.207.6 187.93 ms AS4812 China, Shanghai, ChinaTelecom 11 101.95.225.158 169.60 ms AS4811 China, Shanghai, ChinaTelecom 12 101.95.88.93 244.07 ms AS4812 China, Shanghai, ChinaTelecom 13* 14 101.95.225.206 244.45 ms AS4811 China, Shanghai, ChinaTelecom 15 180.153.28.5 168.60 ms AS4812 China, Shanghai, ChinaTelecomBeijing 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 62.115.123.140 106.42 ms AS1299 Sweden, Stockholm County, Stockholm, telia.com 7 218.30.54.181 110.11 ms AS4134 United States, California, Los Angeles, ChinaTelecom 8 202.97.81.177 107.49 ms AS4134 China, ChinaTelecom 9 202.97.81.177 108.18 ms AS4134 China, ChinaTelecom 10 202.97.28.121 157.88 ms AS4134 China, ChinaTelecom 11 202.97.12.61 150.30 ms AS4134 China, ChinaTelecom 12 180.149.159.6 156.90 ms AS23724 China, Beijing, ChinaTelecom 13 180.149.128.9 166.66 ms AS23724 China, Beijing, ChinaTelecomBeijing 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, ChinaUnicomShanghai Unicom return route:
traceroute to 58.247.8.158 (58.247.8.158), 30 hops max, 32 byte packets 1 * 2 * 3* 4* 5* 6 120.88.54.97 1.24 ms AS2914 Japan, Tokyo, ntt.com 7 129.250.7.79 11.54 ms AS2914 United States, ntt.com 8 129.250.7.81 24.06 ms AS2914 United States, ntt.com 9 129.250.66.86 85.12 ms AS2914 United States, ntt.com 10 219.158.113.118 111.56 ms AS4837 China, ChinaUnicom 11 219.158.113.109 149.43 ms AS4837 China, ChinaUnicom 12* 13 58.247.221.178 148.53 ms AS17621 China, Shanghai, ChinaUnicom 14 58.247.221.178 100.03 ms AS17621 China, Shanghai, ChinaUnicom 15 139.226.225.22 149.74 ms AS17621 China, Shanghai, ChinaUnicom 16 58.247.8.153 110.22 ms AS17621 China, Shanghai, ChinaUnicomGuangzhou Mobile return route:
traceroute to 113.108.209.1 (113.108.209.1), 30 hops max, 32 byte packets 1 * 2 * 3* 4* 5 62.115.41.150 0.50 ms AS1299 Sweden, Stockholm County, Stockholm, telia.com 6 62.115.41.150 0.90 ms AS1299 Sweden, Stockholm County, Stockholm, telia.com 7 62.115.123.140 106.83 ms AS1299 Sweden, Stockholm County, Stockholm, telia.com 8 202.97.81.85 108.00 ms AS4134 China, ChinaTelecom 9 202.97.81.85 107.37 ms AS4134 China, ChinaTelecom 10 202.97.94.117 165.83 ms AS4134 China, ChinaTelecom 11 202.97.94.149 163.91 ms AS4134 China, ChinaTelecom 12 113.108.208.218 168.01 ms AS58466 China, Guangdong, Guangzhou, ChinaTelecom 13* 14 113.108.209.1 160.81 ms AS58466 China, Guangdong, Guangzhou, ChinaTelecomBeijing Mobile backhaul route:
traceroute to 211.136.25.153 (211.136.25.153), 30 hops max, 32 byte packets 1 * 2 * 3* 4* 5 120.88.54.97 1.22 ms AS2914 Japan, Tokyo, ntt.com 6 120.88.54.97 1.16 ms AS2914 Japan, Tokyo, ntt.com 7 129.250.3.23 0.85 ms AS2914 United States, ntt.com 8 129.250.6.98 46.85 ms AS2914 United States, ntt.com 9 129.250.6.98 47.89 ms AS2914 United States, ntt.com 10* 11* 12* 13* 14* 15* 16* 17* 18* 19* 20* twenty one * twenty two * twenty three * twenty four * 25* 26* 27* 28* 29* 30*7. Evaluation summary
Compared with the 2020 evaluation ("Vultr Japan Tokyo Data Center Evaluation: Speed, Latency, Packet Loss Rate and Routing Test"), the speed of Vultr Japan Data Center has indeed improved after Telecom expanded its capacity, but what about packet loss? It’s still terrible, and the delay is very high. To sum up, Japan’s NTT is still unusable.
If you need a Japanese VPS, then you can consider the Japanese SoftBank route, which is relatively affordable. After this expansion, the delay is low and the speed is fast. This site has also shared a comparison before: "Comparison between Bricklayer Japan and Vultr Japan Data Center , which one is better and how to choose? 》, this is an evaluation of Telecom after expansion. Mainland China performed very well: "Evaluation of SoftBank Data Center in Osaka, Japan after Telecom expansion: Packet loss is reduced, delay is stable, speed becomes faster (even the bandwidth is full)"
Recommended site searches: Hong Kong vps, server Hong Kong, free mainland China space and foreign website space, cn domain name price, Hong Kong virtual host space, yellow pages, virtual host purchase, website registration, registration,
发表评论