Supabase outage on October 12, 2026: Realtime latency

Supabase reported an incident affecting Supabase for 1 day 21 hours on 12 October 2026, from 22:59 to 20:25 UTC.

supabase.com All times UTC

Resolved

Official incident reported by Supabase

Started: 22:59; 12 Oct 2026 UTC
Resolved: 20:25; 14 Oct 2026 UTC
Duration: 1d 21h; 1 day 21 hours
Impact: Minor; as rated by Supabase
Updates: 9; posted by Supabase

Timeline

All times UTC.

Official incident from Supabase

Realtime latency

Resolved Minor impact 12 Oct 2026 22:59 UTC View on Supabase's status page

12 Oct 22:59 Official
Investigating
We are experiencing increased latency with Realtime and are actively investigating.
13 Oct 00:02 Official
Monitoring
We have identified the cause and taken actions to remediate the high latency issues. We will continue to monitor.
13 Oct 06:38 Official
Monitoring
We have taken preventative steps to expand our realtime cluster capacity and are continuing to monitor our system stability for full recovery.
13 Oct 13:49 Official
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.
13 Oct 17:34 Official
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.
13 Oct 21:15 Official
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.
13 Oct 23:27 Official
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.
14 Oct 03:00 Official
Monitoring
We have stabilised impacted users and enabled improvements to our Realtime infrastructure. We will continue to monitor for full recovery.
14 Oct 20:25 Official
Resolved
Realtime has fully recovered.

"Official" rows are quoted from Supabase's public status page, status.supabase.com. Very long posts are shortened.

What our checkpoints saw

HostTracker's checkpoints, which test supabase.com from several locations, recorded no outage of 5 minutes or longer during this incident. A provider can report a problem that affects only some features, regions or accounts, which a check of the main address does not see. The live Supabase status shows what our checks see right now.

All Supabase incidents Live Supabase status Every service we track

Does your product depend on Supabase?

An outage like this one reaches your users through your product, and most teams hear about it from a customer rather than from a dashboard. HostTracker watches any endpoint you name - your own site, an API you call, a vendor you resell - from 300+ locations, confirms a failure from several of them before it says anything, and then tells you by email, SMS, voice call or your chat tool.

You get the same record you are reading here for your own services: every outage timestamped, with the checks that observed it.

Start monitoring free Check another address

Independent measurement by HostTracker. Not affiliated with Supabase. Official updates are quoted from Supabase's public status page and remain Supabase's own words.