Supabase reported this minor-impact incident on its official status page on Oct 6, 2026, 15:23 UTC. It was resolved after 2h 56m.
Right now Supabase is operational. Live Supabase status →
We've rolled out a fix for this issue and re-enabled upgrades in the dashboard. We apologize for the inconvenience.
The fix has been implemented. Upgrade operation has been restored. We will monitor for stability.
A fix has been developed and we are going through the review and implementation process.
We have identified the issue with the upgrade. To prevent issues, we have suspended the ability to upgrade projects while we resolve this issue. The problem is limited to upgrades from earlier versions of PG17 to the most recent release. We are working on a fix.
We have observed failures in attempted upgrades to 17.11.0.003. We are investigating.
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 60 incidents in the last 90 days, 21 of them major or critical. A typical incident lasted 2h 2m. See Supabase's uptime and incident history