Measuring latency from Guangzhou, Shenzhen and Shanghai to a Vietnam VPS

If you run a team, a business or a software operation that touches Vietnam from inside China, the first question is always the same: what is the real latency from my city to a Vietnam VPS? You have seen forum posts quoting numbers from Hong Kong or Singapore, neither of which is your route. The only figure that matters is the one you measure yourself, from your own carrier, toward a real Vietnam IPv4, at the time of day you actually work. This article gives you the exact method: which tools to run, how to read the output, what the domestic carriers (China Telecom, China Unicom, China Mobile) do with their traffic, and where the path crosses into Vietnam. No invented averages. You run the commands, you get your number.

• Key takeaway: Latency from Guangzhou/Shenzhen to a Hanoi VPS is usually 30 to 50 ms; from Shanghai 50 to 80 ms; from Beijing 70 to 100 ms, but your carrier and time of day change it.
• Key takeaway: The largest variable is which Chinese carrier handles the traffic. China Unicom often routes via Hong Kong; China Telecom can jump via Singapore depending on peering.
• Key takeaway: Traffic leaving the Chinese domestic network is the first and most variable hop. You need to identify where that happens.
• Key takeaway: A Vietnam VPS is local infrastructure for work that touches Vietnam, your own accounts, your own systems, your own Vietnamese users and partners.

从广州到越南服务器的实际延迟大约在30到50毫秒之间，具体取决于你的网络运营商。

Latency from Guangzhou to a Vietnam server is around 30 to 50 ms, depending on your carrier.

Why you should measure yourself, not trust benchmarks

A benchmark number posted on a forum three years ago tells you nothing about your path today. Routing changes: China Telecom may have shifted a peer, a submarine cable may be in maintenance, and a carrier in Vietnam (VNPT, Viettel, FPT, CMC Telecom) may have changed its upstream. Your city matters: a Ping from Guangzhou (80 km from Hong Kong) hits different cables than a Ping from Shanghai (800 km away), and both are completely different from Beijing or Kunming. Your carrier matters: China Telecom and China Mobile route Vietnam traffic through different gateways. A VPS for Chinese users sitting on a Viettel IP in Hanoi may behave differently than one on a VNPT IP in Ho Chi Minh City. The only truthful answer is the one you measure at 10:00 AM on a Tuesday from your own desk.

Tools of the trade, what to install

You need three tools. All are standard and available on any Linux or macOS system, and on Windows through WSL or native binaries:

• ping, measures round-trip time (RTT) to a single IP. Fast, but tells you nothing about where the delay is.
• mtr, combines traceroute and ping. Shows every hop from you to the target, with packet loss and latency per hop. This is the tool you will rely on.
• traceroute (Windows: tracert), the older version of mtr. Still useful when mtr is not available.

# On Debian / Ubuntu
sudo apt update && sudo apt install mtr

# On AlmaLinux / Rocky Linux
sudo dnf install mtr

# On macOS (Homebrew)
brew install mtr

If you are on a Windows VPS (RDP into a Windows Server instance), you can use tracert from the command prompt. For mtr on Windows, install the WinMTR utility, it gives the same hop-by-hop view.

Step 1, Ping a real Vietnam IPv4

Start simple. Get the IPv4 of a server inside Vietnam, any VPS you control, your own, or a public DNS resolver from VNPT or Viettel. Do not use a domain served through a CDN; a CDN may terminate the connection in Singapore or Hong Kong and give you a fake latency.

# Example, replace with a real Vietnam IP you control
ping -c 20 123.30.220.123

# On Windows (replace IP)
ping -n 20 123.30.220.123

Read the output: look for min/avg/max/mdev on Linux, or Minimum / Maximum / Average on Windows. The average is your baseline. If the packet loss is above 1 %, something on the path is dropping. Do not dismiss loss under 1 %, for real-time work (SSH, database queries), even 0.5 % is noticeable.

Step 2, mtr to see every hop

Ping hides the path. mtr shows it. Run this from your machine in China toward a Vietnam IP:

mtr --report --report-wide 123.30.220.123

# On Windows (WinMTR): fill in the same IP and click Start

The output is a table. Each row is a hop. The columns you care about:

• Loss%, packet loss at that hop. If a hop in the middle shows loss but later hops do not, that router is deprioritising ICMP (common and harmless). If loss persists to the destination, you have a problem.
• Snt, number of packets sent.
• Last / Avg / Best / Wrst, latency for that hop.

Identify the hop where your traffic leaves the Chinese domestic network. It is the last hop whose hostname ends with .cn or contains a Chinese carrier name (Chinanet, CNC, Unicom, CMNET). After that, the next hop should have a name ending in .vn or contain vnpt, viettel, fpt or cmc. That hop is where the cable crosses.

Step 3, Using public looking glasses

