- 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 1d 21h it lasted.
Anything that failed between 2026-10-12 22:59 UTC and 2026-10-14 20:25 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 9
- investigating
We are experiencing increased latency with Realtime and are actively investigating.
provider
- monitoring
We have identified the cause and taken actions to remediate the high latency issues. We will continue to monitor.
provider
- monitoring
We have taken preventative steps to expand our realtime cluster capacity and are continuing to monitor our system stability for full recovery.
provider
- identified
We’re seeing increased Realtime latency and instability affecting the presence feature, which may impact join rates. This recurrence comes as we continue work on the remaining preventative measures. We are actively investigating and taking steps to mitigate the impact. We’ll share another update as soon as we have more information.
provider
- identified
We are continuing to investigate increased Realtime latency and instability affecting the presence feature, which may impact join rates. Our team is actively working on mitigation and we will share another update as soon as more information becomes available.
provider
- identified
We’ve added extra capacity to the system and are currently testing it. We expect to begin stabilizing the affected clusters shortly. We’ll continue to share further updates as more information becomes available.
provider
- identified
We’re seeing recovery for a large percentage of affected customers, though some issues remain in certain regions. We’re continuing to work on resolving the remaining issues and will share further updates as more information becomes available.
provider
- monitoring
We have stabilised impacted users and enabled improvements to our Realtime infrastructure. We will continue to monitor for full recovery.
provider
- resolved
Realtime has fully recovered.
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-27b93739af
Is Supabase still down?
No, this incident was resolved 2026-10-14 20:25 UTC. For Supabase's live state, see https://down.guide/supabase.
How long did it last?
1d 21h, from 2026-10-12 22:59 UTC to 2026-10-14 20:25 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.