---
id: "INC-supabase-01M6FW7DHCPTKZK7J5MDGGDHGR"
kind: "incident"
aliases: []
title: "Supabase: Management API Postgres config updates overwriting previous updates"
severity: "low"
cvss: null
epss: null
exploited: false
status: "open"
category: "vendor"
products: [{"name": "Supabase", "fixed": [], "affected": "", "ecosystem": "vendor"}]
ecosystems: ["vendor"]
tags: ["database", "incident", "ops", "postgres", "supabase", "vendor"]
not_affected_if: []
published_at: "2026-11-03T04:56:05+00:00"
first_seen_at: "2026-11-03T04:57:29+00:00"
updated_at: "2026-11-03T05:05:04+00:00"
sources: [{"source": "statuspage", "url": "https://status.supabase.com/incidents/01M6FW7DHCPTKZK7J5MDGGDHGR", "first_seen_at": "2026-11-03T04:57:29+00:00"}]
---

# Supabase: Management API Postgres config updates overwriting previous updates

## Affected

- vendor:Supabase affected ? fixed ?

## Timeline

- 2026-11-03T04:57:29+00:00 statuspage https://status.supabase.com/incidents/01M6FW7DHCPTKZK7J5MDGGDHGR

## From the sources

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)

---

_Free to read at a human pace. An API with keys and an MCP server are in preparation; early access: hello@infrastack.ai_