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

Source of record: provider status page. Summary written by SquidGrid from the provider’s published updates; times in UTC.

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 see
Customers 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.

The full archive is on the Supabase status & history page.

Related: Supabase status & history. SquidGrid is not affiliated with Supabase.