No impact incident

Supabase: Management API Postgres config updates overwriting previous updates

Current status of Supabase: Operational — live Supabase status

Timeline

1. Nov 3, 2026, 04:56 UTC
   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. Nov 3, 2026, 05:16 UTC
   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. Nov 3, 2026, 06:17 UTC
   monitoring
   We have identified the cause and are deploying a fix. The dashboard setting that was temporarily disabled will soon be enabled again.
4. Nov 3, 2026, 06:24 UTC
   monitoring
   A fix has been deployed, and the Connection Logging setting that was temporarily disabled on the dashboard is available again.
5. Nov 3, 2026, 07:04 UTC
   resolved
   Connection Logging feature is working fine for all customers now.

Updates as published by Supabase.