Supabase experienced a minor incident on June 25, 2026 affecting Database, lasting 4h 31m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Jun 25, 2026, 02:20 PM UTC
We are investigating potential upgrade issues in multiple regions. We are working to confirm impact and determine next steps.
- investigating Jun 25, 2026, 02:41 PM UTC
Upgrades are taking longer than usual, but generally will complete if allowed to proceed. We are investigating the cause of the delays.
- identified Jun 25, 2026, 03:01 PM UTC
The upgrade delays have been caused by resource capacity limits. We are taking actions to increase the appropriate resources.
- identified Jun 25, 2026, 03:32 PM UTC
We are aware that upgrades continue to be delayed. We are exploring other factors that are contributing to the slow upgrades.
- identified Jun 25, 2026, 04:03 PM UTC
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.
- identified Jun 25, 2026, 04:27 PM UTC
We are implementing operational mitigations to try to improve upgrade performance.
- identified Jun 25, 2026, 05:03 PM UTC
We are continuing our operational and investigative work to improve upgrade flow performance and mitigate further problems.
- identified Jun 25, 2026, 05:46 PM UTC
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.
- monitoring Jun 25, 2026, 06:08 PM UTC
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.
- resolved Jun 25, 2026, 06:51 PM UTC
Through our monitoring, we have determined that project upgrade behavior has returned to normal across the fleet. This incident is resolved.