region·latency

GCP asia-southeast3 latency

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

The region

CloudGoogle Cloud
Region codeasia-southeast3
Region nameBangkok
Datacentre cityBangkok, Thailand, TH
Coordinates13.76, 100.50
Published IPv4 prefixes4
Probe endpointhttps://asia-southeast3-5tkroniexa-eu.a.run.app/api/ping
Probe styletimed blind — the endpoint sends no CORS headers
VerificationNo regional storage endpoint exists for this region yet, so it is timed against the shared gcping frontend — which answers from Google’s nearest edge. Its round trip does not reflect the distance below.

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 Bangkok, Thailand and the latency no network can beat — not a measurement, a limit. What you actually measure is this plus routing.

FromDistanceFloor
New York13,932 km139 ms
Los Angeles13,303 km133 ms
São Paulo16,395 km164 ms
London9,532 km95 ms
Frankfurt8,967 km90 ms
Johannesburg8,998 km90 ms
Dubai4,885 km49 ms
Mumbai3,001 km30 ms
Singapore1,427 km14 ms
Tokyo4,599 km46 ms
Sydney7,537 km75 ms

Other regions in this metro

Within 75 km of Bangkok, Thailand — 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-southeast3 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.

This region is the one exception on its cloud: without a regional endpoint, what you measure is the distance to Google’s nearest edge, not to this city.

See every GCP region on the GCP latency page.