region·latency

GCP europe-west12 latency

Turin. 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-west12
Region nameTurin
Datacentre cityTurin, Italy, IT
Coordinates45.07, 7.69
Published IPv4 prefixes11
Probe endpointhttps://storage.europe-west12.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 Turin, Italy and the latency no network can beat — not a measurement, a limit. What you actually measure is this plus routing.

FromDistanceFloor
New York6,380 km64 ms
Los Angeles9,669 km97 ms
São Paulo9,403 km94 ms
London919 km9.2 ms
Frankfurt565 km5.7 ms
Johannesburg8,190 km82 ms
Dubai4,771 km48 ms
Mumbai6,587 km66 ms
Singapore10,382 km104 ms
Tokyo9,821 km98 ms
Sydney16,680 km167 ms

Other regions in this metro

Within 75 km of Turin, Italy — 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-west12 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.