- Level
- confirmed
- Worst impact
- Degraded
- Supabase says
- 2026-11-12 14:14 to 14:18 UTC (4m), and 2026-11-12 14:25 to 14:29 UTC (4m)
- Regions
- eu, eu-west-1
What to do
Check whether you use Supabase in eu, eu-west-1. Check your stack
Drop a package.json, lockfile, Terraform or a list of domains at down.guide to see every provider you depend on.Confirm your retries, queues and scheduled jobs caught up after the 8m it lasted.
Anything that failed between 2026-11-12 14:48 UTC and 2026-11-12 14:56 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 2
- monitoring
Between 14:14-14:18 UTC and 14:25-14:29, Storage requests may have been slow or aborted in the eu-west-1 region. This issue has been resolved and we do not expect recurrence. We are monitoring the region.
provider
- resolved
We have mitigated the issue with the Storage service and we have not observed any further issues during our monitoring period. We consider this incident to be 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-4b578b279b
Is Supabase still down?
No, this incident was resolved 2026-11-12 14:56 UTC. For Supabase's live state, see https://down.guide/providers/supabase.
How long did it last?
8m, from 2026-11-12 14:48 UTC to 2026-11-12 14:56 UTC, by the times Supabase posted.
What was affected?
Supabase named in eu, eu-west-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.