- Level
- confirmed
- Worst impact
- Degraded
- Down Index
- 19of 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 2h it lasted.
Anything that failed between 2026-09-19 20:12 UTC and 2026-09-19 22:12 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 4
- investigating
We are experiencing degradation of project lifecycle activities. We are investigating.
provider
- investigating
We are observing recovery in project lifecycle operations. Our team is investigating the root cause and actively working to prevent recurrence.
provider
- monitoring
Project lifecycle operations have remained stable. We will continue to monitor the platform.
provider
- resolved
Project lifecycle operations are behaving normally.
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-9f263c367c
Is Supabase still down?
No, this incident was resolved 2026-09-19 22:12 UTC. For Supabase's live state, see https://down.guide/supabase.
How long did it last?
2h, from 2026-09-19 20:12 UTC to 2026-09-19 22:12 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.