Supabase: Log Drain Issues
Affected components: Logging & Observability
Timeline of updates
- investigating
Customers using log drains in some regions may be missing some routed logs for a subset of components. We've rolled back changes and are continuing to investigate.
- monitoring
The rollback has restored log drains to normal operation. We will monitor for continued functionality.
- resolved
This issue is now resolved.
Changes Rewindex caught on this incident
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.
First version captured
In the 2026-10-22 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
b6ada704293b974a…Version 2 captured
In the 2026-10-22 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
caec93b0637886fa…Version 3 captured
In the 2026-10-22 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
ad653b00750682dc…
Impact, status and times are the vendor’s own, as last archived. View on status.supabase.com (opens in new tab).
Cite this
Status incident (vendor impact label: minor) posted by Supabase, started 2026-10-22 18:03 UTC, resolved after 47 min, 3 update(s); edited after publishing.
- Title
- Log Drain Issues
- Vendor
- Supabase
- Date
- URL
- https://rewindex.com/company/supabase/incidents/01M5JCGSKAHFMP1Y4YK2QJMGHH
Supabase profileRecent Supabase incidentsAll outages on October 22, 2026Supabase in October 2026MarkdownJSON