region·latency

GCP us-west2 latency

Los Angeles. 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 codeus-west2
Region nameLos Angeles
Datacentre cityLos Angeles, California, US
Coordinates34.05, -118.24
Published IPv4 prefixes19
Probe endpointhttps://storage.us-west2.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 Los Angeles, California and the latency no network can beat — not a measurement, a limit. What you actually measure is this plus routing.

FromDistanceFloor
New York3,935 km39 ms
Los Angeles0 kmunder 0.5 ms
São Paulo9,907 km99 ms
London8,755 km88 ms
Frankfurt9,303 km93 ms
Johannesburg16,674 km167 ms
Dubai13,391 km134 ms
Mumbai13,991 km140 ms
Singapore14,121 km141 ms
Tokyo8,819 km88 ms
Sydney12,074 km121 ms

Other regions in this metro

Within 75 km of Los Angeles, California — 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 us-west2 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.