Supabase incident
Storage users in US-West-2 experiencing increased latency on storage requests
Supabase experienced a minor incident on June 12, 2026 affecting Storage, lasting 8h 39m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- identified Jun 12, 2026, 04:00 PM UTC
Users in US-West-2 are seeing increased latency on storage requests. The team has identified the issue and is working on a solution.
- identified Jun 12, 2026, 04:30 PM UTC
We are implementing load mitigation strategies to improve the performance of storage requests in US-West-2.
- identified Jun 12, 2026, 05:29 PM UTC
The team is still working on a solution, and mitigation work is underway.
- identified Jun 12, 2026, 06:28 PM UTC
We have implemented further mitigations and are tracking their progress. We continue to actively work this issue.
- identified Jun 12, 2026, 07:30 PM UTC
We are seeing improvement in the performance of us-west-2 after implementation of our mitigation strategies. Storage operation is returning to normal. We will continue to monitor performance in this region.
- monitoring Jun 12, 2026, 08:26 PM UTC
Backlog is being effectively processed and operations have returned to normal. We continue to monitor the performance in us-west-2.
- monitoring Jun 12, 2026, 11:57 PM UTC
Job queues continue to drain. We will actively monitor until they are complete.
- resolved Jun 13, 2026, 12:40 AM UTC
All residual jobs have drained. Storage performance and job activity is normal.