# BYOC Tiers and Regions

> 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: BYOC Tiers and Regions
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: tiers/byoc-tiers
page-component-name: cloud-data-platform
page-version: master
page-component-version: master
page-component-title: Cloud
page-relative-src-path: tiers/byoc-tiers.adoc
page-edit-url: https://github.com/redpanda-data/cloud-docs/edit/main/modules/reference/pages/tiers/byoc-tiers.adoc
description: Learn about supported tiers and regions for BYOC clusters.
page-git-created-date: "2024-06-06"
page-git-modified-date: "2024-08-01"
---

<!-- Source: https://docs.redpanda.com/cloud-data-platform/reference/tiers/byoc-tiers.md -->

## [](#byoc-usage-tiers)BYOC usage tiers

When you create a BYOC cluster, you select your usage tier. Each tier provides tested workload configurations for maximum throughput, partitions, and connections.

| Tier | Ingress | Egress | Partitions (pre-replication) | Connections |
| --- | --- | --- | --- | --- |
| Tier 1 | 20 MBps | 60 MBps | 2,000 | 9,000 |
| Tier 2 | 50 MBps | 150 MBps | 5,600 | 22,500 |
| Tier 3 | 100 MBps | 200 MBps | 11,200 | 45,000 |
| Tier 4 | 200 MBps | 400 MBps | 22,600 | 90,000 |
| Tier 5 | 400 MBps | 800 MBps | 45,600 | 180,000 |
| Tier 6 | 800 MBps | 1,600 MBps | 90,000 | 180,000 |
| Tier 7 | 1,200 MBps | 2,400 MBps | 112,500 | 270,000 |
| Tier 8 | 1,600 MBps | 3,200 MBps | 112,500 | 360,000 |
| Tier 9 | 2,000 MBps | 4,000 MBps | 112,500 | 450,000 |

> 📝 **NOTE**
>
> -   Partition counts are based on clusters running Redpanda version 25.1 or higher and on the assumption that the replication factor is 3 (default). If you set a higher replication factor, the maximum value for partitions will be lower.
>
> -   On Azure, tiers 1-5 are supported.
>
> -   Redpanda supports compute-optimized tiers with AWS Graviton3 processors.
>
> -   Depending on the workload, it may not be possible to achieve all maximum values. For example, a high number of partitions may make it more difficult to reach the maximum value in throughput.
>
> -   Connections are regulated per broker for best performance. For example, in a tier 1 cluster with 3 brokers, there could be up to 3,000 connections per broker.

## [](#byoc-supported-regions)BYOC supported regions

### Google Cloud Platform (GCP)

| Region |
| --- |
| asia-east1 |
| asia-northeast1 |
| asia-south1 |
| asia-southeast1 |
| australia-southeast1 |
| europe-southwest1 |
| europe-west1 |
| europe-west2 |
| europe-west3 |
| europe-west4 |
| europe-west9 |
| northamerica-northeast1 |
| southamerica-east1 |
| southamerica-west1 |
| us-central1 |
| us-east1 |
| us-east4 |
| us-west1 |
| us-west2 |

### Amazon Web Services (AWS)

| Region |
| --- |
| af-south-1 |
| ap-east-1 |
| ap-northeast-1 |
| ap-south-1 |
| ap-southeast-1 |
| ap-southeast-2 |
| ap-southeast-3 |
| ca-central-1 |
| eu-central-1 |
| eu-north-1 |
| eu-south-1 |
| eu-west-1 |
| eu-west-2 |
| eu-west-3 |
| me-central-1 |
| sa-east-1 |
| us-east-1 |
| us-east-2 |
| us-west-2 |

### Azure

| Region |
| --- |
| centralus |
| eastus |
| eastus2 |
| germanywestcentral |
| northeurope |
| norwayeast |
| swedencentral |
| uksouth |
| westeurope |
| westus2 |