GCP asia-east2 latency

Hong Kong. How long a round trip from your machine to this region takes — and how much of that distance alone demands.

The region

Cloud	Google Cloud
Region code	asia-east2
Region name	Hong Kong
Datacentre city	Hong Kong, HK
Coordinates	22.32, 114.17
Published IPv4 prefixes	11
Probe endpoint	https://storage.asia-east2.rep.googleapis.com/
Probe style	timed blind — the endpoint sends no CORS headers
Verification	Probed on this region’s dedicated regional storage endpoint — one address per region, no wildcard DNS — with identity confirmed by a single gcping call per sweep. The recorded range-check predates this endpoint and covered an earlier host. Checked 2026-08-21.

Coordinates are the real datacentre city rather than the marketing region name, because they feed the distance maths below.

Distance, and the floor it sets

Light in fibre covers about 100 km per millisecond of round trip. These are the great-circle distances to Hong Kong and the latency no network can beat — not a measurement, a limit. What you actually measure is this plus routing.

From	Distance	Floor
New York	12,956 km	130 ms
Los Angeles	11,650 km	116 ms
São Paulo	18,046 km	180 ms
London	9,623 km	96 ms
Frankfurt	9,158 km	92 ms
Johannesburg	10,719 km	107 ms
Dubai	5,955 km	60 ms
Mumbai	4,297 km	43 ms
Singapore	2,586 km	26 ms
Tokyo	2,876 km	29 ms
Sydney	7,376 km	74 ms

Other regions in this metro

Within 75 km of Hong Kong — near enough that distance sets no meaningful floor between them. When several sit in one city, the fastest is the city’s real floor; a slower neighbour is usually the endpoint’s own server time.

Measure it yourself

These figures are geometry. Your own round trip to asia-east2 depends on your connection and the route it takes — open the instrument, pick GCP, and sweep. Every region is timed from your browser against the endpoint listed above, and the result is split into the part physics demands and the part the network added.

See every GCP region on the GCP latency page.