- Level
- confirmed
- Worst impact
- Degraded
- Down Index
- 18of 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 1h 8m it lasted.
Anything that failed between 2026-10-31 20:06 UTC and 2026-10-31 21:14 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
- identified
We are actively investigating some reports of failed PG15 -> PG17 upgrades. We have identified an error in an AMI release from today and are rolling it back to unblock upgrades.
provider
- monitoring
We are seeing successful upgrades again, and error rates have returned to normal levels. We will continue to monitor to ensure continued stability.
provider
- resolved
This issue is now 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-9e30ca2103
Is Supabase still down?
No, this incident was resolved 2026-10-31 21:14 UTC. For Supabase's live state, see https://down.guide/supabase.
How long did it last?
1h 8m, from 2026-10-31 20:06 UTC to 2026-10-31 21:14 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.