# Zero downtime deployment

**URL:** <https://community.fly.io/t/zero-downtime-deployment/7971>\
**Category:** General\
**Created:** [October 18, 2022, 6:48pm UTC](https://community.fly.io/t/zero-downtime-deployment/7971 "2022-10-18T18:48:06Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![ignoramous](https://avatars.discourse-cdn.com/v4/letter/i/a9adbd/32.png) [@ignoramous](https://community.fly.io/u/ignoramous)\
**Post date:** [October 18, 2022, 10:39pm UTC](https://community.fly.io/t/zero-downtime-deployment/7971/3 "2022-10-18T22:39:09Z")

</div>

> [@stayallive](#):
>
> There are ~30 seconds between the request on the previous version and the next one, however it takes until `18:35:55` (so a full minute) before service is stable again with intermittent timeouts.

May be this post has some _more_ insights (even if it could be outdated): [High availability on Fly.io - #3 by kurt](https://community.fly.io/t/high-availability-on-fly-io/3448/3)

> [@stayallive](#):
>
> Is zero downtime deployment possible currently?

Only if one is running _multi-region_ Fly apps, does `fly deploy --strategy rolling <other-args>` prevent outages from client PoV ([ref](https://community.fly.io/t/liveview-app-unavailable-for-2-minutes-after-deployment/3753/14))?

I am compelled to point out that, [Machine app](https://community.fly.io/t/were-launching-fly-machines-today/5305) instances get [fixed `6pn` (private) IPs](https://community.fly.io/t/leftover-dns-records/6319/4) across deploys (unlike regular Fly apps unless they [‘anchor’ themselves to a host](https://community.fly.io/t/can-an-instance-have-a-persistent-network-identity/5045/7)), and so, these are likely to not be subject to deploy-induced downtime. If you can, you should move to Machines (after evaluating it for [a round or two](https://community.fly.io/t/fly-instance-id-header-alternative-for-websockets/7536/5)).

---

_[View the full topic](https://community.fly.io/t/zero-downtime-deployment/7971)._