- Level
- confirmed
- Worst impact
- Degraded
- Down Index
- 8of 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 0m it lasted.
Anything that failed between 2026-08-28 16:18 UTC and 2026-08-28 16:18 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 1
- resolved
PostgreSQL 15 projects were failing to load /usr/lib/postgresql/15/lib/supautils.so because GLIBC_2.33 is unavailable on affected hosts. This disrupted database access in multiple regions. Rollback is now complete and we are seeing access restored to projects in the affected regions.
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-4983662d9e
Is Supabase still down?
No, this incident was resolved 2026-08-28 16:18 UTC. For Supabase's live state, see https://down.guide/supabase.
How long did it last?
0m, from 2026-08-28 16:18 UTC to 2026-08-28 16:18 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.