Provider
SupabaseIncident detail
Management API Postgres config updates overwriting previous updates
Resolved incidentMinor
Timeline window
to
Get alerted the next time Supabase breaks
Free email alerts for the handful of vendors you cannot afford to miss. No card, live in about a minute. Paid plans add Slack, Teams, Discord, and webhook delivery across your whole stack, plus higher API quotas.
Timeline
Incident updates
Every update on the official status source, oldest to newest, exactly as it appeared there.
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 or in the Database Settings Dashboard
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.
Monitoring
We have identified the cause and are deploying a fix. The dashboard setting that was temporarily disabled will soon be enabled again.
Monitoring
A fix has been deployed, and the Connection Logging setting that was temporarily disabled on the dashboard is available again.
Resolved
Connection Logging feature is working fine for all customers now.
Keep exploring
More from Supabase
Neighboring incidents on Supabase's timeline and the rest of their record on OutageDeck.