- Level
- confirmed
- Worst impact
- Degraded
- Regions
- eu, eu-east-1
- Down Index
- 16of 100
What to do
Check whether you use Supabase in eu, eu-east-1. 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 0m it lasted.
Anything that failed between 2026-08-24 05:39 UTC and 2026-08-24 05:39 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 1
- resolved
Between 04:54 and 04:58 UTC we observed error spikes in one of the eu-east-1 Supavisor clusters. Users would have experienced errors in connecting to postgres via Supavisor. The issue has since recovered. Errors reported: ClientHandler: (ECHECKOUTTIMEOUT) unable to check out connection from the pool after 15000ms in Transaction mode.
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-762aeaeba6
Is Supabase still down?
No, this incident was resolved 2026-08-24 05:39 UTC. For Supabase's live state, see https://down.guide/supabase.
How long did it last?
0m, from 2026-08-24 05:39 UTC to 2026-08-24 05:39 UTC, by the times Supabase posted.
What was affected?
Supabase named in eu, eu-east-1.
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.