# Management API Postgres config updates overwriting previous updates

- Provider: [Supabase](https://down.guide/supabase)
- Level: confirmed
- Impact: Degraded
- lasted 2h 8m
- started 2026-11-03 04:56 UTC
- id: DWN-acf7f11f1a
- Official page: https://status.supabase.com/incidents/01M6FW7DHCPTKZK7J5MDGGDHGR

## Updates from Supabase
### 2026-11-03 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)

### 2026-11-03 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.

### 2026-11-03 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.

### 2026-11-03 06:24 UTC: monitoring
A fix has been deployed, and the Connection Logging setting that was temporarily disabled on the dashboard is available again.

### 2026-11-03 07:04 UTC: resolved
Connection Logging feature is working fine for all customers now.

---
down.guide reads providers' official status pages every minute and adds its own evidence, always labeled. Free, no account. Agents: MCP at https://down.guide/mcp, REST at https://down.guide/api/v1, feeds at https://down.guide/feed. Built by Sazabi (https://sazabi.com/?utm_source=down-guide&utm_medium=markdown).