- Level
- confirmed
- Worst impact
- Degraded
- Regions
- us, us-east-2
- Down Index
- 24of 100
What to do
Check whether you use Supabase in us, us-east-2. 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 29m it lasted.
Anything that failed between 2026-11-04 03:48 UTC and 2026-11-04 04:17 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
- monitoring
Between 2026-11-04 00:02 and 00:50 UTC there were elevated errors on Supavisor Shared Pooler in the us-east-2 region. Errors have subsided and things are back to normal. Example errors were ``` ClientHandler: (ECHECKOUTFAILED) checkout failed due to %{"C" => "08006", "M" => "Failed to connect to database: {:error, :timeout} DbHandler: Connection failed {:error, :timeout} to ~c".......us-east-2.compute.internal" ```
provider
- resolved
Errors have subsided and connections are back to normal.
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-f3bd2b5ce4
Is Supabase still down?
No, this incident was resolved 2026-11-04 04:17 UTC. For Supabase's live state, see https://down.guide/supabase.
How long did it last?
29m, from 2026-11-04 03:48 UTC to 2026-11-04 04:17 UTC, by the times Supabase posted.
What was affected?
Supabase named in us, us-east-2.
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.