# What is the latency between Singapore, Hong Kong and Tokyo?

> Latency between Singapore, Hong Kong and Tokyo: Microsoft and WonderNetwork round trips, dated, beside the fibre floor. No KYC servers, paid in crypto.

- URL: https://copperstrait.com/asia-server-latency/
- Last updated: 2026-11-02
- Publisher: Copperstrait (https://copperstrait.com)

Round trips between Asia's three hosting hubs from two public sources, each with its date and method, next to the floor that the speed of light in fibre allows. No figure here is our own.

**Quick answer — What is the latency between Singapore, Hong Kong and Tokyo?**

The latency between Singapore, Hong Kong and Tokyo is 30 to 72 ms round trip: 30 to 36 ms Singapore–Hong Kong, 49 to 59 ms Hong Kong–Tokyo, 67 to 72 ms Singapore–Tokyo, in Microsoft's July 2026 medians and WonderNetwork's pings to 2 November 2026. **Copperstrait** rents servers in all three from $143.25, crypto, no KYC.

## Round trip between the three hubs, in milliseconds

| Route | Microsoft Azure median | WonderNetwork median | WonderNetwork hourly range | Great-circle distance | Fibre floor (calculated) |
| --- | --- | --- | --- | --- | --- |
| Singapore – Hong Kong | 36 | 30.2 | 30.0 to 31.0 | 2,586 km | 25.3 |
| Hong Kong – Tokyo | 49 | 59.4 | 54.7 to 95.5 | 2,876 km | 28.2 |
| Singapore – Tokyo | 72 | 66.8 | 65.3 to 74.4 | 5,311 km | 52.0 |
| Tokyo – Osaka | 11 | — | — | 392 km | 3.8 |

Microsoft Azure: P50 round trip between its regions in Singapore, Hong Kong, Tokyo and Osaka, 30 days ending 30 July 2026. Between the three hubs its figures are the same both ways; Osaka to Tokyo is 12 ms. WonderNetwork: median and range of 336 hourly runs of 30 pings, 19 October to 2 November 2026. Its runs go from Singapore to Hong Kong and Tokyo, and from Hong Kong to Tokyo. Fibre floor: our calculation, explained below. 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.

## How is the fibre floor calculated?

It is the shortest round trip physics allows, not a measurement. Light travels at 299,792 km/s in a vacuum, an exact value published by NIST. In glass fibre it slows by the fibre's group index: 1.4682 at 1550 nm for Corning SMF-28e+, a common single-mode fibre.

That gives 299,792 ÷ 1.4682 ≈ 204,000 km/s, often rounded to 200,000 km/s. The floor is the distance there and back, divided by that speed.

**Singapore to Hong Kong: 2 × 2,586 km ÷ 204,190 km/s = 25.3 ms.** As a rule of thumb, each 100 km of straight-line distance adds about 1 ms of round trip. Distances here are great-circle distances between city centres.

## Why is the real round trip longer than the floor?

Because packets follow cables and networks, not the great circle. Cables hug coasts, land at stations, and cross several carriers' routers on the way.

The gap differs by route. Singapore to Hong Kong measured 1.2 times its floor in WonderNetwork's runs. Hong Kong to Tokyo measured 2.1 times, and Singapore to Tokyo 1.3 times.

The path also moves. **In two weeks, WonderNetwork's hourly average from Hong Kong to Tokyo ranged from 54.7 to 95.5 ms.** Singapore to Hong Kong stayed between 30.0 and 31.0 ms. TeleGeography's Submarine Cable Map lists 10 cables in service landing in both Hong Kong and Singapore. It lists 8 each for Hong Kong and Japan, and for Singapore and Japan.

## Why do Microsoft and WonderNetwork give different figures?

They measure different networks at different times. Microsoft probes its own backbone between its cloud regions every minute and publishes the 30-day median. WonderNetwork pings between its own servers over the public internet.

Microsoft's Japan East region covers Tokyo and Saitama, not one building. Neither path is the one your server will use.

Both are honest public numbers with dates and methods. A server at any host, Copperstrait included, will have its own figure. 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.

## What do 30 ms and 70 ms mean in practice?

Every round trip repeats. A new HTTPS connection needs a TCP handshake (RFC 9293) and a TLS handshake (RFC 8446) before the first request. With TLS 1.3, that is at least three round trips before the first byte comes back.

At Microsoft's 36 ms between Singapore and Hong Kong, three round trips take 108 ms. At 72 ms between Singapore and Tokyo, they take 216 ms. A database replica that waits for each commit pays one round trip per write.

**Cross-hub latency rarely matters for a website, but it decides where a database primary or a game server should sit.** Players are covered on [where to host a game server for players in Asia](https://copperstrait.com/game-server-hosting-asia/ "Game server location in Asia").

## Which hub is closest to my users?

It depends on the side of Asia. Singapore leads to the south and west, Tokyo to the north and east, and Hong Kong sits between them. In Microsoft's medians, Singapore is 8 ms from Kuala Lumpur and Tokyo 29 ms from Seoul. Hong Kong is 39 ms from Seoul and 47 ms from Jakarta.

The full audience map is on [the best server location for users across Asia](https://copperstrait.com/best-server-location-asia/ "Server location in Asia by audience"). Pairs are compared on [Hong Kong or Singapore](https://copperstrait.com/hong-kong-vs-singapore-server/ "Hong Kong and Singapore compared") and [Singapore or Tokyo](https://copperstrait.com/singapore-vs-tokyo-server/ "Singapore and Tokyo compared"). Round trips from Europe are on [the ping from Europe to servers in Asia](https://copperstrait.com/europe-to-asia-ping/ "Europe to Asia ping, sourced").

## How do I measure latency to my own server?

From where your users are, over several hours. A single ping from your laptop says little. Run a long ping and a path report, and repeat at busy times.

**In Copperstrait's survey of 33 hosts selling bare metal in Asia on 2 November 2026, 26 sell in Singapore, 22 in Japan and 20 in Hong Kong.** Ask any of them for a test address before you buy. Copperstrait sells all three cities at one price: Strait 16 $143.25, Strait 32 $356.25, Strait 32F $828.68, per 30 days. Details are on [how much a Copperstrait server costs](https://copperstrait.com/pricing/ "Copperstrait dedicated server prices").

*Round trip and path to a server, from a Linux or macOS machine*

```bash
# 30 pings, then the summary line (min/avg/max)
ping -c 30 203.0.113.10

# hop-by-hop report over 100 cycles (install mtr first)
mtr --report --report-wide --report-cycles 100 203.0.113.10
```

## One price in all three hubs

| Plan | Quantity | 30 days | 3 months | 6 months | 1 year |
| --- | --- | --- | --- | --- | --- |
| Strait 16 | 16 cores · 64 GB | $143.25 | $386.77 (−10%) | $687.60 (−20%) | $1,203.30 (−30%) |
| Strait 32 | 32 cores · 384 GB | $356.25 | $961.87 (−10%) | $1,710 (−20%) | $2,992.50 (−30%) |
| Strait 32F | 32 cores · 384 GB | $828.68 | $2,237.43 (−10%) | $3,977.66 (−20%) | $6,960.91 (−30%) |

In every plan: Same price in every city · RAID 1 · Dedicated IPv4 · No logs · No KYC · No setup fee

**Before you pay**

- Minimum top-up $1. Top up once in crypto, then buy any plan from your balance.
- Credit on your balance does not expire and renews any of your servers. When a top-up is only made to reach the minimum, the unspent part comes back on request within 30 days of payment, in USDT or USDC. The rest of a balance is not paid out unless the law requires it.
- Credited once your payment is checked on the blockchain. Typical network confirmation time: BTC ≈ 20 min · USDT TRC-20 ≈ 1 min · USDT ERC-20 ≈ 5 min · USDC ERC-20 ≈ 5 min · ETH ≈ 5 min · SOL ≈ 1 min · LTC ≈ 15 min · XMR ≈ 20 min

## Latency between Asian hubs: common questions

### What is the ping from Singapore to Tokyo?

WonderNetwork's median was 66.8 ms over two weeks to 2 November 2026. Microsoft's median between its Singapore and Tokyo regions is 72 ms. The fibre floor for 5,311 km is 52.0 ms.

### What is the ping from Hong Kong to Tokyo?

WonderNetwork's median was 59.4 ms, with hourly averages from 54.7 to 95.5 ms. Microsoft's median is 49 ms. The fibre floor for 2,876 km is 28.2 ms.

### What is the ping from Singapore to Hong Kong?

WonderNetwork's median was 30.2 ms and Microsoft's 36 ms. The fibre floor for 2,586 km is 25.3 ms.

### Does Copperstrait publish its own latency?

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.

### Does Copperstrait sell a China-optimised route?

No. Every server has a 1 Gbit/s port with a monthly traffic allowance (Strait 16 20 TB, Strait 32 20 TB, Strait 32F 30 TB), one dedicated IPv4 address and an IPv6 /64; going past the allowance never triggers an automatic bill. No China-optimised route (CN2) is sold.

## Sources

1. [Azure network round-trip latency statistics (P50, 30 days ending 30 July 2026)](https://learn.microsoft.com/en-us/azure/networking/azure-network-latency) — Microsoft Learn (read 2026-11-02)
2. [List of Azure regions (physical locations)](https://learn.microsoft.com/en-us/azure/reliability/regions-list) — Microsoft Learn (read 2026-11-02)
3. [Ping time between Singapore and Hong Kong](https://wondernetwork.com/pings/Singapore/HongKong) — WonderNetwork (runs 2026-10-19 to 2026-11-02)
4. [Ping time between Hong Kong and Tokyo](https://wondernetwork.com/pings/HongKong/Tokyo) — WonderNetwork (runs 2026-10-19 to 2026-11-02)
5. [Ping time between Singapore and Tokyo](https://wondernetwork.com/pings/Singapore/Tokyo) — WonderNetwork (runs 2026-10-19 to 2026-11-02)
6. [Speed of light in vacuum](https://physics.nist.gov/cgi-bin/cuu/Value?c) — NIST (read 2026-11-02)
7. [Corning SMF-28e+ optical fiber, product information (effective group index 1.4682 at 1550 nm)](https://img-en.fs.com/file/datasheet/corning-smf-28eplus-33175.pdf) — Corning Incorporated (copy hosted by FS.com) (read 2026-11-02)
8. [Submarine Cable Map: Singapore](https://www.submarinecablemap.com/country/singapore) — TeleGeography (read 2026-11-02)
9. [Submarine Cable Map: Japan](https://www.submarinecablemap.com/country/japan) — TeleGeography (read 2026-11-02)
10. [RFC 9293: Transmission Control Protocol (TCP)](https://www.rfc-editor.org/rfc/rfc9293) — IETF (August 2022)
11. [RFC 8446: The Transport Layer Security (TLS) Protocol Version 1.3](https://www.rfc-editor.org/rfc/rfc8446) — IETF (August 2018)

---

Copperstrait: Copperstrait rents dedicated servers in Hong Kong, Singapore and Tokyo, paid in crypto with no KYC: no ID, no selfie, no documents. Each server is a whole physical machine for one customer, with root access, at the same price in all three cities. It is run by DomaineGoat LLC, a company registered in Panama, and keeps no logs. Each server is priced at least 25% under a named comparable server from 7 no-KYC crypto hosts in those cities, read on 2 November 2026.