# Availability

> For the complete documentation index, see [llms.txt](https://docs.redpanda.com/llms.txt). Component-specific: [cloud-data-platform-full.txt](https://docs.redpanda.com/cloud-data-platform-full.txt)

---
title: Availability
latest-operator-version: v26.1.4
latest-console-tag: v3.7.3
latest-connect-version: 4.93.0
latest-redpanda-tag: v26.1.9
docname: cloud-availability
page-component-name: cloud-data-platform
page-version: master
page-component-version: master
page-component-title: Cloud
page-relative-src-path: cloud-availability.adoc
page-edit-url: https://github.com/redpanda-data/cloud-docs/edit/main/modules/security/pages/cloud-availability.adoc
description: Learn how Redpanda Cloud supports deploying clusters in single or multiple availability zones (AZs).
page-git-created-date: "2024-06-06"
page-git-modified-date: "2024-08-01"
---

<!-- Source: https://docs.redpanda.com/cloud-data-platform/security/cloud-availability.md -->

Redpanda Cloud supports the deployment of Redpanda clusters in single or multiple availability zones (AZs), spanning at most three AZs. Brokers are evenly distributed across AZs, and the number of topic replicas is set to `3` by default. Data is evenly distributed across AZs automatically. This behavior is known as [rack awareness](https://docs.redpanda.com/cloud-data-platform/reference/glossary/#rack-awareness).

To prevent downtime during cluster upgrades, the Redpanda Cloud cluster operator upgrades one broker at a time. It waits for the health of the cluster to return to its nominal state before continuing with the next broker upgrade, until all brokers are fully rolled out.

Redpanda’s Support, Security, and Site Reliability Engineering (SRE) teams monitor Redpanda Cloud clusters 24/7 to ensure they meet availability service level agreements (SLAs). If incidents occur, teams at Redpanda trigger an incident response process to quickly mitigate them.