region·latency

GCP europe-central2 latency

Warsaw. 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-central2
Region nameWarsaw
Datacentre cityWarsaw, Poland, PL
Coordinates52.23, 21.01
Published IPv4 prefixes8
Probe endpointhttps://storage.europe-central2.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 Warsaw, Poland and the latency no network can beat — not a measurement, a limit. What you actually measure is this plus routing.

FromDistanceFloor
New York6,855 km69 ms
Los Angeles9,637 km96 ms
São Paulo10,660 km107 ms
London1,449 km14 ms
Frankfurt890 km8.9 ms
Johannesburg8,748 km87 ms
Dubai4,156 km42 ms
Mumbai5,781 km58 ms
Singapore9,400 km94 ms
Tokyo8,577 km86 ms
Sydney15,594 km156 ms

Other regions in this metro

Within 75 km of Warsaw, Poland — 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-central2 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.