Supabase reported this minor-impact incident on its official status page on Oct 12, 2026, 22:59 UTC. It was resolved after 1d 21h.
Right now Supabase is operational. Live Supabase status →
Realtime has fully recovered.
We have stabilised impacted users and enabled improvements to our Realtime infrastructure. We will continue to monitor for full recovery.
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.
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.
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.
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.
We have taken preventative steps to expand our realtime cluster capacity and are continuing to monitor our system stability for full recovery.
We have identified the cause and taken actions to remediate the high latency issues. We will continue to monitor.
We are experiencing increased latency with Realtime and are actively investigating.
Overlapping incidents aren't necessarily related.
Supabase reported 65 incidents in the last 90 days, 24 of them major or critical. A typical incident lasted 2h 2m. See Supabase's uptime and incident history