- Level
- confirmed
- Worst impact
- Degraded
- Down Index
- 23of 100
What to do
Check whether your product depends on Supabase. 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 22h 36m it lasted.
Anything that failed between 2026-10-12 19:49 UTC and 2026-10-13 18:24 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 5
- identified
We are experiencing significant degraded performance across edge functions, mainly affecting deploy and retrieving function body. We have identified the root cause and are working on the fix now.
provider
- identified
We're now seeing reduced error rates for Edge Functions. We've identified the root cause and are working on a fix.
provider
- identified
Edge Functions deployments have returned to normal levels. We're now reviewing worker jobs that failed during the incident, including any backups that may have been affected. We'll re-queue these jobs once we've identified them, and we'll share more details on the status page. If you're noticing particular job failures that are unusual, please reach out to support.
provider
- monitoring
Edge Functions deployments have returned to normal levels. We will continue monitoring for full recovery.
provider
- resolved
Edge function deployments have remained stable. We are closing the incident.
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-e42eceac44
Is Supabase still down?
No, this incident was resolved 2026-10-13 18:24 UTC. For Supabase's live state, see https://down.guide/supabase.
How long did it last?
22h 36m, from 2026-10-12 19:49 UTC to 2026-10-13 18:24 UTC, by the times Supabase posted.
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.