- Level
- confirmed
- Worst impact
- Degraded
- Down Index
- 13of 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 9m it lasted.
Anything that failed between 2026-08-17 01:47 UTC and 2026-08-17 01: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
- investigating
We are investigating an issue with project creation failing. We will be confirming more information shortly.
provider
- resolved
We have identified this as a non-user impacting alert and as such this is being 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-019f4bb432
Is Supabase still down?
No, this incident was resolved 2026-08-17 01:56 UTC. For Supabase's live state, see https://down.guide/supabase.
How long did it last?
9m, from 2026-08-17 01:47 UTC to 2026-08-17 01:56 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.