- Level
- confirmed
- Worst impact
- Degraded
- Down Index
- 17of 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 49m it lasted.
Anything that failed between 2026-09-28 13:47 UTC and 2026-09-28 14:36 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
Log ingestion is experiencing some delays. Ingestion will be retried by clients.
provider
- identified
The log ingestion issue was the result of a scaling gap. The relevant resources have been scaled and ingestion is recovering.
provider
- monitoring
Log ingestion has recovered. We are monitoring for continued stability.
provider
- resolved
Log ingestion is 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-cf1e4043f1
Is Supabase still down?
No, this incident was resolved 2026-09-28 14:36 UTC. For Supabase's live state, see https://down.guide/supabase.
How long did it last?
49m, from 2026-09-28 13:47 UTC to 2026-09-28 14:36 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.