> ## Documentation Index
> Fetch the complete documentation index at: https://docs.e6data.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Upgrade states

> The states a cluster or platform upgrade moves through, and the cluster upgrade deployment phases.

Upgrades report progress differently for clusters and for platform releases.

## Cluster version upgrade

When you change a cluster's version, the cluster enters **Updating** and continues serving queries on the current version. On success it returns to **Running** on the new version; on failure it automatically reverts and returns to **Running** on the previous version, with the failure recorded in Activity History. See [Zero-downtime upgrades](/query/clusters/zero-downtime-upgrades).

For In-VPC deployments, the cluster also exposes a deployment phase: `Stable → Deploying → Switching → Draining → Cleanup → Stable` (or `RollingBack`). See [CloudPrem cluster operations](/query/clusters/cloudprem-operations).

## Platform release states

A platform release (Platform Components) progresses through:

| Status | Meaning |
| - | - |
| **Not deployed** | No platform release deployed through this section yet (not an outage) |
| **Pending** | Selected, not yet started |
| **Deploying** | Rollout in progress |
| **Deployed** | Successfully live |
| **Failed** | One or more components failed |
| **Rolled Back** | The deploy failed and was automatically reverted to the previous version |

See [Rollbacks, failure modes, and recovery](/platform/upgrades/rollbacks-and-recovery) and [Status signals](/platform/upgrades/status-signals).

## See also

* [Cluster states](/query/cluster-reference/cluster-states)
* [Zero-downtime upgrades](/query/clusters/zero-downtime-upgrades)
* [Upgrades and releases](/platform/upgrades)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.