Live / Supabase / Incident
Supabase: Log ingestion impaired
Supabase · supabase.comMinor incidentResolved2026-10-13 01:30 UTC
Public — what happened
Summary
Supabase reported a minor problem with log ingestion beginning at 19:39 UTC on October 12, 2026, saying logs could arrive late or not show up at all. About half an hour later the company said it had pinpointed the issue, though it did not describe a cause, and by 20:56 UTC it reported that a fix was being applied and traffic was starting to recover. Supabase said at 00:35 UTC on October 13 that the fix was complete and logging was working normally again, and the incident was marked resolved at 01:30.
Timeline
- Started — 2026-10-12 19:39 UTC
- Investigating — 2026-10-12 19:39 UTC
- Identified — 2026-10-12 20:09 UTC (4 updates)
- Monitoring — 2026-10-13 00:35 UTC
- Resolved — 2026-10-13 01:30 UTC · 5h 51m 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.