- Level
- confirmed
- Worst impact
- Degraded
- Regions
- us, us-east-1
- Down Index
- 26of 100
What to do
Check whether you use Supabase in us, us-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 1h 12m it lasted.
Anything that failed between 2026-08-24 15:26 UTC and 2026-08-24 16:38 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 aware of reports of increased rates of connection timeouts for users connecting to Projects in us-east-1 via Supavisor.
provider
- monitoring
We have identified a degraded Supavisor node and we have rolled out a fix. We are monitoring to ensure continued stability. Confirmed Impact: On Aug 24, 2026 between 14:30 and 15:20 UTC we observed increased rates of connection timeouts connecting to Supavisor in us-east-1 due to a degraded node.
provider
- resolved
This incident has been 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-a5ad1ecb56
Is Supabase still down?
No, this incident was resolved 2026-08-24 16:38 UTC. For Supabase's live state, see https://down.guide/supabase.
How long did it last?
1h 12m, from 2026-08-24 15:26 UTC to 2026-08-24 16:38 UTC, by the times Supabase posted.
What was affected?
Supabase named in us, us-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.