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

AWS latency check.

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

AWS latency check — browser-measured RTT to all 12 AWS regions using DynamoDB regional healthcheck endpoints.

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

AWS · 0 regions

measured from your browser · running… · sample size 3 · DynamoDB endpoints
us-east-1
N. Virginia
us-east-2
Ohio
us-west-1
N. California
us-west-2
Oregon
ca-central-1
Canada Central
sa-east-1
São Paulo
eu-west-1
Ireland
eu-west-2
London
eu-central-1
Frankfurt
ap-northeast-1
Tokyo
ap-southeast-1
Singapore
ap-south-1
Mumbai

// endpoint used

dynamodb.<region>.amazonaws.com returns a tiny ~40-byte healthy: ... response on GET / — the same low-overhead endpoint used by other public AWS latency probes. 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 — a few ms higher than raw ping, but the 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