- Level
- confirmed
- Worst impact
- Degraded
- Regions
- eu, eu-central-1, us, us-east-1
- Down Index
- 39of 100
What to do
Check whether you use Supabase in eu, eu-central-1, us, us-east-1. Check your stack
Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.Confirm your retries, queues and scheduled jobs caught up after the 16h 18m it lasted.
Anything that failed between 2026-11-04 18:43 UTC and 2026-11-05 11:02 UTC may need a replay.Subscribe to Supabase's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=supabase works in Slack (/feed subscribe), Discord feed bots and any RSS reader.
Updates from Supabase 6
- investigating
We have identified some customers in us-east-1 are experiencing 5XX errors when interacting with our Storage components. We are investigating.
provider
- investigating
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.
provider
- monitoring
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.
provider
- monitoring
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.
provider
- monitoring
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.
provider
- resolved
The incident has been resolved.
provider
Reports count in aggregate; nothing about you is shown.
Corrections
None so far.
Something wrong on this page? Report an error or send us a note. Every fix is listed here.
Questions about DWN-bd121c4916
Is Supabase still down?
No, this incident was resolved 2026-11-05 11:02 UTC. For Supabase's live state, see https://down.guide/supabase.
How long did it last?
16h 18m, from 2026-11-04 18:43 UTC to 2026-11-05 11:02 UTC, by the times Supabase posted.
What was affected?
Supabase named in eu, eu-central-1, us, us-east-1.
What caused it?
Supabase hasn't published a root cause. If it does, it shows here.
Where does this come from?
Supabase's official status page, https://status.supabase.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.