---
id: "INC-supabase-01M5FMMYVR79JACNFDTVJK7C1K"
kind: "incident"
aliases: []
title: "Supabase: Intermittent connection errors via the connection pooler in us-east-1"
severity: "low"
cvss: null
epss: null
exploited: false
status: "resolved"
category: "vendor"
products: [{"name": "Supabase", "fixed": [], "affected": "", "ecosystem": "vendor"}]
ecosystems: ["vendor"]
tags: ["database", "incident", "ops", "postgres", "supabase", "vendor"]
not_affected_if: []
published_at: "2026-10-21T16:27:59+00:00"
first_seen_at: "2026-10-23T19:12:22+00:00"
updated_at: "2026-10-23T20:09:50+00:00"
sources: [{"source": "statuspage", "url": "https://status.supabase.com/incidents/01M5FMMYVR79JACNFDTVJK7C1K", "first_seen_at": "2026-10-23T19:12:22+00:00"}]
---

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

## Affected

- vendor:Supabase affected ? fixed ?

## Timeline

- 2026-10-23T19:12:22+00:00 statuspage https://status.supabase.com/incidents/01M5FMMYVR79JACNFDTVJK7C1K

## From the sources

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.

---

_Free to read at a human pace. An API with keys and an MCP server are in preparation; early access: hello@infrastack.ai_