---
id: "INC-supabase-01M6JARR0HG39EDQ8VZEKV69M4"
kind: "incident"
aliases: []
title: "Supabase: Intermittent errors on Supavisor Shared Pooler in us-east-2"
severity: "medium"
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-11-04T03:48:42+00:00"
first_seen_at: "2026-11-04T03:49:51+00:00"
updated_at: "2026-11-04T04:19:21+00:00"
sources: [{"source": "statuspage", "url": "https://status.supabase.com/incidents/01M6JARR0HG39EDQ8VZEKV69M4", "first_seen_at": "2026-11-04T03:49:51+00:00"}]
---

# Supabase: Intermittent errors on Supavisor Shared Pooler in us-east-2

## Affected

- vendor:Supabase affected ? fixed ?

## Timeline

- 2026-11-04T03:49:51+00:00 statuspage https://status.supabase.com/incidents/01M6JARR0HG39EDQ8VZEKV69M4

## From the sources

Between 2026-11-04 00:02 and 00:50 UTC there were elevated errors on Supavisor Shared Pooler in the us-east-2 region. Errors have subsided and things are back to normal.

Example errors were

```
ClientHandler: (ECHECKOUTFAILED) checkout failed due to %{"C" => "08006", "M" => "Failed to connect to database: {:error, :timeout}

DbHandler: Connection failed {:error, :timeout} to ~c".......us-east-2.compute.internal"
```

---

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