OutageDB

No impact incident

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

Oct 21, 2026, 16:27 UTC
started
02:10 UTC
resolved October 10, 2026
—
duration

Current status of Supabase: Operational — live Supabase status

Timeline

  1. Oct 10, 2026, 02:10 UTC
    resolved
    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.

Updates as published by Supabase.

Other services with incidents at the same time

This was part of a wider event: 109 services reported incidents within the hour.

More Supabase incidents