Skip to main content
Supabase

pgBouncer issues on some older projects

Degraded Lasted 22h 35m · started · Supabase's page

Level
confirmed
Worst impact
Degraded
Down Index
23of 100

What to do

  • Check whether your product depends on Supabase. Check your stack

    Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.
  • Confirm your retries, queues and scheduled jobs caught up after the 22h 35m it lasted.

    Anything that failed between 2026-08-26 19:49 UTC and 2026-08-27 18:24 UTC may need a replay.
  • Subscribe to Supabase's feed to hear about the next one first. RSS feed

    https://down.guide/feed?provider=supabase works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from Supabase 7

  1. investigating

    Some users on older Projects are experiencing a pgBouncer configuration issue causing connection issues for the Dedicated Pooler and Storage services. This issue should only affect users with Project versions 15.1 and older. We have determined the cause of this issue and we are rolling out a fix.

    provider

  2. investigating

    Some users on Project versions 15.1 and older are experiencing a pgBouncer configuration issue causing connection issues for the Dedicated Pooler and Storage services. We are continuing our investigation of this issue.

    provider

  3. identified

    This issue is fixed in eu-central-2 and ap-south-1. We are continuing to rollout the fix to all regions.

    provider

  4. identified

    We are continuing to rollout the fix to further regions.

    provider

  5. identified

    An enhanced automated solution is currently being tested in staging. It is expected to be more effective and efficient than the approach used previously. Once testing has completed successfully, we will use this approach to roll out the fix in production. We will provide further updates as this work progresses.

    provider

  6. monitoring

    A fix has been rolled out across all regions, and results are positive. We will continue monitoring to ensure the service remains stable. Moving this incident to monitoring.

    provider

  7. resolved

    The fix has remained stable across all regions, and the issue has been resolved.

    provider

Reports count in aggregate; nothing about you is shown.

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.

Questions about DWN-7a5cc2409c

Is Supabase still down?

No, this incident was resolved 2026-08-27 18:24 UTC. For Supabase's live state, see https://down.guide/supabase.

How long did it last?

22h 35m, from 2026-08-26 19:49 UTC to 2026-08-27 18:24 UTC, by the times Supabase posted.

What caused it?

Supabase hasn't published a root cause. If it does, it shows here.

Where does this come from?

Supabase's official status page, https://status.supabase.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.