Supabase incident

Issues propagating Postgres configuration updates

Resolved after 2 hours 50 minutes, on March 17, 2026.

monitoring Mar 17, 2026, 07:07 AM UTC

A fix has been implemented and we are monitoring.

Started
Mar 17, 2026, 04:50 AM UTC
Resolved
Mar 17, 2026, 07:41 AM UTC
Duration
2h 50m
Detected by Pingoru
Mar 17, 2026, 04:50 AM UTC

Update timeline

  1. investigating Mar 17, 2026, 04:50 AM UTC

    Some custom Postgres configurations applied through the Supabase CLI are not currently taking effect for projects running Postgres version 17.6.1.084. Projects that do not use CLI-managed Postgres configurations, or that are running earlier Postgres versions, are not affected.

  2. identified Mar 17, 2026, 05:11 AM UTC

    We have identified the root cause and are currently working on a fix.

  3. monitoring Mar 17, 2026, 07:07 AM UTC

    A fix has been implemented and we are monitoring.

  4. resolved Mar 17, 2026, 07:41 AM UTC

    This incident has been resolved.

Your product runs on more than Supabase

Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.

Add your stack →