Supabase experienced a minor incident on May 8, 2026, lasting 2h 48m. The incident has been resolved; the full update timeline is below.
Update timeline
- identified May 08, 2026, 01:25 PM UTC
Our engineering team are investigating issues with customer projects being stuck when upgrading Postgres version. We advise that you do not upgrade your project until the incident is resolved.
- identified May 08, 2026, 01:26 PM UTC
We are continuing to work on a fix for this issue.
- identified May 08, 2026, 01:46 PM UTC
We are continuing to investigate issues impacting project upgrades. We have observed that the majority of affected projects are successfully returning to a healthy state on their previous PostgreSQL version following failed upgrade attempts. Our engineering team is actively working to manually restore the remaining projects that are still stuck during the upgrade process. As a precaution, we recommend that customers do not attempt to upgrade their projects until this incident has been fully resolved. We will continue to provide updates as information becomes available.
- monitoring May 08, 2026, 02:39 PM UTC
We have identified the root cause and developed a fix, which has been applied in production. Projects which have failed to upgrade will be automatically recovered and returned to ACTIVE_HEALTHY without manual intervention. Any future upgrades should complete successfully. We are continuing to monitor recovery and system stability closely.
- resolved May 08, 2026, 04:13 PM UTC
Upgrade operations have returned to normal.