Provider
SupabaseIncident detail
Customer Projects Experiencing Upgrade Issues
Resolved incidentMinor
Timeline window
to
Get alerted the next time Supabase breaks
Free email alerts for the handful of vendors you cannot afford to miss. No card, live in about a minute. Paid plans add Slack, Teams, Discord, and webhook delivery across your whole stack, plus higher API quotas.
Timeline
Incident updates
Every update on the official status source, oldest to newest, exactly as it appeared there.
Identified
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
We are continuing to work on a fix for this issue.
Identified
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
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
Upgrade operations have returned to normal.
Keep exploring
More from Supabase
Neighboring incidents on Supabase's timeline and the rest of their record on OutageDeck.