# Error spikes in one of the eu-east-1 Supavisor clusters

- Provider: [Supabase](https://down.guide/providers/supabase)
- Confidence: Confirmed
- Impact: Degraded
- lasted 0m
- started 2026-08-24 05:39 UTC
- eu, eu-east-1
- Supabase states the impact was 2026-08-24 04:54 to 04:58 UTC (4m)
- id: DWN-762aeaeba6
- Official page: https://status.supabase.com/incidents/01M0S61KGF8FXH6TAMAM7NBSN1

## Updates from Supabase
### 2026-08-24 05:39 UTC: resolved
Between 04:54 and 04:58 UTC we observed error spikes in one of the eu-east-1 Supavisor clusters. Users would have experienced errors in connecting to postgres via Supavisor. The issue has since recovered.
Errors reported: ClientHandler: (ECHECKOUTTIMEOUT) unable to check out connection from the pool after 15000ms in Transaction mode.

From the builder: does your app depend on Supabase? [Sazabi](https://www.sazabi.com/?utm_source=down-guide&utm_medium=markdown&utm_content=supabase) detects problems in your own logs without hand-written monitors, and you can ask it in plain language which errors mention Supabase.

---
down.guide reads providers' official status pages every minute and adds its own evidence, always labeled. Free, no account. Agents: MCP at https://down.guide/mcp, REST at https://down.guide/api/v1, feeds at https://down.guide/feed. Built by [Sazabi](https://www.sazabi.com/?utm_source=down-guide&utm_medium=markdown&utm_content=DWN-762aeaeba6), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.