GCP latency check.
Round-trip latency from your browser to Google Cloud regions. Hit in parallel, median ms reported. Click rerun for a fresh measurement.
GCP latency check — browser-measured RTT to Google Cloud regions using BigQuery regional endpoints.Measured live from your browser to 0 GCP region endpoints. Three samples per region in parallel, fetch(no-cors) + median ms reported, four-second timeout.
GCP · 0 regions
// endpoint used
<region>-bigquery.googleapis.com — the regional BigQuery frontend. Unauth GET / returns 404 quickly, but the TLS handshake still reaches the region-routed edge, which is what we time.
// what it measures
Per region: 4 sequential samples, first discarded as TLS warm-up, median of the remaining 3 reported. Numbers approximate TCP + TLS + first-byte time. Relative ordering between regions is accurate.
// what it doesn't
We don't persist runs, send your IP anywhere, or compare inter-region paths. For serious benchmarking, mtr beats browser fetch timing every time.