rewindex

CompaniesSupabaseIncidents

Supabase: Logs degraded in multiple regions

No impact listedStatus: resolvededitedStarted Resolved (51 min)4 updatesstatus.supabase.com (opens in new tab)

Timeline of updates

  1. investigating

    We are currently investigating degraded Logs functionality in multiple regions. Some users may experience delayed, missing, or unavailable logs in the Dashboard and Logs API.

    Other services, including your database and APIs, are not affected at this time.

    Our team is actively investigating. We'll post another update as soon as we have one.

  2. identified

    We have identified the cause of the Logs degradation and a fix is being prepared.

    Other services remain unaffected.

    We'll post another update as soon as we have one.

  3. monitoring

    A fix has been deployed and we are now monitoring the log service.

    We'll post another update as soon as we have one.

  4. resolved

    We have deployed the fix for degraded logs, and smoke tests completed successfully at 12:20 UTC.

    Service is now operating normally. We apologise for the disruption

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.

Impact, status and times are the vendor’s own, as last archived. View on status.supabase.com (opens in new tab).

Supabase profileRecent Supabase incidentsMarkdownJSON