We loaded supabase.com from Amsterdam, Montreal, San Francisco and Singapore — 20 times each — and measured how long it actually took. If you're building on Supabase, here's what your users around the world would experience.
Independent measurement by LatencyRadar. Not affiliated with Supabase.
Supabase loaded fast and reliably in every city we tested. Every request came back successfully, and the typical load time was under 50 ms globally — comfortably in the 'users won't notice' range. The most interesting finding is how evenly matched all four regions were. Unlike a lot of services where one city is dramatically slower, Supabase stayed tight across the board.
A standard page load from four cities, repeated 20 times each. Supabase is a popular backend platform for indie hackers and vibe coders, so knowing how fast it loads globally is useful whether you're building on it or just curious how it compares to the competition.
Everywhere — and more evenly than most services we've tested. Montreal was the fastest at 41 ms, San Francisco and Singapore were nearly identical at 47–49 ms, and Amsterdam was slightly slower but still well under 100 ms. There's no region where Supabase feels noticeably slow.
Montreal came in fastest at 41 ms typical. San Francisco and Singapore were almost tied at 47 ms and 49 ms. Amsterdam was the slowest at 67 ms typical, and occasionally spiked to 354 ms on a bad request — that's the one number worth watching. Every other region was rock solid, with worst-case times staying well under 200 ms.
DNS lookup was instant in every city — not worth thinking about. Most of the time is split between the server preparing the response and the security handshake. That's a normal, healthy pattern for a well-run service. It means Supabase isn't wasting time on anything obvious — what you're seeing is just the physics of the network.
Start with the headline number for each city. Open the technical breakdown only if you want to see where that time is coming from.
20 requests · 100% successful
20 requests · 100% successful
20 requests · 100% successful
20 requests · 100% successful
The typical load time tells you what most requests look like. But every so often a request is slower — and that's the one your user notices. Amsterdam's typical time was 67 ms, which is fine. But occasionally it hit 354 ms. That's not a dealbreaker, but it's the kind of thing worth knowing before you assume your European users are having the same experience as everyone else.
We made a standard page request to supabase.com from servers in 4 cities: Amsterdam, Montreal, San Francisco and Singapore. Each city ran 20 requests. We measured how long each step took — DNS lookup, connecting, security handshake, server response, and download — then calculated typical and worst-case times from the results.
This test measured supabase.com itself — but your actual database and API endpoints are a different story. Run a free speed test and find out where your users are really waiting.
Takes about 30 seconds.