Intermittent connection errors via the connection pooler in us-east-1

Summary

Intermittent connection errors via the connection pooler in us-east-1

Between 22:10 and 22:51 UTC on October 9, 2026, about 1% of new database connections made through the Shared Pooler (Supavisor) in us-east-1 failed with "Failed to connect to database" timeout errors. The cause of the failures was an incident at our cloud provider which affected network traffic between availability zones. Supabase Project databases were not affected, and connections that had already been open prior to the incident remained open. The issue was resolved at 22:51 UTC. Clients that retried on connection errors would have reconnected successfully.

• Started

  Oct 21, 2026 · 4:27 PM

• Resolved

  Oct 10, 2026 · 2:10 AM

• Duration

  11d 14h 17m

• Severity

  None

• ✓

  Resolved

  Oct 21 · 4:27 PM Supabase

  Between 22:10 and 22:51 UTC on October 9, 2026, about 1% of new database connections made through the Shared Pooler (Supavisor) in us-east-1 failed with "Failed to connect to database" timeout errors. The cause of the failures was an incident at our cloud provider which affected network traffic between availability zones. Supabase Project databases were not affected, and connections that had already been open prior to the incident remained open. The issue was resolved at 22:51 UTC. Clients that retried on connection errors would have reconnected successfully.