Cases1 case

1 to 1 of 1

1. IL-0307 Supabase's Postgres connection pooler Supavisor 2.0 dropped connections for about 80% of us-east-1 tenants

   Supabase2025

   Symptoms

   At 16:05 UTC on January 29, 2025, most clients connected through Supavisor, Supabase's Postgres connection pooler, in us-east-1 were disconnected and could not reconnect reliably. Connections dropped for about 80% of tenants, and Supabase Storage connectivity also failed until the pooler was fixed.

   Connection resetsIntermittent connection failures

   Trigger

   The planned upgrade of Supavisor to version 2.0 in us-east-1, which completed at 14:46 UTC.

   Root cause

   Faulty deployment

   Component

   Database proxy and connection poolerDatabase

   Contributing factor

   –

   Remediation

   • Rolled Supavisor back to the previous version

   Action items

   • Cut rollback time from 40 minutes to under 90 seconds
   • Detect client disconnections within 2 minutes

   Lessons

   Rollback was too slow and the pooler was not resilient enough to unforeseen failures under load; future work focuses on faster rollbacks to reduce the impact of similar failed deployments.

   View case

By root cause1