rewindex

CompaniesSupabaseIncidents

Supabase: Management API Postgres config updates overwriting previous updates

No impact listedStatus: resolvededitedStarted Resolved (2.1 h)5 updatesstatus.supabase.com (opens in new tab)

Timeline of updates

  1. investigating

    We are actively correcting an issue with the Management API:

    • Postgres Config changes only save the latest values sent, past changes are not being saved

    For now please refrain from not making any Postgres Config changes via the Management API: https://supabase.com/docs/reference/api/introduction (opens in new tab) or in the Database Settings Dashboard: https://supabase.com/dashboard/project/_/database/settings (opens in new tab)

  2. investigating

    We are actively correcting an issue with the Management API:

    • Postgres Config changes only save the latest values sent. Past changes are being overwritten

    For now, we have disabled making certain Postgres config changes on the dashboard until the issue is resolved.

  3. monitoring

    We have identified the cause and are deploying a fix. The dashboard setting that was temporarily disabled will soon be enabled again.

  4. monitoring

    A fix has been deployed, and the Connection Logging setting that was temporarily disabled on the dashboard is available again.

  5. resolved

    Connection Logging feature is working fine for all customers now.

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.

How the archive is checked, and what it cannot prove.

Rewindex captured this after the last checkpoint; the next run () commits it.

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