region·latency

GCP me-west1 latency

Tel Aviv. 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 codeme-west1
Region nameTel Aviv
Datacentre cityTel Aviv, Israel, IL
Coordinates32.09, 34.78
Published IPv4 prefixes12
Probe endpointhttps://storage.me-west1.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 Tel Aviv, Israel and the latency no network can beat — not a measurement, a limit. What you actually measure is this plus routing.

FromDistanceFloor
New York9,115 km91 ms
Los Angeles12,138 km121 ms
São Paulo10,622 km106 ms
London3,557 km36 ms
Frankfurt2,938 km29 ms
Johannesburg6,520 km65 ms
Dubai2,137 km21 ms
Mumbai4,060 km41 ms
Singapore7,962 km80 ms
Tokyo9,156 km92 ms
Sydney14,180 km142 ms

Other regions in this metro

Within 75 km of Tel Aviv, Israel — 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 me-west1 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.