Supabase reported this minor-impact incident on its official status page on Nov 4, 2026, 18:43 UTC. It was resolved after 16h 18m.
Right now Supabase is operational. Live Supabase status →
The incident has been resolved.
The planned database capacity increase for Storage in us-east-1 was completed at 08:06 UTC. Some requests to Storage in us-east-1 may have failed briefly while the database switched over during the change. Storage in us east-1 and eu-central-1 is operating normally. We are continuing to monitor Storage error rates.
We will be conducting maintenance to address storage service improvements between 0800 and 0900 UTC on 5 November 2026. There may be an interruption of storage services in us-east-1 at some point during that window. The impact will be of a short duration and limited to us-east-1.
The cause of the issue has been identified as directly related to load. We will be doing maintenance on our platform to address this issue. As of now, storage response has returned to normal. We will continue to monitor the environment.
We are still investigating increased error rates for storage requests, and have expanded the investigation to eu-central-1 as well. The team has identified higher-than-usual load in some areas of the storage infrastructure and is currently working on remediation options.
We have identified some customers in us-east-1 are experiencing 5XX errors when interacting with our Storage components. We are investigating.
Overlapping incidents aren't necessarily related.
Supabase reported 59 incidents in the last 90 days, 22 of them major or critical. A typical incident lasted 2h. See Supabase's uptime and incident history