Supabase incident

Upgrade Failures

Minor Resolved Upstream link ↗

Started

June 25, 2026 at 02:20 PM UTC

Duration

4h 31m

Resolved

June 25, 2026 at 06:51 PM UTC

Updates timeline

  1. Investigating

    We are investigating potential upgrade issues in multiple regions. We are working to confirm impact and determine next steps.

  2. Investigating

    Upgrades are taking longer than usual, but generally will complete if allowed to proceed. We are investigating the cause of the delays.

  3. Identified

    The upgrade delays have been caused by resource capacity limits. We are taking actions to increase the appropriate resources.

  4. Identified

    We are aware that upgrades continue to be delayed. We are exploring other factors that are contributing to the slow upgrades.

  5. Identified

    We are continuing to work through a variety of options for improving upgrade performance. This includes working with our upstream provider and adjusting operational parameters.

  6. Identified

    We are implementing operational mitigations to try to improve upgrade performance.

  7. Identified

    We are continuing our operational and investigative work to improve upgrade flow performance and mitigate further problems.

  8. Identified

    We are starting to notice improvements as a result of our mitigation efforts, and expect that project upgrades should start to become less delayed. We’ll continue monitoring and will update as we observe improvements across the fleet.

  9. Monitoring

    We have implemented all necessary mitigations and the project upgrade rates have returned to normal across the fleet. We will continue to monitor these flows for any irregularities or recurring degradation. If you are still experiencing delayed or blocked upgrades on your Project, please contact Support.

  10. Resolved

    Through our monitoring, we have determined that project upgrade behavior has returned to normal across the fleet. This incident is resolved.

Live Supabase status

Current indicator + 24h latency

All incidents

Cross-service timeline

Subscribe via RSS

Atom feed for any reader