Supabase reported this major-impact incident on its official status page on Jul 17, 2026, 17:49 UTC. It was resolved after 7h 52m.
Right now Supabase is degraded. Live Supabase status →
Project actions have been sustained at normal performance. This incident is resolved.
The mitigation has returned project activity to normal performance. Project actions that failed during the outage are being requeued to run. We will continue to monitor to ensure project functionality.
We have identified a problem with a specific job in us-east-1, we have mitigated the job and are observing the results.
We are testing mitigation options to attempt to restore project action performance.
We have determined that there are four main project actions impacted in the identified regions: Pause/unpause failures, Restore/PITR failures, PITR configuration failures and Backup problems. We are pursuing root cause and mitigation options in parallel.
Project actions in us-east-1, us-east-2, sa-east-1, ca-central-1 are experiencing significant increases in error rates. We are exploring the best options for restoring performance.
Certain project actions are failing. We are actively investigating to determine the regions impacted and source of the issue.
Our 5-minute checks didn't record a change in Supabase's overall status around this incident. Smaller or regional incidents often leave a provider's overall status green.
Overlapping incidents aren't necessarily related.
Supabase reported 43 incidents in the last 90 days, 16 of them major or critical. A typical incident lasted 2h 2m. See Supabase's uptime and incident history