Live / Supabase / Incident
Supabase: Logs degraded in multiple regions
Supabase · supabase.comResolved2026-10-30 12:29 UTC
Public — what happened
Summary
Supabase said its Logs feature was degraded in multiple regions starting at 11:38 UTC on 2026-10-30, meaning some users could see logs that were late, missing, or unavailable in the Dashboard and Logs API. The company stated that other services, including databases and APIs, were not affected. By 11:56 UTC it said it had identified the cause and was preparing a fix, and at 12:11 UTC it said a fix was deployed and it was monitoring. The incident was marked resolved at 12:29 UTC.
Timeline
- Started — 2026-10-30 11:38 UTC
- Investigating — 2026-10-30 11:38 UTC
- Identified — 2026-10-30 11:56 UTC
- Monitoring — 2026-10-30 12:11 UTC
- Resolved — 2026-10-30 12:29 UTC · 51 min 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 45, 2026, our weekly internet health report.