If you do not have a shell on a machine in Guangzhou, Shenzhen or Shanghai, use a public looking glass that sits in one of those cities. Several Chinese carriers and academic networks operate web-based looking glasses that let you run ping or traceroute from a server inside China:

• China Telecom (Guangzhou node), URL varies; search for "China Telecom looking glass Guangzhou".
• China Unicom (Shanghai node), similar search.
• CERNET (Tsinghua University, Beijing), useful for education traffic patterns.
• Hetzner / DigitalOcean looking glass in Singapore, not helpful for China-to-Vietnam paths, but useful as a control. Ignore for this test.

Enter the Vietnam IP into the looking glass field. The tool will ping or traceroute from that node and show you the result. This gives you a datapoint from a different Chinese city than your own, combine it with your own measurement to build a picture.

Reading the path, domestic networks and Vietnam carriers

Vietnam has four major internet service providers that operate their own international cables and domestic backbone:

• VNPT (Vietnam Posts and Telecommunications Group), the incumbent. Routes through the AAG and SEA-ME-WE 3/5 cables. Common peer with China Telecom and China Unicom.
• Viettel (Vietnam Telecommunication Group), military-owned, largest market share. Has its own cable to Hong Kong and direct peering with China Unicom. Frequently the lowest latency from northern China.
• FPT Telecom, private, strong in the south. Routes through AAG and APG. Often cheaper but sometimes higher latency to northern Chinese cities.
• CMC Telecom, smaller, but has a Tier-3 datacenter and good peering with China Telecom.

When you read an mtr output, the jump from a chinanet.*.cn hop to a vnpt.*.vn hop tells you which cable the traffic used. If the Vietnam hop shows an IP that geolocates to Hong Kong, the traffic is landing there first and then crossing into Vietnam, expect an extra 10 to 15 ms.

For a cross-border China Vietnam business operation, understanding this path matters because latency is not symmetric. The return path (Vietnam → China) may use a different cable. You can see it by running mtr from the Vietnam VPS back to your Chinese IP.

Why you should run the test at different times

Latency between China and Vietnam fluctuates with load. A test at 2:00 AM Beijing time (low traffic) will be faster than one at 10:00 AM (peak business hours). The difference can be 20 to 40 ms. Run your mtr three times: 9:00 AM, 2:00 PM, and 10:00 PM in China time. The average of those three is your working latency. If you rely on the 2:00 AM low point, you will be disappointed during your afternoon conference call.

Choosing the right VPS for your Chinese team

Once you confirm that the latency works for your use case, say, 40 ms from Guangzhou to a Vietnam VPS, the next question is the machine itself. For teams operating across the border, a Windows VPS with a dedicated IPv4 in Vietnam is often the most practical setup. You RDP into a full desktop environment that stays online 24/7. Everyone on your team logs into the same stable instance, with their own accounts, from wherever they are. No VPN to maintain, no laptop that sleeps. The Vietnam IPv4 is the same every time, so your partners, your banking portals, your platforms see a consistent domestic Vietnamese address. The dedicated IPv4 means you can set rDNS, whitelist it in your API dashboards, and not share the address with anyone else.

A Linux VPS is the alternative, same network, same latency profile, if what you need is only SSH and command-line tools. Many cross-border China Vietnam teams now use a Windows VPS as their remote workstation and a Linux VPS for the backend servers, both in the same Vietnam datacenter.

Latency from specific Chinese cities, what to expect

These are typical ranges, not guarantees. Your carrier changes everything.

If you are in Guangdong or Yunnan, the geography works in your favour. From Kunming to Hanoi is less than 400 km by cable; from Guangzhou about 900 km. The bulk of the delay is not the cable distance but the routing through carrier gateways. A Vietnam VPS for China business in Hanoi will give you 5 to 15 ms less latency than one in Ho Chi Minh City, purely because the submarine cables land in the north.

Troubleshooting high latency or packet loss

If your mtr shows >80 ms from Guangzhou to a Vietnam IP, something is wrong. Check these:

• The IP is behind a CDN. If you ping a domain and not a raw IP, the CDN may terminate in Hong Kong or Singapore. Always use a raw Vietnam IPv4 that points to a server you control.
• The carrier is routing via Europe. This sounds absurd but happens: China Telecom sometimes sends traffic to Vietnam via Frankfurt on certain BGP paths. If you see a German or UK hop, that is what is happening. You need to change your route by choosing a different carrier.
• Time of day. If it is 9:00 PM in China, the domestic network is under load. Retest at 6:00 AM.
• Your own local network. Test from a different machine (preferably a VPS inside China) to isolate whether the problem is your local router or the carrier. If a China-based VPS shows good latency but your office machine does not, your office connection is the bottleneck.

FAQ

Related articles

• Vietnam VPS vs Singapore VPS for serving Vietnamese users
• Why a Vietnam IPv4 matters when your users are in Vietnam
• Set up a VPS VPN for China users on Ubuntu 24.04
• How to connect to a Linux VPS for the first time via SSH