Supabase: Delayed Log Delivery from 14:10 - 15:30 UTC
Affected components: Logging & Observability
Timeline of updates
- monitoring
Between 14:10 - 15:30 UTC we have experienced an issue in delivering logs, leading to a delay of about 7–8 minutes. Most affected events have now been recovered - a small subset of events is still being re-inserted and we will confirm once completed.
- resolved
This issue has been resolved and log delivery is operational again.
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-28 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
d40ff3a7ade4286b…Version 2 captured
In the 2026-10-28 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
86b2227744112c65…
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-28 16:21 UTC, resolved after 53 min, 2 update(s); edited after publishing.
- Title
- Delayed Log Delivery from 14:10 - 15:30 UTC
- Vendor
- Supabase
- Date
- URL
- https://rewindex.com/company/supabase/incidents/01M61N1EA48SQQYHEJ5H8XQA2W
Supabase profileRecent Supabase incidentsAll outages on October 28, 2026Supabase in October 2026MarkdownJSON