Where should your app live?

Measure the latency from where you are to 18 cloud regions around the world. Find the region closest to your users — and how many milliseconds the wrong choice adds to every request.

18 AWS regions · 5 continents
Median of real requests
Latency test≈ 20 seconds
Samples per regionMore samples give a steadier median.
Regions
How to read latency
< 50 msFeels instant. Ideal for real-time apps.
50–100 msFast. Fine for any business app.
100–200 msNoticeable. Use a CDN and cache.
> 200 msSlow. Avoid serving users from here.

Each value is the median time of an HTTPS round trip from your browser to a health endpoint in that region, after the connection is open.

Closest region
—

Press Start test to measure latency to every region.

Choosing regions, CDN and architecture for a global product?Talk to an engineer →

Latency varies with your network, Wi-Fi and time of day. Run the test from where your users actually are.

Real round trips, region by region.

Your browser calls a lightweight health endpoint in each cloud region several times. We report the median, which ignores occasional spikes.

Connection first

The first request to each region opens the connection (DNS, TCP, TLS) and is discarded — your users pay that cost once, not on every call.

Samples

Then 3, 5 or 10 requests in sequence. The median of those is the latency shown.

Parallelism

Three regions are measured at a time, so the test is quick without competing with itself.

Why it matters

Latency adds up: a screen that makes 10 sequential API calls pays the round trip 10 times. Choosing the right region is often the cheapest performance win there is.

Frequently asked questions

What is the difference between latency and speed?

Speed (bandwidth) is how much data per second your connection carries. Latency is how long a single round trip takes. Business apps make many small requests, so latency usually matters more than bandwidth.

How do I choose a cloud region for my application?

Host your API and database in the region with the lowest latency to most of your users, then check data residency rules (such as LGPD or GDPR) and service availability. Serve static files from a CDN.

What latency is acceptable for a web application?

Under 100 ms per round trip feels fast for business applications. Between 100 and 200 ms it starts to show, especially on screens that make several calls. Above 200 ms you need caching, a CDN or a closer region.

You bring the problem. We figure out what needs to be built.

Tell us what’s happening in your operation, the product you want to create or the system that needs to evolve. Our first conversation starts with the problem — not the technology.

Talk to Kordis