Supabase reported this minor-impact incident on its official status page on Aug 3, 2026, 15:28 UTC. It was resolved after 2d 2h.
Right now Supabase is degraded. Live Supabase status →
Project upgrades have remained stable, we are resolving this incident.
We have deployed a tested fix for the upgrade issue impacting some projects. The fix has been effective and we are monitoring for continued stability.
We are continuing to test the fix to project upgrades. We will update again when the fix is applied.
The team has identified a likely fix and is consolidating the details in order to move to thorough testing. We will update again when the fix is applied.
We are continuing to fix project upgrade issues and are investigating further remediation. We will provide our next update within the next 14 hours.
We are developing a fix for the upgrade issues.
We have identified the cause of the upgrade delays and are working on a fix.
We are continuing to investigate project upgrade issues.
We are investigating a potential issue that could result in a delay or failure in some users' project upgrades.
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