GCP me-central1 latency

Doha. 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	me-central1
Region name	Doha
Datacentre city	Doha, Qatar, QA
Coordinates	25.29, 51.53
Published IPv4 prefixes	6
Probe endpoint	https://storage.me-central1.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 Doha, Qatar 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	10,773 km	108 ms
Los Angeles	13,329 km	133 ms
São Paulo	11,871 km	119 ms
London	5,214 km	52 ms
Frankfurt	4,577 km	46 ms
Johannesburg	6,255 km	63 ms
Dubai	376 km	3.8 ms
Mumbai	2,301 km	23 ms
Singapore	6,198 km	62 ms
Tokyo	8,244 km	82 ms
Sydney	12,383 km	124 ms

Other regions in this metro

Within 75 km of Doha, Qatar — 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.

Azure qatarcentral0 km

Measure it yourself

These figures are geometry. Your own round trip to me-central1 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.