Supabase outage, 3 November 2026

Management API Postgres config updates overwriting previous updates

Started
Status
Ongoing: Investigating
Impact
Not stated

Is this still happening?

Yes. Supabase still lists it as investigating; last update 3 Nov 2026, 05:16 UTC.

Right now: Supabase reports all systems operational. (as of 3 Nov, 06:06 UTC) Live Supabase status

Last update from Supabase

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.

3 Nov 2026, 05:16 UTC

Similar Supabase incidents

Earlier incidents with the same affected part or wording - useful to see how long this kind of problem usually takes.

  1. , resolved after 1 h 10 min

    Increased errors on management api leading to project operation failures

Other recent Supabase incidents

  1. Storage uploads failing in us-east-1

  2. PG15 -> PG17 Upgrade Failures

  3. Logs degraded in multiple regions

  4. Delayed Log Delivery from 14:10 - 15:30 UTC

  5. Log Drain Issues

  6. Elevated Mgmt API Error Rates in Multiple Regions

  7. Elevated Mgmt API Error Rates in Multiple Regions

  8. Project lifecycle operation errors in the EU region

All recorded Supabase incidents