GCP europe-west10 latency

Berlin. 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	europe-west10
Region name	Berlin
Datacentre city	Berlin, Germany, DE
Coordinates	52.52, 13.40
Published IPv4 prefixes	4
Probe endpoint	https://storage.europe-west10.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 Berlin, Germany 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	6,385 km	64 ms
Los Angeles	9,310 km	93 ms
São Paulo	10,253 km	103 ms
London	932 km	9.3 ms
Frankfurt	424 km	4.2 ms
Johannesburg	8,868 km	89 ms
Dubai	4,625 km	46 ms
Mumbai	6,286 km	63 ms
Singapore	9,916 km	99 ms
Tokyo	8,915 km	89 ms
Sydney	16,095 km	161 ms

Other regions in this metro

Within 75 km of Berlin, Germany — 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-west10 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.