Benchmark report
Is supabase.com slow?
Page load times from 6 cities
Fast globally
Supabase responds quickly from all 6 test locations. Montreal was fastest at 58 ms; Amsterdam took 95 ms.
- Fastest
- 58 ms
- Montreal
- Slowest
- 95 ms
- Amsterdam
- Successful requests
- 100%
- 6 locations
Response time around the world
Montreal
58 msTokyo
62 msMumbai
64 msSingapore
70 msSan Francisco
74 msAmsterdam
95 ms
Fast everywhere, Amsterdam a little behind
Every city got the homepage from a Vercel server close by: Frankfurt for Amsterdam, and local ones in San Francisco, Montreal, Singapore, Tokyo and Mumbai. The typical times stay between 58 and 95 ms. Amsterdam is the slowest, and in the controlled run of 4 October its secure connection took 21 ms against 6 to 13 ms elsewhere, and its download 20 ms against 8 to 14 ms. None of this reaches a Supabase project: your database and API run in the region you picked when you created the project, and that region sets your users’ wait.
Click the location to see each stage.
Amsterdam96 ms
- Finding the server
- 11 ms
- Reaching the server
- 3 ms
- Setting up security
- 21 ms
- Waiting for the server: most of the time
- 52 ms
- Receiving the response
- 20 ms
- Total
- 96 ms
Finding the server is measured once per location, so it sits outside these bars. Open a city to see it.
Bars show the typical request, so the parts add up to its total. Why
Compare all locationsHide the comparison
Click a city to see its stage-by-stage breakdown.
Amsterdam96 ms
- Finding the server
- 11 ms
- Reaching the server
- 3 ms
- Setting up security
- 21 ms
- Waiting for the server: most of the time
- 52 ms
- Receiving the response
- 20 ms
- Total
- 96 ms
San Francisco73 ms
- Finding the server
- 13 ms
- Reaching the server
- 4 ms
- Setting up security
- 7 ms
- Waiting for the server: most of the time
- 48 ms
- Receiving the response
- 14 ms
- Total
- 73 ms
Montreal62 ms
- Finding the server
- 3 ms
- Reaching the server
- 5 ms
- Setting up security
- 9 ms
- Waiting for the server: most of the time
- 40 ms
- Receiving the response
- 8 ms
- Total
- 62 ms
Singapore79 ms
- Finding the server
- 4 ms
- Reaching the server
- 3 ms
- Setting up security
- 13 ms
- Waiting for the server: most of the time
- 52 ms
- Receiving the response
- 11 ms
- Total
- 79 ms
Tokyo64 ms
- Finding the server
- 1 ms
- Reaching the server
- 2 ms
- Setting up security
- 6 ms
- Waiting for the server: most of the time
- 47 ms
- Receiving the response
- 9 ms
- Total
- 64 ms
Mumbai58 ms
- Finding the server
- 4 ms
- Reaching the server
- 2 ms
- Setting up security
- 9 ms
- Waiting for the server: most of the time
- 37 ms
- Receiving the response
- 10 ms
- Total
- 58 ms
The phases come from the controlled run of 4 October 2026. Typical and slower times pool the daily requests. 6 of 6 test locations included: Amsterdam, San Francisco, Montreal, Singapore, Tokyo, Mumbai.
Finding the server is measured once per location, so it sits outside these bars. Open a city to see it.
Bars show the typical request, so the parts add up to its total. Why
Supabase still feels slow?
- Check Supabase’s status page
- Incidents with the platform or a project region are posted there. The homepage can be fine while a project is not.
- This is not a project benchmark
- Your project’s API, Auth, Realtime, Storage and Edge Functions live in the one region you chose when you created it. Distance to that region sets query time, and this page does not measure it.
- The homepage is served by Vercel
- supabase.com is cached at Vercel’s edge. A slow homepage points at Vercel’s edge for your location, not at Supabase’s database.
Response time over the last 30 days
Show the numbers
| Day | Amsterdam | San Francisco | Montreal | Singapore | Tokyo | Mumbai |
|---|---|---|---|---|---|---|
| 21 September 2026 | 112 ms | 80 ms | 56 ms | 72 ms | 69 ms | 62 ms |
| 22 September 2026 | 99 ms | 68 ms | 76 ms | 67 ms | 59 ms | 66 ms |
| 23 September 2026 | 99 ms | 70 ms | 58 ms | 69 ms | 62 ms | 63 ms |
| 24 September 2026 | 99 ms | 68 ms | 64 ms | 66 ms | 62 ms | 78 ms |
| 25 September 2026 | 103 ms | 81 ms | 62 ms | 67 ms | 52 ms | 68 ms |
| 26 September 2026 | 100 ms | 76 ms | 61 ms | 70 ms | 52 ms | 73 ms |
| 27 September 2026 | 93 ms | 90 ms | 59 ms | 64 ms | 55 ms | 58 ms |
| 28 September 2026 | 100 ms | 60 ms | 49 ms | 76 ms | 71 ms | 61 ms |
| 29 September 2026 | 112 ms | 69 ms | 70 ms | 81 ms | 57 ms | 66 ms |
| 30 September 2026 | 88 ms | 64 ms | 59 ms | 68 ms | 59 ms | 58 ms |
| 1 October 2026 | 97 ms | 75 ms | 62 ms | 82 ms | 64 ms | 62 ms |
| 2 October 2026 | 97 ms | 69 ms | 55 ms | 65 ms | 54 ms | 66 ms |
| 3 October 2026 | 140 ms | 105 ms | 64 ms | 70 ms | 65 ms | 56 ms |
| 4 October 2026 | 100 ms | 72 ms | 66 ms | 71 ms | 57 ms | 60 ms |
| 5 October 2026 | 104 ms | 78 ms | 64 ms | 63 ms | 57 ms | 62 ms |
| 6 October 2026 | 95 ms | 82 ms | 59 ms | 77 ms | 55 ms | 55 ms |
| 7 October 2026 | 95 ms | 90 ms | 65 ms | 71 ms | 54 ms | 74 ms |
| 9 October 2026 | 86 ms | 69 ms | 58 ms | 73 ms | 57 ms | 71 ms |
| 10 October 2026 | 95 ms | 65 ms | 51 ms | 64 ms | 75 ms | 74 ms |
| 11 October 2026 | 95 ms | 87 ms | 58 ms | 81 ms | 65 ms | 57 ms |
| 12 October 2026 | 86 ms | 79 ms | 53 ms | 64 ms | 70 ms | 69 ms |
| 13 October 2026 | 90 ms | 70 ms | 54 ms | 66 ms | 59 ms | 51 ms |
| 14 October 2026 | 101 ms | 77 ms | 53 ms | 77 ms | 60 ms | 68 ms |
| 15 October 2026 | 98 ms | 72 ms | 64 ms | 60 ms | 56 ms | 72 ms |
| 16 October 2026 | 92 ms | 75 ms | 58 ms | 118 ms | 55 ms | 65 ms |
| 17 October 2026 | 111 ms | 85 ms | 54 ms | 102 ms | 62 ms | 57 ms |
| 18 October 2026 | 97 ms | 71 ms | 59 ms | 72 ms | 67 ms | 67 ms |
| 19 October 2026 | 93 ms | 75 ms | 59 ms | 92 ms | 59 ms | 58 ms |
| 20 October 2026 | 93 ms | 70 ms | 60 ms | 65 ms | 56 ms | 61 ms |
About this measurement
GET supabase.com · 65 requests per location over 13 daily runs · 7 October 2026 to 20 October 2026
What we tested · Marketing website. The supabase.com marketing homepage, about 1.3 MB of HTML served from Vercel's cache, not from Supabase's own infrastructure.
How LatencyRadar measures response time →
Technical details
Doesn’t measure: Your project's API (PostgREST), Auth, Realtime, Storage or the management API. A control API surface is planned.
This page covers one Supabase surface: the supabase.com marketing homepage, about 1.3 MB of HTML that Vercel serves from its cache, not from Supabase’s own infrastructure. It shows how quickly that page reaches each of our cities. It says nothing about a Supabase project. A project’s API, Auth, Realtime, Storage and Edge Functions run in the region chosen when the project was created, so where your users are compared with that region decides their wait. We have not published a project measurement.
Between 7 and 20 October 2026 the typical time was 58 ms in Montreal, 62 ms in Tokyo, 64 ms in Mumbai, 70 ms in Singapore, 74 ms in San Francisco and 95 ms in Amsterdam. The daily medians stayed in a narrow band: Montreal between 51 and 65 ms, Mumbai between 51 and 74 ms and Amsterdam between 86 and 111 ms. Singapore had the widest range, 60 to 118 ms, its slowest day on 16 October. The slower time, which 95% of requests finished within, was 76 ms in Montreal and 143 ms in Tokyo.
| Test location | Typical response time | Slower response time | Requests |
|---|---|---|---|
| Amsterdam | 95 ms | 132 ms | 65 |
| San Francisco | 74 ms | 104 ms | 65 |
| Montreal | 58 ms | 76 ms | 65 |
| Singapore | 70 ms | 129 ms | 65 |
| Tokyo | 62 ms | 143 ms | 65 |
| Mumbai | 64 ms | 108 ms | 65 |
Typical: half of the requests finished within this time (technical: p50). Slower: 95% of requests finished within this time (technical: p95). Statistics
- Request
- GET supabase.com
- Measured from
- Amsterdam · San Francisco · Montreal · Singapore · Tokyo · Mumbai
- Requests
- Daily measurements from 7 October 2026 to 20 October 2026. 6 of 6 test locations included: Amsterdam, San Francisco, Montreal, Singapore, Tokyo, Mumbai. · 7 October 2026 to 20 October 2026
- Timings taken
- DNS, connect, TLS, waiting for the server, download
- Report coverage
- 6 of 6 test locations included: Amsterdam, San Francisco, Montreal, Singapore, Tokyo, Mumbai.
- Daily requests in each location
- Amsterdam: 65 · San Francisco: 65 · Montreal: 65 · Singapore: 65 · Tokyo: 65 · Mumbai: 65
- Typical response time
- Median of the eligible daily requests in each included location.
- Slower response time
- The 95th percentile of the same eligible daily requests in each included location.
Supabase
https://supabase.com
Independent measurement by LatencyRadar. Not affiliated with Supabase. · How we measure (v1.3)
How fast is your Supabase project compared to this?
This page measures supabase.com itself. Your project’s API runs in its own region, so test that endpoint to see where your users wait.
No account required · Takes about 30 seconds.