Management API Postgres config updates overwriting previous updates
Supabase reports a problem with the Management API. Postgres config changes only save the latest values sent, and later changes overwrite earlier changes. The provider identified the cause and deployed a fix. Supabase is monitoring the result.
State
Monitoring
Started
2 h ago
2026-11-03 04:56 UTC
Ongoing for
1 h 59 min
Worst impact
Notice
Timeline
4 updatesInvestigating
1 h 22 min 69%
Monitoring
37 min 31%
Updates
Times in UTCAs posted by Supabase
A fix has been deployed, and the Connection Logging setting that was temporarily disabled on the dashboard is available again.
We have identified the cause and are deploying a fix. The dashboard setting that was temporarily disabled will soon be enabled again.
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.
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)
Supabase in the last 90 days
Full historyIncidents in 90 days
26
Days with an incident
29
Median duration
1 h 22 min
This incident
1.5× the median
Other Supabase incidents
All incidentsSupabase·Storage uploads failing in us-east-1
Supabase Storage uploads failed with 5xx errors for users in us-east-1. Supabase identified the problem, implemented a fix, and monitored the result. The issue is resolved and it lasted 74 minutes.
Supabase·PG15 -> PG17 Upgrade Failures
This issue is now resolved.
Supabase·Logs degraded in multiple regions
We have deployed the fix for degraded logs, and smoke tests completed successfully at 12:20 UTC. Service is now operating normally. We apologise for the disruption
Supabase·Delayed Log Delivery from 14:10 - 15:30 UTC
This issue has been resolved and log delivery is operational again.
Supabase·Log Drain Issues
This issue is now resolved.
Follow Supabase
Your coding agent knows when Supabase is down, and tells you when a failure is theirs, not yours. You can also get Supabase incidents in a feed reader or in Slack.
Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.
Add it as a remote MCP server named "outages" at https://outages.live/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.
Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "supabase" and tell me if Supabase has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.Paste this into any coding agent. It adds the server with its own MCP setup.
https://outages.live/feed.xml?providers=supabase/feed subscribe https://outages.live/feed.xml?providers=supabaseFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane