Storage issues in us-east-1 and eu-central-1
Nov 4, 18:43 UTCNov 5, 11:02 UTC
Duration
16h 18m
Impact
Minor
Root cause
Not disclosed
Supabase, 90 days
55 incidents
Affected
Not listed by the vendor.
Final update
The incident has been resolved.
Timeline
- Resolved · Nov 5, 11:02 UTC
The incident has been resolved.
- Monitoring · Nov 5, 08:30 UTC
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.
- Monitoring · Nov 4, 21:53 UTC
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.
- Monitoring · Nov 4, 20:05 UTC
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.
- Investigating · Nov 4, 19:18 UTC
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.
- Investigating · Nov 4, 18:43 UTC
We have identified some customers in us-east-1 are experiencing 5XX errors when interacting with our Storage components. We are investigating.
More from Supabase
Full historyIntermittent 502/503 errors for pg_net calls to Edge Functionslasted 42mIntermittent errors on Supavisor Shared Pooler in us-east-2lasted 29mManagement API Postgres config updates overwriting previous updateslasted 2h 8mStorage uploads failing in us-east-1lasted 1h 14mPG15 -> PG17 Upgrade Failureslasted 1h 8mLogs degraded in multiple regionslasted 51m