# Update a Deployment

Learn how to update a deployment to a newer version of FusionAuth.

> For the index of this section of the site, see [llms.txt](https://fusionauth.io/docs/llms.txt)

If your deployment is not running the latest version of FusionAuth, you may update to a newer version. We recommend running the latest released version of FusionAuth for access to the latest fixes, security updates, and features.

However, you will not be forced to update on a certain schedule. Updates are optional and controlled by you.

The update process described in this section updates the version of FusionAuth; for help modifying other attributes of your deployment, such as the region, the deployment size, or the service tier, see [Alter a Deployment](https://fusionauth.io/docs/cloud/operate/alter-a-deployment.md).

## Update Process

Caution

You cannot downgrade a FusionAuth Cloud deployment version. After an update, you can only [roll back to a backup of an earlier version](#roll-back-to-a-backup). This *permanently loses any new or changed user or configuration data since the backup*.

Please test updates before performing them on your production system.

To update a deployment from version `1.x-1` to version `1.x`:

1.  Test `1.x` on a staging or development environment.
2.  Select a time that works for your users, your team, and your applications.
3.  Log into your account at [account.fusionauth.io](https://account.fusionauth.io/).
4.  Record the time you began the update.
5.  Navigate to the Hosting tab. Manage the deployment, then choose the Upgrade option. Select `1.x` from the **Version** dropdown.
6.  Confirm you want to start the update.
7.  After confirmation, the deployment will enter an **Upgrading** state until finished. To monitor the update, navigate to the Hosting tab. To programmatically monitor the update, call the [System Status API](https://fusionauth.io/docs/apis/system/retrieve-system-status.md).
8.  Your update is complete when the user interface deployment has a status of **Active**, or when the System Status API returns success.

## Update Duration

This update process takes between 5 and 60 minutes. The exact duration of system downtime depends on the type of deployment, amount of data in your system, and database changes required by the version update.

| Hosting Option | Duration of Update | Expected Downtime |
| --- | --- | --- |
| Basic Cloud | 5 to 60 minutes | 5 to 60 minutes |
| Business Cloud | 5 to 60 minutes | 5 to 60 minutes |
| HA Cloud | 5 to 60 minutes | seconds |

HA systems have significantly lower downtime during an update because the system has two or more nodes. We update these one at a time, so they continue to receive traffic throughout the update.

## Update Considerations

Consult the [relevant release notes](https://fusionauth.io/docs/release-notes.md) for functional changes. Such changes may require updates or modifications to your code, whether to take advantage of new features or, occasionally, to handle changes in FusionAuth functionality.

Due to the downtime, it is recommended that you schedule the update for a low traffic period. Test the update process on development or test servers first.

## Roll Back to a Backup

Business and High Availability deployments retain backups for 30 days after an update. Basic deployments do not retain backups.

If an update is problematic, and you identify the issue during the timeframe of your plan's backup retention period, open a [support ticket](https://account.fusionauth.io/account/support/), including the following information:

*   The version from which you were updating. This will be the version of your restored instance.
*   The approximate time the update began, including timezone, so that the correct backup can be restored.

Both production and non-production environments can be rolled back if on a plan with backups.

Production rollbacks will be treated the same as a production outage.

Non-production rollbacks will be completed within two business days, and will be handled during normal FusionAuth business hours (9am-5pm Mountain time, Monday-Friday). Non-production rollbacks will not be treated as a production outage.

All rollbacks will have data loss; the amount of data loss depends on when the update began and when the rollback was requested.

Related

[Update Update a Development Instance of FusionAuth Learn how to update an instance of FusionAuth that isn't used for production purposes. version upgradeupdate fusionauthversion update](https://fusionauth.io/docs/update/dev-instance.md)

[Update Update to a Newer Version of FusionAuth Learn how to update FusionAuth instances, FusionAuth Cloud deployments, and client libraries to a newer version. version upgradeupdate fusionauthversion update](https://fusionauth.io/docs/update.md)

[Update Update a Production Instance of FusionAuth Learn how to plan, perform, and verify an update of a FusionAuth instance in a production environment. version upgradeupdate fusionauthversion update](https://fusionauth.io/docs/update/prod-instance.md)

[Update Roll Back a FusionAuth Update Learn how to roll back FusionAuth to a previous version. version upgradeupdate fusionauthversion update](https://fusionauth.io/docs/update/rollback.md)
---

## Other pages in Cloud

> For the full index of this section, see [Cloud](https://fusionauth.io/docs/llms-cloud.txt).

- [Account](https://fusionauth.io/docs/cloud/account.md): Learn about the account portal, where you can manage account data, deployments, and licenses.
- [Cloud-Hosted FusionAuth vs Self-Hosted FusionAuth](https://fusionauth.io/docs/cloud/cloud-vs-self-hosted.md): Learn about the pros and cons of FusionAuth Cloud compared to self-hosted FusionAuth.
- [Create a Deployment](https://fusionauth.io/docs/cloud/create-a-deployment.md): Learn how to create a FusionAuth Cloud deployment.
- [Delete a Deployment](https://fusionauth.io/docs/cloud/delete-a-deployment.md): Learn how to delete a FusionAuth Cloud deployment.
- [Support](https://fusionauth.io/docs/cloud/support.md): Support information for FusionAuth Cloud.