- 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 1d it lasted.
Anything that failed between 2026-09-23 09:31 UTC and 2026-09-24 10:01 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
- investigating
We have identified an issue with Storage for projects are restoring from backups. Users may experience increased 500 errors. We are working to identify the root cause and will notify for any progress as soon as we have an update
provider
- monitoring
A fix has been implemented for the affected tenants and we are monitoring the results. We will continue to monitor the situation and will provide further updates as more information becomes available.
provider
- resolved
Storage is now operating normally. We apologise for the disruption. Hardening measures are being put in place to prevent recurrence and will be communicated upon completion.
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-93449235cc
Is Supabase still down?
No, this incident was resolved 2026-09-24 10:01 UTC. For Supabase's live state, see https://down.guide/supabase.
How long did it last?
1d, from 2026-09-23 09:31 UTC to 2026-09-24 10:01 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.