Live / Supabase / Incident
Supabase: Log Drain Issues
Supabase · supabase.comMinor incidentResolved2026-10-22 18:50 UTC
Public — what happened
Summary
Supabase reported a minor incident, titled Log Drain Issues, in which customers using log drains in some regions might not receive some of their routed logs from a subset of components. The company said it began at 18:03 UTC on 2026-10-22, and that it had already undone recent changes while it kept investigating. By 18:22 UTC Supabase said that undoing those changes had returned log drains to normal and that it would keep watching them, and the incident was marked resolved at 18:50.
Timeline
- Started — 2026-10-22 18:03 UTC
- Investigating — 2026-10-22 18:03 UTC
- Monitoring — 2026-10-22 18:22 UTC
- Resolved — 2026-10-22 18:50 UTC · 47 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 44, 2026, our weekly internet health report.