# upstash redis timeouts **URL:** \ **Category:** Questions / Help\ **Created:** [November 1, 2022, 8:50pm UTC](https://community.fly.io/t/upstash-redis-timeouts/8381 "2022-11-01T20:50:53Z")\ **Posts on this page:** 1\ **Showing post:** 17
**Author:** ![jsierles](https://sea1.discourse-cdn.com/fly1/user_avatar/community.fly.io/jsierles/32/595_2.png) [@jsierles](https://community.fly.io/u/jsierles)\ **Post date:** [November 11, 2022, 3:59pm UTC](https://community.fly.io/t/upstash-redis-timeouts/8381/17 "2022-11-11T15:59:11Z")
Can you try `fly redis connect`? That might help us debug what’s going on here. This is most likely related to the fact that idle connections are timed out. More info here: > [@Redis timeouts](https://community.fly.io/t/redis-timeouts/7232/6): > > Hi @kevin, Managed Redis currently has a relatively short idle timeout that will result in periodic disconnects from applications that are mostly idle. You will need to configure your Redis client to automatically reconnect, for example using the [redis-rb](https://github.com/redis/redis-rb#reconnections) Ruby client, by setting reconnect\_attempts \> 0 and not using disable\_reconnection. Our Rails guide has a [patch](https://fly.io/docs/rails/getting-started/#patching-action-cable-to-handle-redis-timeouts) for use with Action Cable. As noted in the [documentation](https://fly.io/docs/reference/redis/#traffic-routing), the managed Redis instance address is a private IPv6 address. There is n… --- _[View the full topic](https://community.fly.io/t/upstash-redis-timeouts/8381)._