# Redis timeouts

**URL:** <https://community.fly.io/t/redis-timeouts/7232>\
**Category:** General\
**Created:** [September 18, 2022, 4:50am UTC](https://community.fly.io/t/redis-timeouts/7232 "2022-09-18T04:50:54Z")\
**Posts on this page:** 1\
**Showing post:** 6

<div class="post-metadata">

**Author:** ![wjordan](https://sea1.discourse-cdn.com/fly1/user_avatar/community.fly.io/wjordan/32/1280_2.png) [@wjordan](https://community.fly.io/u/wjordan)\
**Post date:** [September 19, 2022, 4:18pm UTC](https://community.fly.io/t/redis-timeouts/7232/6 "2022-09-19T16:18:58Z")

</div>

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.

> [@rmortes](#):
>
> I’ve not been successful in finding the internal address of the provisioned free Redis, so I ended up deploying a standalone instance.

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 no public address. It’s listed as `Private URL` in the `flyctl redis status` output.  
The older thread you referenced was discussing a standalone app deployment, not the managed product released more recently.

> [@Yaeger](#):
>
> Upstash Redis is a beta product, and when I tried it a few weeks ago it was practically unusable.

The product was only _just_ launched a few weeks ago, and we’ve been working hard on stability and bug-fixing improvements since the initial rollout.

---

_[View the full topic](https://community.fly.io/t/redis-timeouts/7232)._