Supabase reported this major-impact incident on its official status page on Sep 24, 2026, 15:36 UTC. It was resolved after 2h 2m.
Right now Supabase is degraded. Live Supabase status →
This incident has been resolved.
We are continuing to monitor to ensure ongoing stability.
The remaining projects have now been brought back up, and we have no projects remaining on the unhealthy underlying hardware in the upstream infrastructure. We are monitoring to ensure ongoing stability.
Most projects have been brought back up, and the team is working on the remaining projects, which should be completed soon. This issue was related to specific underlying hardware in the region, so this was isolated to only projects on that hardware. Project lifecycle operations (restarts, upgrades, etc) broadly across the region remain available.
All projects affected by the upstream infrastructure issues, and mitigation efforts are underway internally. These affected projects will be brought back up on new hardware as quickly as possible.
We have isolated the scope of the problem to a specific upstream incident. We are working to address the upstream incident and determine mitigations.
We are investigating project lifecycle operation issues in eu-west-1.
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