Supabase uptime
Supabase, checked by StatOSS every 5 minutes from Aarhus and Copenhagen in Denmark, Falkenstein in Germany, Ashburn in the USA, Singapore, and Sydney in Australia. Measured from outside, with every outage dated in UTC.
Supabase is up.
Up for 6 d 3 h. Last checked 2026-10-06 11:34 UTC from Sydney, Australia: 401 in 257 ms.
Last 24 hours
Up for 6 d 3 h100% passed
287 checks, median 78 ms from Falkenstein, all passed
95% under 162 ms
Response time by region
Medians over this range, on one scale up to 300 ms. Europe's places are scaled to Falkenstein, its fastest shared place.
Last 90 days
Up for 6 d 3 h99.94% passed
1,763 checks, median 76 ms from Falkenstein, 1 timeout
95% under 123 ms
Response time by region
Medians over this range, on one scale up to 300 ms. Europe's places are scaled to Falkenstein, its fastest shared place.
In the last 24 hours Supabase passed 288 of 288 checks, 100%.
No outage since checks began on 30 Sep 2026.
Availability
The share of checks that passed, and the outages that began, in each window up to now.
| Last | Passed | Checks | Outages |
|---|---|---|---|
| 24 hours | 100% | 288 of 288 | 0 |
| 7 days | Not enough history yet: checks began on 30 Sep 2026 | ||
| 30 days | Not enough history yet: checks began on 30 Sep 2026 | ||
| 90 days | Not enough history yet: checks began on 30 Sep 2026 | ||
A year of checks is kept; the year's figure appears here once there is a year of them.
Response time by location
Over the last 7 days, from the checks that passed: the time from the start of the request to the answer's headers, with the DNS lookup, the connection and TLS included.
| From | Median | 95th percentile | Mean | Checks |
|---|---|---|---|---|
| Falkenstein, Germany | 78 ms | 127 ms | 108 ms | 198 |
| Ashburn, USA | 52 ms | 126 ms | 94 ms | 554 |
| Copenhagen, Denmark | 88 ms | 141 ms | 102 ms | 170 |
| Singapore | 68 ms | 187 ms | 111 ms | 564 |
| Sydney, Australia | 219 ms | 300 ms | 241 ms | 84 |
| Aarhus, Denmark | 90 ms | 151 ms | 128 ms | 192 |
Outages
None detected since checks began on 30 Sep 2026.
What is checked
Hosted Postgres with authentication, storage, realtime and edge functions around it.
StatOSS sends GET https://api.supabase.com/v1/projects and counts the check as passed on status 401 within 10 seconds. The Management API's list of projects, which the dashboard and the CLI use. Without a token it answers 401.
It checks the platform's API. Each project's database and APIs run on their own and are not checked.
Supabase reports its own incidents at status.supabase.com. The figures here are measured from outside and can differ from it in both directions.
How it is measured
- One check every 5 minutes, from one location at a time in turn: Aarhus and Copenhagen in Denmark, Falkenstein in Germany, Ashburn in the USA, Singapore, and Sydney in Australia.
- A check fails when no answer comes within 10 seconds, when the connection or TLS fails, or when the answer is not status 401.
- A failed check is repeated at once from a second location, and counts only when that location fails too, or cannot answer within 20 seconds.
- Two failed checks in a row make an outage, dated from the second, and the first check that passes ends it. A failure shorter than 10 minutes may not make one, and times are good to about 5 minutes.
- Availability is the share of checks that passed. There are no maintenance windows: every check counts.
It is the same check a StatOSS status page runs for its owner, with the same rules; the docs on checks have the details.