Live / Supabase / Incident
Supabase: Realtime latency
Supabase · supabase.comMinor incidentResolved2026-10-14 20:25 UTC
Public — what happened
Summary
Supabase reported slower-than-normal response times in its Realtime service beginning on 2026-10-12 at 22:59 UTC, and rated the incident as minor. About an hour later the company said it had found the cause and applied a fix, and it later added capacity to its Realtime cluster as a precaution. On 2026-10-13 the problem returned, with Supabase saying the presence feature was unstable and users might have trouble joining, and that most affected customers had recovered by that evening while some regions still had issues. Supabase said it had stabilized affected users by 03:00 UTC on 2026-10-14 and marked the incident resolved at 20:25 that day.
Timeline
- Started — 2026-10-12 22:59 UTC
- Investigating — 2026-10-12 22:59 UTC
- Monitoring — 2026-10-13 00:02 UTC (2 updates)
- Identified — 2026-10-13 13:49 UTC (4 updates)
- Monitoring — 2026-10-14 03:00 UTC
- Resolved — 2026-10-14 20:25 UTC · 45h 26m after it started
With SquidGrid — where it starts on the route
Independent path health
The status page is the symptom. SquidGrid measures the paths that reach Supabase against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.
🔒 Sign in to seeCustomers get the live Provider Assessment Report for Supabase: its full incident track record, what tends to break, and recent public reports of problems.
Included with any paid plan.
Open the Supabase report →
More from Supabase
Covered in The Squid’s Ink, Week 43, 2026, our weekly internet health report.