region·latency

GCP europe-southwest1 latency

Madrid. 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 codeeurope-southwest1
Region nameMadrid
Datacentre cityMadrid, Spain, ES
Coordinates40.42, -3.70
Published IPv4 prefixes9
Probe endpointhttps://storage.europe-southwest1.rep.googleapis.com/
Probe styletimed blind — the endpoint sends no CORS headers
VerificationProbed 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 Madrid, Spain and the latency no network can beat — not a measurement, a limit. What you actually measure is this plus routing.

FromDistanceFloor
New York5,768 km58 ms
Los Angeles9,363 km94 ms
São Paulo8,385 km84 ms
London1,264 km13 ms
Frankfurt1,446 km14 ms
Johannesburg8,102 km81 ms
Dubai5,656 km57 ms
Mumbai7,532 km75 ms
Singapore11,381 km114 ms
Tokyo10,761 km108 ms
Sydney17,685 km177 ms

Other regions in this metro

Within 75 km of Madrid, Spain — 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 europe-southwest1 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.