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

- Provider: [Supabase](https://down.guide/providers/supabase)
- Confidence: Confirmed
- Impact: Operational
- lasted 0m
- started 2026-10-21 16:27 UTC
- us, us-east-1
- id: DWN-5364e71c30
- Official page: https://status.supabase.com/incidents/01M5FMMYVR79JACNFDTVJK7C1K

## Updates from Supabase
### 2026-10-10 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.

From the builder: does your app depend on Supabase? [Sazabi](https://www.sazabi.com/?utm_source=down-guide&utm_medium=markdown&utm_content=supabase) detects problems in your own logs without hand-written monitors, and you can ask it in plain language which errors mention Supabase.

---
down.guide reads providers' official status pages every minute and adds its own evidence, always labeled. Free, no account. Agents: MCP at https://down.guide/mcp, REST at https://down.guide/api/v1, feeds at https://down.guide/feed. Built by [Sazabi](https://www.sazabi.com/?utm_source=down-guide&utm_medium=markdown&utm_content=DWN-5364e71c30), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.