rewindex

ChangesSupabaseLogs degraded in multiple regions

Supabase: Incident updated: Logs degraded in multiple regions

Incident updateNormal progress (rule, 100%)Changed status.supabase.com (opens in new tab)
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
Before: identified
After: monitoring
AddedUpdatemonitoring#2
Before: not present
After: A fix has been deployed and we are now monitoring the log service. We'll post another update as soon as we have one.

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.

History of this incident

YesterdayFriday, October 30Fri, Oct 30

3 incident changes

All Supabase changesSupabase profileMarkdownJSON