Supabase incident

Management API Postgres config updates overwriting previous updates

Informational Resolved

Started

November 3, 2026 at 04:56 AM UTC

Duration

2h 8m

Resolved

November 3, 2026 at 07:04 AM UTC

Updates timeline

  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) or in the [Database Settings Dashboard](https://supabase.com/dashboard/project/\_/database/settings)

  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.

Get an email the next time Supabase goes down

Outage alerts for Supabase, straight to your inbox. No account needed, unsubscribe in every email.

Watching more than one service? A free account covers 5 services + a daily digest — and Pro is currently free.

Live Supabase status

Current indicator + 24h latency

All incidents

Cross-service timeline

Subscribe via RSS

Atom feed for any reader