Live / Supabase / Incident
Supabase: Delayed Log Delivery from 14:10 - 15:30 UTC
Supabase · supabase.comMinor incidentResolved2026-10-28 17:13 UTC
Public — what happened
Summary
Supabase said it had a problem delivering logs between 14:10 and 15:30 UTC, which caused delays of roughly 7 to 8 minutes. In an update posted at 16:21 UTC, the company said most of the affected events had been recovered, while a small number were still being re-added and it would confirm when that finished. The incident, rated minor by Supabase, is now marked resolved as of 17:13 UTC, and no cause was given in the text provided.
Timeline
- Started — 2026-10-28 16:21 UTC
- Monitoring — 2026-10-28 16:21 UTC
- Resolved — 2026-10-28 17:13 UTC · 53 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 45, 2026, our weekly internet health report.