A bug in Supabase's Management API caused Postgres configuration updates to overwrite previous changes rather than preserving them, affecting both the API and the Database Settings Dashboard. As a precaution, certain Postgres config options were temporarily disabled on the dashboard during the investigation. A fix was deployed and fully resolved within approximately 2 hours, restoring all affected functionality including Connection Logging.
Trusted by 1,000+ teams
Stop finding out about outages from your users. Monitor 6,320+ cloud services and get alerted the second something breaks.
Connection Logging feature is working fine for all customers now.
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)
With IsDown, you can monitor all your critical services' official status pages from one centralized dashboard and receive instant alerts the moment an outage is detected. Say goodbye to constantly checking multiple sites for updates and stay ahead of outages with IsDown.
Start free trialNo credit card required · Cancel anytime · 6320 services available
Integrations with