Google Cloud latency test

Is this a GCP ping?

An ICMP echo needs a raw socket, which browsers never expose to JavaScript, so a GCP ping from a web page is something else. Almost every region here is timed on its own regional Cloud Storage endpoint — a dedicated address per region rather than one shared frontend; the single exception is named below. The community gcping service answers a related question with Cloud Run instances, and is asked here once per region per sweep, purely to confirm which region replied.

How GCP is probed

Timed on storage.{region}.rep.googleapis.com, which terminates inside the region — its handshake tracks real distance where the gcping frontend answers in 8 ms from anywhere. Each region has a dedicated address and no wildcard DNS, so a made-up region name does not resolve. Identity is then confirmed by one call to gcping, whose reply is the region code.

One exception: asia-southeast3 has no regional endpoint yet and is still timed against the shared gcping frontend, so its figure reflects Google’s nearest edge rather than the region.

The first request of a sweep is discarded — it pays for DNS, TCP and TLS — so every sample after it is essentially one round trip, and the reported figure is the fastest of them.

Every GCP region

Prefix counts come from GCP’s own published feed. Each region links to its distance, its physical floor and the endpoint used to time it.

Measure it yourself

Open the instrument, select GCP, choose regions and run a sweep. Nothing is pre-selected and nothing runs until you press the button.