- Level
- confirmed
- Worst impact
- Degraded
- Down Index
- 20of 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 3h 53m it lasted.
Anything that failed between 2026-08-11 14:37 UTC and 2026-08-11 18:30 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 6
- investigating
We're currently investigating an issue that is impacting MCP connections to branch environments.
provider
- identified
We've identified the root cause that was leading to permission errors on MCP connections to branch environments. We're currently working on addressing this.
provider
- identified
We're still working on implementing a fix for the identified root cause.
provider
- monitoring
UPDATE: We are currently pushing a fix to address the root cause. We'll provide another update once the fix has been fully deployed.
provider
- monitoring
We have pushed a fix to address the root cause and are monitoring the situation. If you continue to see an error, you can re-authenticate with the Supabase MCP server and also confirm that you have access to the preview branch.
provider
- resolved
Customers should now be able to connect to branch environments via MCP normally.
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-61c79963e6
Is Supabase still down?
No, this incident was resolved 2026-08-11 18:30 UTC. For Supabase's live state, see https://down.guide/supabase.
How long did it last?
3h 53m, from 2026-08-11 14:37 UTC to 2026-08-11 18:30 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.