Supabase outage on November 3, 2026: Management API Postgres config updates overwriting previous updates
Supabase has reported an incident affecting Supabase since 04:56 UTC on 3 November 2026 (2 hours so far).
Open
Official incident reported by Supabase
- Started
- 04:56
- 3 Nov 2026 UTC
- Status
- Open
- not resolved yet
- Duration
- 2h
- 2 hours so far
- Impact
- -
- as rated by Supabase
- Updates
- 4
- posted by Supabase
Timeline
All times UTC.
Official incident from Supabase
Management API Postgres config updates overwriting previous updates
-
Official
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](https://supabase.com/docs/reference/api/introduction) or in the [Database Settings Dashboard](https://supabase.com/dashboard/project/\_/database/settings)
-
Official
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.
-
Official
Monitoring
We have identified the cause and are deploying a fix. The dashboard setting that was temporarily disabled will soon be enabled again.
-
Official
Monitoring
A fix has been deployed, and the Connection Logging setting that was temporarily disabled on the dashboard is available again.
"Official" rows are quoted from Supabase's public status page, status.supabase.com. Very long posts are shortened.
What our checkpoints saw
HostTracker's checkpoints, which test supabase.com from several locations, recorded no outage of 5 minutes or longer during this incident. A provider can report a problem that affects only some features, regions or accounts, which a check of the main address does not see. The live Supabase status shows what our checks see right now.
Does your product depend on Supabase?
An outage like this one reaches your users through your product, and most teams hear about it from a customer rather than from a dashboard. HostTracker watches any endpoint you name - your own site, an API you call, a vendor you resell - from 300+ locations, confirms a failure from several of them before it says anything, and then tells you by email, SMS, voice call or your chat tool.
You get the same record you are reading here for your own services: every outage timestamped, with the checks that observed it.
Independent measurement by HostTracker. Not affiliated with Supabase. Official updates are quoted from Supabase's public status page and remain Supabase's own words.