WhatBrokeToday
Today's Trends
minorArchivedSupabase

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

  1. Investigating(done)
  2. Trending(skipped)
  3. Workaround available(skipped)
  4. Resolved(done)
  5. Archived

Executive summary

Between 22:10 and 22:51 UTC on October 9, 2026, about 1% of new database connections via the Shared Pooler (Supavisor) in us-east-1 failed with 'Failed to connect to database' timeout errors. The issue was caused by a cloud provider incident affecting network traffic between availability zones.

No verified workaround yet

This incident was resolved upstream without a reported workaround.

Official fix
Technical root cause

Under active investigation. No report has identified a root cause yet.

Evidence

1 report · 1 StatusShow
  1. [1]
    Status First report
    Intermittent connection errors via the connection pooler in us-east-1(opens official status page in a new tab)

    Status: 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…

    by supabase status

Timeline

  1. First report on status page

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

    Source
  2. Official statement

    Status: 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.

    Source
  3. Status changed

    Status changed: new → archived (resolved more than 14 days ago).