Supabase: Incident updated: Log Drain Issues

Incident updateNormal progress (rule, 100%)Changed 2026-10-22 18:23 UTCstatus.supabase.com

Summary

Summary pending. The diff below shows exactly what changed.

Incident page: the full timeline of updates

What changed

~~Struck in red~~ is what Supabase removed; blue is what they added. Muted text is unchanged context.

ChangedStatus#1

~~investigating~~

monitoring

AddedUpdatemonitoring2026-10-22 18:22 UTC#2

not present

The rollback has restored log drains to normal operation. We will monitor for continued functionality.

Compared with the previous archived version of this incident (10 to 30-minute polling). View the live incident (opens in new tab).

Archive proof

Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert. That proves these records existed by then and have not been changed since, by anyone, Rewindex included.

How the archive is checked, and what it cannot prove.

Oct 22
Before captured 18:13 UTC
In the 2026-10-22 checkpoint, timestamped by FreeTSA and DigiCert on Oct 23, 11:49 UTC. Record hash b6ada704293b974a…
Download proof
Oct 22
After captured 18:23 UTC
In the 2026-10-22 checkpoint, timestamped by FreeTSA and DigiCert on Oct 23, 11:49 UTC. Record hash caec93b0637886fa…
Download proof

History of this incident

Thursday, October 22

2 incident changes

Normal progress
18:53Incident
Incident updateLog Drain Issues
Normal progress
18:23Incident
Incident updateLog Drain Issuesthis change

Cite this

Incident updated: Log Drain Issues on Supabase’s status page, changed 2026-10-22 18:23 UTC (change 1 of 2).

Title: Incident updated: Log Drain Issues
Vendor: Supabase
Date: 2026-10-22 18:23 UTC
URL: https://rewindex.com/change/r79a0f467f33b0e

All Supabase changes Supabase profile Markdown JSON