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

> Supabase status incident “Intermittent connection errors via the connection pooler in us-east-1” on 2026-10-10: impact none (vendor’s label), 0 min, 1 update(s). Archived by Rewindex.

Canonical: https://rewindex.com/company/supabase/incidents/01M5FMMYVR79JACNFDTVJK7C1K
Last updated: 2026-10-10T02:10:00Z

- Impact (vendor’s label): none
- Status: resolved
- Started: 2026-10-10 02:10 UTC · Resolved: 2026-10-10 02:10 UTC · Duration: 0 min
- Updates: 1
- [Vendor status page: https://status.supabase.com/incidents/01M5FMMYVR79JACNFDTVJK7C1K](https://status.supabase.com/incidents/01M5FMMYVR79JACNFDTVJK7C1K)
- [Company: Supabase](https://rewindex.com/company/supabase.md)

## Part of an outage event

- [AWS us-east-1 outage, Oct 9, 2026: 11 vendors, 12 incidents](https://rewindex.com/events/2026-10-09-aws-us-east-1)
- This incident blames AWS as the cause. (hop 1, posted +3 h 37 min vs the first vendor naming AWS)
- Evidence: “…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…”

```mermaid
flowchart LR
  root["AWS us-east-1<br/>own incident not archived"]:::inferred
  h1["Within an hour<br/>5 vendors, 2 blamed AWS<br/>Convex, Temporal Cloud, JFrog, PlanetScale +1"]:::blames
  root --> h1
  h4["1 to 4 hours later<br/>1 vendor, 1 blamed AWS<br/>Supabase"]:::blames
  root --> h4
  later["Later<br/>1 vendor, 1 blamed AWS<br/>Chargebee"]:::blames
  root --> later
  dr["Known dependency<br/>2 vendors<br/>Bandwidth, Sprout Social"]:::hop2
  root -.->|"depends on AWS"| dr
  me["Supabase (this incident)<br/>posted +3 h 37 min"]:::me
  h4 --- me
```

_Detected automatically from incidents that started together and named the same provider; a link means one incident named another vendor, not a confirmed cause._

## Timeline of updates

- **resolved** 2026-10-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.

## Cite this

Status incident (vendor impact label: none) posted by Supabase, started 2026-10-10 02:10 UTC, resolved after 0 min, 1 update(s).

- Canonical URL: https://rewindex.com/company/supabase/incidents/01M5FMMYVR79JACNFDTVJK7C1K
- Citation: Supabase, “Intermittent connection errors via the connection pooler in us-east-1” (2026-10-10 02:10 UTC). Archived by Rewindex: https://rewindex.com/company/supabase/incidents/01M5FMMYVR79JACNFDTVJK7C1K (CC BY 4.0).
- Markdown link: `[Supabase: Intermittent connection errors via the connection pooler in us-east-1 (2026-10-10)](https://rewindex.com/company/supabase/incidents/01M5FMMYVR79JACNFDTVJK7C1K)`


---
Canonical: https://rewindex.com/company/supabase/incidents/01M5FMMYVR79JACNFDTVJK7C1K · Markdown: https://rewindex.com/company/supabase/incidents/01M5FMMYVR79JACNFDTVJK7C1K.md · JSON: https://rewindex.com/api/v1/companies/supabase/incidents/01M5FMMYVR79JACNFDTVJK7C1K · Data licensed CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/) · Generated 2026-11-05T15:18:13.544Z