GCP asia-south1 latency

Mumbai. 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	asia-south1
Region name	Mumbai
Datacentre city	Mumbai, India, IN
Coordinates	19.08, 72.88
Published IPv4 prefixes	32
Probe endpoint	https://storage.asia-south1.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 Mumbai, India 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	12,538 km	125 ms
Los Angeles	13,991 km	140 ms
São Paulo	13,774 km	138 ms
London	7,192 km	72 ms
Frankfurt	6,564 km	66 ms
Johannesburg	6,983 km	70 ms
Dubai	1,935 km	19 ms
Mumbai	1 km	under 0.5 ms
Singapore	3,904 km	39 ms
Tokyo	6,720 km	67 ms
Sydney	10,157 km	102 ms

Other regions in this metro

Within 75 km of Mumbai, India — 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 asia-south1 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.