Incidentsby IbisIntermittent connection errors via the connection pooler in us-east-1
Oct 21, 16:27 UTCOct 10, 02:10 UTC
Duration
0m
Impact
Informational
Root cause
Dependency
Supabase, 90 days
80 incidents
Affected
Not listed by the vendor.
Final update
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.
Timeline
- Resolved · Oct 10, 02:10 UTC
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.
More from Supabase
Full historyProject lifecycle operation errors in the EU regionstill openProject lifecycle operations such as project creation, pausing, and restoration, in all regionslasted 1h 16mProjects stuck in restarting statelasted 7h 41mSupport Form Errorslasted 1hProject creation errors ap-ne1lasted 1h 22mRealtime latencylasted 45h 26m