// /digitalocean-latency-check · 0 regions · live

DigitalOcean latency check.

Round-trip latency from your browser to DigitalOcean regions. Hit in parallel, median ms reported. Click rerun for a fresh measurement.

DigitalOcean latency check — browser-measured RTT to DigitalOcean regions using Spaces (S3-compatible) regional endpoints.

Measured live from your browser to 0 DigitalOcean region endpoints. Three samples per region in parallel, fetch(no-cors) + median ms reported, four-second timeout.

Digital Ocean · 0 regions

measured from your browser · running… · sample size 3 · Spaces endpoints
nyc3
New York 3
sfo3
San Francisco 3
tor1
Toronto 1
ams3
Amsterdam 3
fra1
Frankfurt 1
lon1
London 1
sgp1
Singapore 1
blr1
Bangalore 1

// endpoint used

<region>.digitaloceanspaces.com — Spaces is DigitalOcean's S3-compatible object store, with one hostname per region. Hit with fetch(no-cors).

// 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.

Need more network tools?
/netops has the rest.

open netops