Live / Supabase / Incident
Supabase: Database Connection Errors
Supabase · supabase.comMinor incidentResolved2026-11-12 23:40 UTC
Public — what happened
Summary
Supabase said that starting at 20:35 UTC on 2026-11-12 some customer databases had more connection errors than normal, and some were unreachable. The company said later that the trouble reached beyond the regions first named, though only some projects were affected. At 22:38 UTC Supabase said it had found the problem and was putting a fix in place, and by 23:03 UTC it reported services recovering and moved to monitoring. The incident was marked resolved at 23:40 UTC.
Timeline
- Started — 2026-11-12 20:35 UTC
- Investigating — 2026-11-12 20:35 UTC (3 updates)
- Identified — 2026-11-12 22:38 UTC
- Monitoring — 2026-11-12 23:03 UTC
- Resolved — 2026-11-12 23:40 UTC · 3h 04m 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 47, 2026, our weekly internet health report.