Live  /  Supabase  /  Incident

Supabase: Management API Postgres config updates overwriting previous updates

Supabase · supabase.comResolved2026-11-03 07:04 UTC
Public — what happened

Summary

Supabase said a problem with its Management API caused Postgres configuration changes to keep only the most recent values sent, so earlier changes were being overwritten. The report began at 04:56 UTC on 2026-11-03, and the company asked customers to hold off on making such changes through the API or the dashboard's database settings, and later disabled certain config changes on the dashboard. Supabase said it identified the cause and deployed a fix by 06:24 UTC, when the temporarily disabled Connection Logging setting became available again, and it marked the incident resolved at 07:04.

Timeline

Source of record: provider status page. Summary written by SquidGrid from the provider’s published updates; times in UTC.

Independent path health

The status page is the symptom. SquidGrid measures the paths that reach Supabase against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.

🔒 Sign in to see
Customers get the live Provider Assessment Report for Supabase: its full incident track record, what tends to break, and recent public reports of problems.

Included with any paid plan.

Open the Supabase report →

More from Supabase

Covered in The Squid’s Ink, Week 46, 2026, our weekly internet health report.

The full archive is on the Supabase status & history page.

Related: Supabase status & history. SquidGrid is not affiliated with Supabase.