Benchmark report

Supabase thumbnail

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

Amsterdam 95ms typicalSan Francisco 74ms typicalMontreal 58ms typicalSingapore 70ms typicalTokyo 62ms typicalMumbai 64ms typical
  • CanadaMontreal
    58 ms
  • JapanTokyo
    62 ms
  • IndiaMumbai
    64 ms
  • SingaporeSingapore
    70 ms
  • United StatesSan Francisco
    74 ms
  • NetherlandsAmsterdam
    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.

ConnectTLSServer waitDownload
NetherlandsAmsterdam
96 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 locations

Click a city to see its stage-by-stage breakdown.

ConnectTLSServer waitDownload
NetherlandsAmsterdam
96 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
United StatesSan Francisco
73 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
CanadaMontreal
62 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
SingaporeSingapore
79 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
JapanTokyo
64 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
IndiaMumbai
58 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

Daily median of 5 requests per location, 21 September 2026 to 20 October 2026.
0100200 ms21 Sept20 Oct
Show the numbers
DayAmsterdamSan FranciscoMontrealSingaporeTokyoMumbai
21 September 2026112 ms80 ms56 ms72 ms69 ms62 ms
22 September 202699 ms68 ms76 ms67 ms59 ms66 ms
23 September 202699 ms70 ms58 ms69 ms62 ms63 ms
24 September 202699 ms68 ms64 ms66 ms62 ms78 ms
25 September 2026103 ms81 ms62 ms67 ms52 ms68 ms
26 September 2026100 ms76 ms61 ms70 ms52 ms73 ms
27 September 202693 ms90 ms59 ms64 ms55 ms58 ms
28 September 2026100 ms60 ms49 ms76 ms71 ms61 ms
29 September 2026112 ms69 ms70 ms81 ms57 ms66 ms
30 September 202688 ms64 ms59 ms68 ms59 ms58 ms
1 October 202697 ms75 ms62 ms82 ms64 ms62 ms
2 October 202697 ms69 ms55 ms65 ms54 ms66 ms
3 October 2026140 ms105 ms64 ms70 ms65 ms56 ms
4 October 2026100 ms72 ms66 ms71 ms57 ms60 ms
5 October 2026104 ms78 ms64 ms63 ms57 ms62 ms
6 October 202695 ms82 ms59 ms77 ms55 ms55 ms
7 October 202695 ms90 ms65 ms71 ms54 ms74 ms
9 October 202686 ms69 ms58 ms73 ms57 ms71 ms
10 October 202695 ms65 ms51 ms64 ms75 ms74 ms
11 October 202695 ms87 ms58 ms81 ms65 ms57 ms
12 October 202686 ms79 ms53 ms64 ms70 ms69 ms
13 October 202690 ms70 ms54 ms66 ms59 ms51 ms
14 October 2026101 ms77 ms53 ms77 ms60 ms68 ms
15 October 202698 ms72 ms64 ms60 ms56 ms72 ms
16 October 202692 ms75 ms58 ms118 ms55 ms65 ms
17 October 2026111 ms85 ms54 ms102 ms62 ms57 ms
18 October 202697 ms71 ms59 ms72 ms67 ms67 ms
19 October 202693 ms75 ms59 ms92 ms59 ms58 ms
20 October 202693 ms70 ms60 ms65 ms56 ms61 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 locationTypical response timeSlower response timeRequests
Amsterdam95 ms132 ms65
San Francisco74 ms104 ms65
Montreal58 ms76 ms65
Singapore70 ms129 ms65
Tokyo62 ms143 ms65
Mumbai64 ms108 ms65

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.

Test my project

No account required · Takes about 30 seconds.

More benchmarks

All benchmarks →