Checked 3 minutes ago
One problem in the last 48 hours, 44 days ago, lasting 1034h 2m.
This longer record is here so the 48-hour picture above can mean something — without it we could tell you a problem happened, but not whether that is normal for Supabase.
Something was impaired on 24.98% of our checks over that window. That is how often Supabase was reporting a problem somewhere, which is not the same as how often it was unreachable. The longest outage we have on record ran 1034h 2m.
The last 30 days of Supabase, one row each.
| Day | Clear | Up | Checks | Started | Longest ended |
|---|---|---|---|---|---|
| 2026-09-27 | No checks yet today | ||||
| 2026-09-26 | 81.94% | 100% | 288 | none | 1034h 2m |
| 2026-09-25 | 68.53% | 100% | 286 | 1 | — |
| 2026-09-24 | 86.41% | 86.41% | 287 | 2 | 2h 5m |
| 2026-09-23 | 32.06% | 94.08% | 287 | 1 | 981h 23m |
| 2026-09-22 | 91.64% | 100% | 287 | 2 | 1h 32m |
| 2026-09-21 | 100% | 100% | 287 | none | — |
| 2026-09-20 | 100% | 100% | 287 | none | — |
| 2026-09-19 | 91.64% | 91.64% | 287 | 1 | 2h 3m |
| 2026-09-18 | 68.99% | 100% | 287 | none | 845h 7m |
| 2026-09-17 | 81.53% | 100% | 287 | 1 | — |
| 2026-09-16 | 66.9% | 90.59% | 287 | 2 | 5h 14m |
| 2026-09-15 | 100% | 100% | 287 | none | — |
| 2026-09-14 | 100% | 100% | 287 | none | — |
| 2026-09-13 | 100% | 100% | 287 | none | — |
| 2026-09-12 | 51.22% | 100% | 287 | none | 705h 22m |
| 2026-09-11 | 22.65% | 23.69% | 287 | 1 | 26h 54m |
| 2026-09-10 | 64.46% | 64.46% | 287 | 1 | — |
| 2026-09-09 | 100% | 100% | 288 | none | — |
| 2026-09-08 | 100% | 100% | 287 | none | — |
| 2026-09-07 | 49.83% | 100% | 287 | 1 | 595h 28m |
| 2026-09-06 | 100% | 100% | 287 | none | — |
| 2026-09-05 | 100% | 100% | 287 | none | — |
| 2026-09-04 | 66.55% | 67.6% | 287 | 1 | 8h 5m |
| 2026-09-03 | 68.29% | 100% | 287 | none | 485h 18m |
| 2026-09-02 | 81.88% | 100% | 287 | 1 | — |
| 2026-09-01 | 59.93% | 92.68% | 287 | 1 | 437h 32m |
| 2026-08-31 | 71.78% | 88.85% | 287 | 2 | 2h 42m |
| 2026-08-30 | 100% | 100% | 287 | none | — |
| 2026-08-29 | 44.25% | 44.25% | 287 | none | 65h 36m |
Clear is the share of checks that found nothing wrong at all; Up is the share that found Supabase actually reachable — a vendor reporting one impaired component scores zero on the first and a hundred on the second, and both are true. Started counts outages that began that day and Longest ended the longest that finished on it, so a problem running across midnight is counted once, on the day it began, and measured on the day it stopped.
Rows recorded before 8 August 2026 do not carry a check count — the figure was kept and the denominator was not — so their percentages are shown without one rather than with a number borrowed from somewhere else. Rows before 9 August 2026 have no Up figure either: until then we recorded only whether something was wrong, not whether it was down, and the two are different questions.
| Started | Lasted | Severity | What happened |
|---|---|---|---|
| 2026-08-14 02:23 UTC | 1034h 2m | having problems | 401 errors due to JWT rejections |
| 2026-09-24 15:36 UTC | 2h 5m | partly down | Project Lifecycle Issues in eu-west-1 |
| 2026-09-24 10:37 UTC | 1h 14m | down | Permission errors in the Supabase Dashboard |
| 2026-08-14 02:23 UTC | 981h 23m | partly down | 401 errors due to JWT rejections |
| 2026-09-22 10:49 UTC | 1h 32m | having problems | Supavisor connection disruptions in EU West 1 (Ireland) |
| 2026-09-22 08:33 UTC | 33 min | having problems | Project creations are degraded in multiple regions |
| 2026-09-19 20:12 UTC | 2h 3m | partly down | Project Lifecycle Activity Degradation |
| 2026-08-14 02:23 UTC | 845h 7m | having problems | 401 errors due to JWT rejections |
| 2026-09-16 17:53 UTC | 2h 47m | having problems | Query slowness for projects running Postgres version 14 in us-east-1 and ap-northeast-2 |
| 2026-09-16 07:17 UTC | 5h 14m | partly down | Auth Service Outage |
| 2026-08-14 02:23 UTC | 705h 22m | having problems | 401 errors due to JWT rejections |
| 2026-09-10 15:26 UTC | 26h 54m | partly down | Unresponsive Projects |
| 2026-08-14 02:23 UTC | 595h 28m | having problems | 401 errors due to JWT rejections |
| 2026-09-04 00:15 UTC | 8h 5m | down | Project Lifecycle Actions (Creations, restarts, configuration and compute size updates) Showing increased error rates |
| 2026-08-14 02:23 UTC | 485h 18m | having problems | 401 errors due to JWT rejections |
| 2026-09-01 08:45 UTC | 1h 50m | down | User unable to log in to Supabase Dashboard |
| 2026-08-14 02:23 UTC | 437h 32m | having problems | 401 errors due to JWT rejections |
| 2026-08-31 16:28 UTC | 2h 42m | partly down | Project Creation Failures |
| 2026-08-26 19:49 UTC | 65h 36m | partly down | pgBouncer issues on some older projects |
| 2026-08-14 02:23 UTC | 292h 22m | having problems | 401 errors due to JWT rejections |
Status pages report the vendor's view of their own service, and they lag real
outages — often by many minutes, sometimes by hours, because a human usually has to
confirm before anything is posted. They also can't see the two things most likely to
be wrong at your end.
The first is your own connection under load. A line that idles at 20 ms can
jump to 300 ms the moment something starts uploading, which drops you from sessions
and looks exactly like a server fault. Your plan speed says nothing about this; it's
called bufferbloat and almost nobody measures it.
The second is where everyone else in your group is. A service can be healthy in your
region and unwell in theirs, and if one person is hosting, their problem is everyone's
problem.
Supabase being fine where you are does not mean it is fine for everyone in your group. The live dashboard resolves status against each person's own region, and will tell you which of your friends is in an affected area — plus who has the connection to host, which is usually a different question from who has the fastest plan.
Worth a look when more than one thing feels broken at once: if several are genuinely down together, the fault is usually something they share rather than anything at your end. We are not claiming these particular services fail together — the live dashboard says when they actually do.