Supabase Stability Performance

Connection-pool exhaustion

Part of the Runtime error logs check

What it is

The logs show SQLSTATE 53300 — too many connections — over the last 24 hours.

Why it matters

The database is refusing new connections, so requests fail regardless of how healthy the application is. In serverless deployments this is usually per-invocation connections rather than genuine traffic growth.

How to fix it

Route serverless and edge clients through the connection pooler, reuse clients at module scope rather than per request, and cap pool sizes. Raising the connection limit treats the symptom.

Run them all on your app

Connect your repo and your live services with read-only scopes. The first scan is free, and nothing changes without your approval.