rewindex

CompaniesSupabaseIncidents

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

No impact listedStatus: resolvedStarted Resolved (0 min)1 updatestatus.supabase.com (opens in new tab)
Part of an outage event

AWS us-east-1 outage, Oct 9, 2026 · 11 vendors, 12 incidents

Supabase’s incident blames AWS as the cause. (hop 1, posted +3 h 37 min vs the first vendor naming AWS)

“…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…”

Swipe sideways to see the whole diagram.

depends on AWSAWS us-east-1own incident not archivedWithin an hour5 vendors, 2 blamed AWSConvex, Temporal Cloud, JFrog, PlanetScale +11 to 4 hours later1 vendor, 1 blamed AWSSupabaseLater1 vendor, 1 blamed AWSChargebeeKnown dependency2 vendorsBandwidth, Sprout SocialSupabase (this incident)posted +3 h 37 min
depends on AWSAWS us-east-1own incident not archivedWithin an hour5 vendors, 2 blamed AWSConvex, Temporal Cloud,JFrog, PlanetScale +11 to 4 hours later1 vendor, 1 blamed AWSSupabaseLater1 vendor, 1 blamed AWSChargebeeKnown dependency2 vendorsBandwidth, Sprout SocialSupabase (this incident)posted +3 h 37 min
Supabase is outlined in red. Groups show up to a few vendors each; the event page lists every incident.
Mermaid source
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

Full event: timeline, evidence and all vendors →

Detected automatically from incidents that started together and named the same provider. A link means one vendor’s incident named another, not a confirmed cause.

Timeline of updates

  1. 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.

Archive proof

Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert. That proves this record existed by then and has not been changed since, by anyone, Rewindex included.

How the archive is checked, and what it cannot prove.

Impact, status and times are the vendor’s own, as last archived. View on status.supabase.com (opens in new tab).

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).

Title
Intermittent connection errors via the connection pooler in us-east-1
Vendor
Supabase
Date
URL
https://rewindex.com/company/supabase/incidents/01M5FMMYVR79JACNFDTVJK7C1K

Supabase profileRecent Supabase incidentsAll outages on October 10, 2026Supabase in October 2026MarkdownJSON