Regions and AZs
Last updated: 2025-09-19 17:35:33
A region is the physical location of an IDC. Availability zone (AZ) refers to the physical IDC of Tencent Cloud in the same region with independent power supplies and network resources. For more information, see CVM-Regions and AZs.
Supported regions
China
Region | Code | |
South China | Guangzhou | ap-guangzhou |
| Shenzhen | ap-shenzhen |
| | |
| Shenzhen Finance | ap-shenzhen-fsi (Available only for financial institutions and enterprises; apply through Online Consultation) |
East China | Shanghai | ap-shanghai |
| | |
| Shanghai Finance | ap-shanghai-fsi (Available only for financial institutions and enterprises; apply through Online Consultation) |
| Nanjing | ap-nanjing |
| Hangzhou | ap-hangzhou |
North China | Beijing | ap-beijing |
| | |
| Beijing Finance | ap-beijing-fsi (Available only for financial institutions and enterprises; apply through Online Consultation) |
| Tianjin | ap-tianjin |
Central China | Changsha | ap-changsha |
Southwest China | Chengdu | ap-chengdu |
| Chongqing | ap-chongqing |
Hong Kong/Macao/Taiwan (China) | Taipei (China) | ap-taipei |
| Hong Kong (China) | ap-hongkong |
Other countries and regions
Region | Code | |
Southeast Asia | Singapore | ap-singapore |
| Bangkok | ap-bangkok |
| Jakarta | ap-jakarta |
Northeast Asia | Seoul | ap-seoul |
| Tokyo | ap-tokyo |
US West | Silicon Valley | na-siliconvalley |
US East | Virginia | na-ashburn |
South America | São Paulo | sa-saopaulo |
Europe | Frankfurt | eu-frankfurt |
Selection of Regions and AZs
When selecting a region and AZ, take the following into consideration:
The geographic locations of TDMQ for CKafka instances, your business, and your target users: We recommend that you choose the region closest to your customers when purchasing a TDMQ for CKafka instance to reduce latency and improve access speed.
Relationship between CKafka and other Tencent Cloud services:
When you select other Tencent Cloud services, we recommend that you try to locate them all in the same region and AZ to allow them to communicate with each other through the private network, reducing access latency and increasing access speed.
High availability and disaster recovery.
Even if you have just one VPC, we still recommend that you deploy your businesses in different AZs to prevent a single point of failure and enable cross-AZ disaster recovery.
There may be network latency among different AZs. We recommend that you assess your business requirements and find the optimal balance between high availability and low latency.
If you need access to TDMQ for CKafka instances in other countries or regions, we recommend that you select an instance in those other countries or regions. If you use a TDMQ for CKafka instance in China to access servers in other countries or regions, you may encounter much higher network latency.
Resource availability
The following table describes global, regional, and AZ-specific TDMQ for CKafka resources.
Resource | Resource ID Format (8-Digit String of Numbers and Letters) | Type | Description |
User account | Unlimited | Globally unique | Users can use the same account to access Tencent Cloud resources from around the world. |
TDMQ for CKafka instance | ckafka-xxxxxxxx | TDMQ for CKafka instances can only be used in a single AZ of a single region. | TDMQ for CKafka instances can only be created in a specific AZ. |
Related Operations
Migrating instance to another AZ
CKafka supports instance migration across AZs in the same region. If you need this, submit a ticket for assistance.
Was this page helpful?
You can also Contact Sales or Submit a Ticket for help.
Yes
No
Feedback