- Level
- confirmed
- Worst impact
- Degraded
- Down Index
- 23of 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 3d 22h it lasted.
Anything that failed between 2026-08-27 17:20 UTC and 2026-08-31 15:57 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 11
- investigating
We’re currently investigating latency issue that may cause increased response times for a small percentage of requests. In some cases, this may also result in 525 errors. Our team is actively working to resolve the issue. We’ll share another update as soon as we have more information.
provider
- investigating
We’re continuing to investigate the issue causing increased response times for requests and 525 errors. Our team remains actively engaged in the investigation, we’ll provide another update as soon as we have more details.
provider
- investigating
We are continuing to investigate this issue and we’ll share more information as soon as it becomes available.
provider
- investigating
We are continuing to investigate this issue and we’ll share more information as soon as it becomes available.
provider
- identified
The team has identified the change which resulted in additional latency and error rates for some data API Requests. They are preparing to roll this change back. This rollout will take some time, and we will update again as there is news on the progress of the fix.
provider
- identified
We are continuing to work through the remediation plan for the latency issues. We will provide a further update as soon as more information is available.
provider
- identified
PostgREST 14.5 has been deployed since 12:00pm UTC to all AP regions: ap-east-1, ap-northeast-1, ap-northeast-2, ap-south-1, ap-southeast-1, and ap-southeast-2 as well as sa-east-1 and ca-central-1, eu-central-1, eu-central-2, eu-north-1, eu-west-2, and eu-west-3, us-west-1 We'll continue to provide updates as we roll out the change for the remaining impacted regions.
provider
- identified
The roll out has also been completed for us-east-1.
provider
- monitoring
The rollout has been completed in all regions. We will continue to monitor.
provider
- monitoring
Response times have recovered in all regions. We will continue to monitor throughout the weekend.
provider
- resolved
Response times have recovered in all regions. 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-5edbd7dd9d
Is Supabase still down?
No, this incident was resolved 2026-08-31 15:57 UTC. For Supabase's live state, see https://down.guide/supabase.
How long did it last?
3d 22h, from 2026-08-27 17:20 UTC to 2026-08-31 15:57 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.