Realtime latency
Realtime has fully recovered.
The latest update from Supabase.
State
Resolved
Started
19 d ago
2026-10-12 22:59 UTC
Lasted
45 h 26 min
until 2026-10-14 20:25 UTC
Worst impact
Degraded
Timeline
9 updatesInvestigating
1 h 2 min 2%
Monitoring
31 h 13 min 69%
Identified
13 h 10 min 29%
Updates
Times in UTCAs posted by Supabase
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.
Supabase in the last 90 days
Full historyIncidents in 90 days
24
Days with an incident
27
Median duration
1 h 32 min
This incident
30× the median
Other Supabase incidents
All incidentsSupabase·PG15 -> PG17 Upgrade Failures
This issue is now resolved.
Supabase·Logs degraded in multiple regions
We have deployed the fix for degraded logs, and smoke tests completed successfully at 12:20 UTC. Service is now operating normally. We apologise for the disruption
Supabase·Delayed Log Delivery from 14:10 - 15:30 UTC
This issue has been resolved and log delivery is operational again.
Supabase·Log Drain Issues
This issue is now resolved.
Supabase·Elevated Mgmt API Error Rates in Multiple Regions
This issue has been resolved and our response times are back to operational.
Follow Supabase
Your coding agent knows when Supabase is down, and tells you when a failure is theirs, not yours. You can also get Supabase incidents in a feed reader or in Slack.
Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.
Add it as a remote MCP server named "outages" at https://outages.cc/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.
Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "supabase" and tell me if Supabase has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.Paste this into any coding agent. It adds the server with its own MCP setup.
https://outages.cc/feed.xml?providers=supabase/feed subscribe https://outages.cc/feed.xml?providers=supabaseFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane