- Level
- confirmed
- Worst impact
- Partial outage
- Regions
- eu
- Down Index
- 37of 100
What to do
Check whether you use Supabase in eu. 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 12h 3m it lasted.
Anything that failed between 2026-10-22 03:53 UTC and 2026-10-22 15: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 3
- monitoring
We identified increased error rates in project lifecycle operations (create, restore, pauses, etc.) in the EU region since 21 Oct 23:00 UTC. A mitigation has been put in place and error rates have reduced to normal levels. We are monitoring the situation and are working on fixing affected projects.
provider
- monitoring
Error rates remain at normal levels. We’re continuing to monitor to confirm sustained stability before resolving this incident.
provider
- resolved
Error rates have remained at normal levels following the mitigation. This incident is now 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-c6247a39bd
Is Supabase still down?
No, this incident was resolved 2026-10-22 15:56 UTC. For Supabase's live state, see https://down.guide/supabase.
How long did it last?
12h 3m, from 2026-10-22 03:53 UTC to 2026-10-22 15:56 UTC, by the times Supabase posted.
What was affected?
Supabase named in eu.
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.