Supabase outage, 12 November 2026
Elevated Error rates for All Supabase project APIs
- Started
- Resolved
- 12 Nov 2026, 23:31 UTC (after 1 h 17 min)
- Impact
- Minor
Is this still happening?
No. Supabase marked this incident resolved on 12 Nov 2026, 23:31 UTC, 1 h 17 min after it began.
Right now: Supabase reports all systems operational. (as of 13 Nov, 20:53 UTC) Live Supabase status
At a glance
- Supabase rated this a minor incident.
- It was resolved after 1 h 17 min. That is shorter than a typical Supabase incident: the median of the 43 other resolved ones we recorded is 2 h.
- Supabase had 22 other incidents in the 30 days before it.
- 5 earlier incidents look like the same kind of problem (same affected part or wording); the most recent was on 6 Nov 2026.
Our summary from the Supabase incidents we have recorded since 28 Aug 2026 - how we count.
Last update from Supabase
This issue has been resolved. All API routes are operating normally, and we are no longer observing elevated error rates.
Similar Supabase incidents
Earlier incidents with the same affected part or wording - useful to see how long this kind of problem usually takes.
-
, resolved after 40 min
Increased error rate in project creation and project restore
-
, resolved after 7 h 10 min
Project Lifecycle Actions Showing increased error rates across all regions
-
, resolved after 2 h 27 min
Increased Errors with Project Lifecycle Operations in US-West-2
-
, resolved after 3 days
-
, resolved after 2 h 12 min
Other recent Supabase incidents
Something wrong on this page?
Thanks - your report is on its way to us. We read every one.