Customer Projects Experiencing Upgrade Issues

Summary

Customer Projects Experiencing Upgrade Issues

Upgrade operations have returned to normal.

• Started

  May 8, 2026 · 1:25 PM

• Resolved

  May 8, 2026 · 4:13 PM

• Duration

  2h 48m

• Severity

  Minor

• ◆

  Identified

  May 8 · 1:25 PM Supabase

  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 8 · 1:26 PM Supabase

  We are continuing to work on a fix for this issue.

• ◆

  Identified

  May 8 · 1:46 PM Supabase

  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 8 · 2:39 PM Supabase

  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 8 · 4:13 PM Supabase

  Upgrade operations have returned to normal.