Redis command timed out / ETIMEDOUT / Command timed out Redis Origin: Data OSI layer 7 · Application Last updated 5 Nov 2026

Redis client: Error: Command timed out / redis.exceptions.TimeoutError: Timeout reading from socket

The client waited longer than its timeout for a Redis reply.

Exact message you may see Error: Command timed outredis.exceptions.TimeoutError: Timeout reading from socketredis.exceptions.TimeoutError: Timeout reading from ('host', 6379)io.lettuce.core.RedisCommandTimeoutException: Command timed out after 1 minute(s)redis.clients.jedis.exceptions.JedisConnectionException: java.net.SocketTimeoutException: Read timed out
Explore the map of this error Full error map →
Seen on: Redis Java Python

Meaning

Either Redis is slow/blocked (slow commands, persistence fork, CPU, swap) or the network is lossy. Check SLOWLOG, INFO commandstats, latency (redis-cli --latency), and server load. Tune client timeouts, avoid blocking calls without timeouts, and reduce huge payloads.

Common causes

  • Slow commands blocking the server
  • Network latency/packet loss
  • Server overloaded or swapping
  • Timeout set too low
  • Large values or big pipelines

⚡ Quick fix

  1. redis-cli --latency -h HOST to measure
  2. Inspect SLOWLOG GET and server load
  3. Raise client timeouts moderately; break up large operations

Detailed fix by platform

Linux

  1. redis-cli --latency -h HOST; redis-cli SLOWLOG GET 5

How to diagnose

  1. Latency — Measured?
  2. Server — Blocked/slow?
  3. Timeout — Appropriate?

🔧 Still not fixed?

Many errors look alike. If the steps above didn’t solve it, one of these is probably what you’re facing:

Where this error sits

Origin: Data. Errors that are often confused with or caused by this one (click to open):

BUSY Redis is busy running a script — Redis: (error) BUSY Redis is busy running a script. You can only call SCRIPT KILL or SHUTDOWN NOSAVE (Redis)BUSY Redis is busy ru…Client output buffer limit reached (scheduled to be closed) — Redis: Client id=12 addr=10.0.0.5:51234 scheduled to be closed ASAP for overcoming of output buffer limits (Redis)Client output buffer …cURL error 28: Operation timed out (Laravel HTTP client) — Laravel: Illuminate\Http\Client\ConnectionException: cURL error 28: Operation timed out after 30001 milliseconds with 0 bytes received (Laravel)cURL error 28: Operat…ECONNRESET / Connection reset by peer on idle Redis connection — Redis: Error: read ECONNRESET / redis.exceptions.ConnectionError: Connection reset by peer after idle time (Redis)ECONNRESET / Connecti…MasterNotFoundError: No master found for 'mymaster' (Sentinel) — redis-py: redis.sentinel.MasterNotFoundError: No master found for 'mymaster' / ioredis: All sentinels are unreachable (Redis)MasterNotFoundError: …Maximum execution time of 30 seconds exceeded — Laravel: Symfony\Component\ErrorHandler\Error\FatalError: Maximum execution time of 30 seconds exceeded (Laravel)Maximum execution tim…Only (P|S)SUBSCRIBE / (P|S)UNSUBSCRIBE / PING / QUIT allowed in this context — Redis: ERR Can't execute 'get': only (P|S)SUBSCRIBE / (P|S)UNSUBSCRIBE / PING / QUIT / RESET are allowed in this context (Redis)Only (P|S)SUBSCRIBE /…Redis closes idle clients (timeout setting) — Redis: Closing idle client / Connection closed by server after timeout 300 (Redis)Redis closes idle cli…Redis com…

Explore the map of this error Full error map →

🧠 Still stuck? Analyze your error

Paste the full message, response headers or stack trace — we'll detect the platform and point to the most likely cause.

💬 What worked for others

No tips yet — did something else fix this for you?

Share what worked for you

Tips are checked by an editor before they appear. Links are removed.