Latency · United States to Asia
Round trips from twelve North American cloud regions to Asia's three hosting hubs, from Microsoft's published medians, set beside the physical floor and the Pacific cables that carry the traffic.
Quick answer
What is the ping from the US to servers in Asia?
The ping from the US to servers in Asia is 101 to 162 ms to Tokyo in Microsoft's July 2026 medians, 141 to 204 ms to Hong Kong and 162 to 228 ms to Singapore. Tokyo is closest from every US region listed. Copperstrait rents servers in all three at one price, from $143.25 per 30 days, crypto, no KYC.
| From | Azure region | To Tokyo | To Hong Kong | To Singapore |
|---|---|---|---|---|
| Washington state | West US 2 | 101 | 141 | 162 |
| California | West US | 108 | 148 | 170 |
| Phoenix, Arizona | West US 3 | 112 | 156 | 183 |
| Wyoming | West Central US | 122 | 162 | 184 |
| Texas | South Central US | 129 | 173 | 202 |
| Iowa | Central US | 136 | 176 | 198 |
| Querétaro State, Mexico | Mexico Central | 145 | 189 | 218 |
| Illinois | North Central US | 148 | 188 | 209 |
| Virginia | East US 2 | 161 | 204 | 228 |
| Toronto, Canada | Canada Central | 161 | 201 | 223 |
| Virginia | East US | 162 | 203 | 224 |
| Quebec, Canada | Canada East | 170 | 210 | 231 |
Microsoft Azure: P50 round trip over the 30 days ending 30 July 2026, from each North American region to Japan East (Tokyo, Saitama), East Asia (Hong Kong) and Southeast Asia (Singapore). Places are the physical locations Microsoft lists for each region. These are not Copperstrait figures: We publish no latency or speed figures of our own: we have not measured them. Test from where your users are once the server is yours.
Tokyo, from every region in the table. From the United States, Asia starts in Tokyo: each US region in Microsoft's table reaches Tokyo about 40 ms sooner than Hong Kong and 60 to 70 ms sooner than Singapore.
From Washington state, the medians are 101 ms to Tokyo, 141 ms to Hong Kong and 162 ms to Singapore. From Virginia, they are 162, 203 and 224 ms. The gaps hardly move across the country: Hong Kong adds 40 to 44 ms over Tokyo, and Singapore 61 to 73 ms.
Europe sees the opposite order, with Singapore first and Tokyo last. Those figures are on the ping from Europe to servers in Asia.
About 60 ms. In Microsoft's medians, Virginia sits 61 ms further from Tokyo than Washington state (162 against 101 ms). It is 62 ms further from Hong Kong and 62 ms further from Singapore.
The interior falls in between. Texas reaches Tokyo in 129 ms, Iowa in 136 ms and Illinois in 148 ms. Toronto (161 ms) lines up with Virginia, and Querétaro in Mexico (145 ms) with Illinois.
A US team on the Pacific coast is about a tenth of a second from Tokyo; on the Atlantic coast, about a sixth.
About 75 ms to Tokyo from Seattle, for a straight fibre that nobody has laid. The method: take the great-circle distance between two city centres, double it for the return leg, and divide by the speed of light in glass. Light covers 299,792 km/s in a vacuum; in Corning SMF-28e+ fibre, with a group index of 1.4682, that drops to about 204,190 km/s.
Microsoft names states, not cities. Each pair below therefore uses a city we chose inside that state, so the comparison is approximate. Measured medians run 1.23 to 1.58 times the floor: cables bend around coasts and pass through landing stations and routers.
| Route | Great-circle distance | Fibre floor | Microsoft median | Median ÷ floor |
|---|---|---|---|---|
| Seattle – Tokyo (West US 2) | 7,700 km | 75.4 | 101 | 1.34 |
| Los Angeles – Tokyo (West US) | 8,819 km | 86.4 | 108 | 1.25 |
| Dallas – Tokyo (South Central US) | 10,401 km | 101.9 | 129 | 1.27 |
| Chicago – Tokyo (North Central US) | 10,141 km | 99.3 | 148 | 1.49 |
| Ashburn, Virginia – Tokyo (East US) | 10,874 km | 106.5 | 162 | 1.52 |
| Los Angeles – Hong Kong (West US) | 11,649 km | 114.1 | 148 | 1.30 |
| Ashburn, Virginia – Singapore (East US) | 15,521 km | 152.0 | 224 | 1.47 |
Fibre floor: 2 × distance ÷ 204,190 km/s, our calculation from city-centre coordinates. Microsoft: P50, 30 days ending 30 July 2026, from the Azure region in brackets.
The shortest ones land in Japan. TeleGeography's cable map lists, among others:
The direct routes to Singapore are recent and long. With both in service, Microsoft's July 2026 medians still put Singapore 61 to 73 ms behind Tokyo from every US region.
It matters for the people who use the server more than for the people who run it. Managing a Tokyo machine from Virginia at 162 ms works: each keystroke over SSH echoes about a sixth of a second late.
Serving US visitors from Asia costs more. Before the first byte of a page, a browser spends one round trip on the TCP handshake, one on the TLS 1.3 handshake and one on the request itself. From Virginia to Singapore, three times 224 ms is close to 0.7 seconds.
Put the server near its users: an Asian audience on an Asian server, a US audience on a US one. For an audience on both sides of the Pacific, read whether to use a CDN or a server in Asia.
Pick by the users first, then by the people running the machine. Tokyo serves Japan and Korea and is also the closest hub to every US office. Singapore serves Southeast Asia and India; Hong Kong serves Taiwan and the Philippines. The audience map is on the best server location for users across Asia, and the round trips between the hubs on the latency between Singapore, Hong Kong and Tokyo.
Tokyo often costs more. In Copperstrait's survey of 2 November 2026, MonoVM charged $478 a month for its AMD EPYC 7302 server in Tokyo, against $191 in Singapore. Copperstrait charges one price in every city: Strait 16 $143.25, Strait 32 $356.25, Strait 32F $828.68 per 30 days. See renting a dedicated server in Tokyo, Japan and how much a Copperstrait server costs.
16 cores · 64 GB
$143.25
$128.92 / month
$386.77 for 3 months
$114.60 / month
$687.60 for 6 months
$100.28 / month
$1,203.30 for 1 year
3 months $386.77 (−10%)6 months $687.60 (−20%)1 year $1,203.30 (−30%)
Best value
32 cores · 384 GB
$356.25
$320.62 / month
$961.87 for 3 months
$285 / month
$1,710 for 6 months
$249.38 / month
$2,992.50 for 1 year
3 months $961.87 (−10%)6 months $1,710 (−20%)1 year $2,992.50 (−30%)
32 cores · 384 GB
$828.68
$745.81 / month
$2,237.43 for 3 months
$662.94 / month
$3,977.66 for 6 months
$580.08 / month
$6,960.91 for 1 year
3 months $2,237.43 (−10%)6 months $3,977.66 (−20%)1 year $6,960.91 (−30%)
In every plan: Same price in every city · RAID 1 · Dedicated IPv4 · No logs · No KYC · No setup fee
Microsoft's median from its California region (West US) to Tokyo was 108 ms over the 30 days to 30 July 2026. The fibre floor from Los Angeles is 86.4 ms.
224 ms from Microsoft's Virginia region (East US) and 228 ms from East US 2, in July 2026 medians. The fibre floor from Ashburn, Virginia, is 152.0 ms.
141 to 204 ms in Microsoft's July 2026 medians: 141 ms from Washington state and 203 ms from Virginia. Hong Kong sits 40 to 44 ms behind Tokyo from every US region.
For reaching the server from the US, Tokyo: it is 61 to 73 ms closer. For users in Southeast Asia or India, Singapore still wins, because their round trip matters more than the admin's.
No. We publish no latency or speed figures of our own: we have not measured them. Test from where your users are once the server is yours.
Hong Kong · Singapore · Tokyo from $143.25
Pick a port