← Back to Supabase History
minor✓ Resolved
Customer Projects Experiencing Upgrade Issues
Status
resolved
Duration
2h 49m
Updates
4
Coverage
0 articles
INCIDENT TIMELINE
✓ ResolvedFri, May 8, 2026, 04:15 PM
This incident has been resolved.
monitoringFri, May 8, 2026, 02:39 PM
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.
identifiedFri, May 8, 2026, 01:46 PM
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.
identifiedFri, May 8, 2026, 01:26 PM
We are continuing to work on a fix for this issue.
identifiedFri, May 8, 2026, 01:25 PM
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.
📊 TECHNICAL DETAILS
Internal ID
cfbc58b4-f603-4c9a-b60c-b14a2ac04f07
External ID
9nnnmxkfql8k
🕐 Started
Fri, May 8, 2026, 01:25 PM
🔄 Last Updated
Fri, May 8, 2026, 04:15 PM
✓ Resolved
Fri, May 8, 2026, 04:15 PM
MINOR
Impact Level
2h 49m
Total Duration
4
Status Updates
REQUEST COVERAGE
No article has been written for this incident yet. When 100 people request coverage, we automatically generate one.
0 / 100 requests100 more needed