// troubleshooting guide · redis cloud
Redis Cloud ERR max number of clients reached
- Status
- Ongoing
- platforms:
- All clients
- updated:
- November 15, 2026
- reports:
- 3
- Method
- how we research
RUNBOOK · redis-cloud/max-connections-reached2 FIXES
// quick answer
You exceeded the connection cap of your plan. Free is limited to a small number of connections; fix by pooling and closing connections, or upgrade.
Most likely fix: Reuse one client
How to fix it
// try these in order, the most common fix is first
FIX 1Reuse one client
- 01Create the client outside the request handler
- 02Use a connection pool with a max size
- 03Call quit/close on shutdown
Did this fix it?FIX 2Upgrade or use a proxy
- 01Check the connections limit in your plan details
- 02Move to Essentials or Pro for higher limits
- 03On serverless consider an HTTP-based alternative like Upstash
Did this fix it?
Symptoms
'ERR max number of clients reached' or random connection errors under load, often on serverless.
Why it happens
- C-01Each serverless invocation opens a new connection
- C-02No connection pooling
- C-03Leaked connections
// this guide also covers
- redis max number of clients reached
- redis cloud too many connections
Still not working?
If Redis Cloud keeps failing, you're not alone. See every Redis Cloud problem users report or the alternatives people switch to.
Have an app idea? Our small team builds any software: web and mobile apps, games, desktop, AI tools. Price agreed together.
Talk to usThe same problem in other apps
All not loading, error messages & connection guides →
Upstash Redis ECONNRESET Error (Upstash)
Other Redis Cloud errors
- Redis Cloud Connection Timeout
- Redis Cloud Connection Refused
- Redis Cloud WRONGPASS / NOAUTH Authentication Error
- Redis Cloud SSL / TLS Connection Error
- Redis Cloud OOM command not allowed when used memory > maxmemory
- Why Is Redis Cloud Slow / High Latency
- Redis Cloud Cannot Connect From My IP (Allowlist / Source IP)
- Redis Cloud Data Lost / Keys Disappeared