Supabase · Data and observabilityMay 9, 2026, 15:00 UTC

Error spikes in one of the eu-central-1 Supavisor clusters

MinorNot disclosedUpdated 47d ago

May 9, 15:00 UTCMay 9, 15:00 UTC

Duration

Impact

Minor

Root cause

Not disclosed

Supabase, 90 days

56 incidents

Affected

Not listed by the vendor.

Status page

Final update

Between 15:25 and 15:33 and between 15:38 and 15:41 we observed error spikes in one of the eu-central-1 Supavisor clusters. Users reported failures in connecting to postgres via Supavisor Errors reported: ClientHandler: (ECHECKOUTTIMEOUT) unable to check out connection from the pool after 15000ms in Transaction mode

Timeline

Resolved · May 9, 15:00 UTC
Between 15:25 and 15:33 and between 15:38 and 15:41 we observed error spikes in one of the eu-central-1 Supavisor clusters. Users reported failures in connecting to postgres via Supavisor Errors reported: ClientHandler: (ECHECKOUTTIMEOUT) unable to check out connection from the pool after 15000ms in Transaction mode

More from Supabase

Full history

NoticeNov 8, 10:53 UTC

Interruption in connections to Supavisor in eu-west-2lasted 1h 42m

MinorNov 6, 23:49 UTC

Increased Errors with Project Lifecycle Operations in US-West-2lasted 2h 28m

MinorNov 5, 23:12 UTC

Intermittent 502/503 errors for pg_net calls to Edge Functionslasted 42m

MinorNov 4, 18:43 UTC

Storage issues in us-east-1 and eu-central-1lasted 16h 18m

MinorNov 4, 03:48 UTC

Intermittent errors on Supavisor Shared Pooler in us-east-2lasted 29m

NoticeNov 3, 04:56 UTC

Management API Postgres config updates overwriting previous updateslasted 2h 8m