# Single VM deploy causes temporary unavailability

**URL:** <https://community.fly.io/t/single-vm-deploy-causes-temporary-unavailability/3739>\
**Category:** Questions / Help\
**Created:** [January 21, 2022, 8:19pm UTC](https://community.fly.io/t/single-vm-deploy-causes-temporary-unavailability/3739 "2022-01-21T20:19:11Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![kurt](https://sea1.discourse-cdn.com/fly1/user_avatar/community.fly.io/kurt/32/43757_2.png) [@kurt](https://community.fly.io/u/kurt)\
**Post date:** [January 21, 2022, 8:53pm UTC](https://community.fly.io/t/single-vm-deploy-causes-temporary-unavailability/3739/2 "2022-01-21T20:53:06Z")

</div>

Yes that’s almost definitely the same issue. We are _so close_ to having this fixed, so the answer might be “just bear with us”. But the workaround answer is that running 3 nodes will likely mask the problem.

---

_[View the full topic](https://community.fly.io/t/single-vm-deploy-causes-temporary-unavailability/3739)._
