region·latency

GCP asia-southeast2 latency

Jakarta. 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 codeasia-southeast2
Region nameJakarta
Datacentre cityJakarta, Indonesia, ID
Coordinates-6.21, 106.85
Published IPv4 prefixes16
Probe endpointhttps://storage.asia-southeast2.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 Jakarta, Indonesia and the latency no network can beat — not a measurement, a limit. What you actually measure is this plus routing.

FromDistanceFloor
New York16,178 km162 ms
Los Angeles14,450 km144 ms
São Paulo15,629 km156 ms
London11,718 km117 ms
Frankfurt11,119 km111 ms
Johannesburg8,587 km86 ms
Dubai6,576 km66 ms
Mumbai4,663 km47 ms
Singapore905 km9.1 ms
Tokyo5,782 km58 ms
Sydney5,496 km55 ms

Other regions in this metro

Within 75 km of Jakarta, Indonesia — 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-southeast2 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.