- Level
- confirmed
- Worst impact
- Degraded
- Down Index
- 33of 100
What to do
Check whether your product depends on Supabase. Check your stack
Drop a package.json, lockfile, Terraform or a list of domains at down.guide to see every provider you depend on.Confirm your retries, queues and scheduled jobs caught up after the 1h 18m it lasted.
Anything that failed between 2026-11-12 22:13 UTC and 2026-11-12 23:31 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 are currently seeing slightly increased error rates for API requests to the Data APIs, Auth, Storage, and other HTTP API routes across all regions The team is currently investigating.
provider
- monitoring
We have isolated the error rates to an individual project with a very unusually high request rate, and we have determined there is no widespread issue as we originally suspected. We will continue to monitor to ensure things remain stable, but all API routes are nominal.
provider
- resolved
This issue has been resolved. All API routes are operating normally, and we are no longer observing elevated error rates.
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-dac5b92ace
Is Supabase still down?
No, this incident was resolved 2026-11-12 23:31 UTC. For Supabase's live state, see https://down.guide/providers/supabase.
How long did it last?
1h 18m, from 2026-11-12 22:13 UTC to 2026-11-12 23:31 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.