A region is the physical location of an IDC. In Tencent Cloud, different regions are fully isolated, ensuring cross-region maximum stability and fault tolerance. To reduce access latency and increase download speeds, we recommend you select the region nearest to your end users.
You can view the following table or use the DescribeRegions API to get a complete list of regions.
An availability zone is a physical IDC of Tencent Cloud with independent power supply and network resource in a single region. It can ensure business stability, as failures (except for large-scale disaster or major power failure) in one AZ are isolated without affecting other AZs in the same region. By starting an instance in an independent availability zone, users can protect their applications from being affected by a single point of failure.
You can view the following table or use the DescribeZones API to get a complete list of availability zones.
Tencent Cloud services in the same VPC are interconnected through the private network, meaning they can communicate using private IPs, even if they are in different availability zones.
Note:
Private network interconnection refers to the interconnection of resources under the same account. Resources under different accounts are completely isolated on the private network.
Region | Availability Zone |
---|---|
South China (Guangzhou) ap-guangzhou |
Guangzhou Zone 1 (sold out) ap-guangzhou-1 |
Guangzhou Zone 2 (sold out) ap-guangzhou-2 |
|
Guangzhou Zone 3 ap-guangzhou-3 |
|
Guangzhou Zone 4 ap-guangzhou-4 |
|
Guangzhou Zone 6 ap-guangzhou-6 |
|
East China (Shanghai) ap-shanghai |
Shanghai Zone 1 ap-shanghai-1 |
Shanghai Zone 2 ap-shanghai-2 |
|
Shanghai Zone 3 ap-shanghai-3 |
|
Shanghai Zone 4 ap-shanghai-4 |
|
Shanghai Zone 5 ap-shanghai-5 |
|
East China (Nanjing) ap-nanjing |
Nanjing Zone 1 ap-nanjing-1 |
Nanjing Zone 2 ap-nanjing-2 |
|
Nanjing Zone 3 ap-nanjing-3 |
|
North China (Beijing) ap-beijing |
Beijing Zone 1 ap-beijing-1 |
Beijing Zone 2 ap-beijing-2 |
|
Beijing Zone 3 ap-beijing-3 |
|
Beijing Zone 4 ap-beijing-4 |
|
Beijing Zone 5 ap-beijing-5 |
|
Beijing Zone 6 ap-beijing-6 |
|
Beijing Zone 7 ap-beijing-7 |
|
Southwest China (Chengdu) ap-chengdu |
Chengdu Zone 1 ap-chengdu-1 |
Chengdu Zone 2 ap-chengdu-2 |
|
Southwest China (Chongqing) ap-chongqing |
Chongqing Zone 1 ap-chongqing-1 |
Hong Kong/Macao/Taiwan (Hong Kong, China) ap-hongkong |
Hong Kong Zone 1 (Hong Kong nodes cover services in the Hong Kong, Macao, and Taiwan regions of China) ap-hongkong-1 |
Hong Kong Zone 2 (Hong Kong nodes cover services in the Hong Kong, Macao, and Taiwan regions of China) ap-hongkong-2 |
Region | Availability Zone |
---|---|
Southeast Asia (Singapore) ap-singapore |
Singapore Zone 1 (Singapore nodes cover services in Southeast Asia) ap-singapore-1 |
Singapore Zone 2 (Singapore nodes cover services in Southeast Asia) ap-singapore-2 |
|
Northeast Asia (Seoul) ap-seoul |
Seoul Zone 1 (Seoul nodes cover services in Northeast Asia) ap-seoul-1 |
Seoul Zone 2 (Seoul nodes cover services in Northeast Asia) ap-seoul-2 |
|
Northeast Asia (Tokyo) ap-tokyo |
Tokyo Zone 1 (Tokyo nodes cover services in Northeast Asia) ap-tokyo-1 |
South Asia (Mumbai) ap-mumbai |
Mumbai Zone 1 (Mumbai nodes cover services in South Asia) ap-mumbai-1 |
Mumbai Zone 2 (Mumbai nodes cover services in South Asia) ap-mumbai-2 |
|
Southeast Asia (Bangkok) ap-bangkok |
Bangkok Zone 1 (Bangkok nodes cover services in Southeast Asia) ap-bangkok-1 |
North America (Toronto) na-toronto |
Toronto Zone 1 (Tokyo nodes cover services in North America) na-toronto-1 |
Western US (Silicon Valley) na-siliconvalley |
Silicon Valley Zone 1 (Silicon Valley nodes cover services in Western US) na-siliconvalley-1 |
Silicon Valley Zone 2 (Silicon Valley nodes cover services in Western US) na-siliconvalley-2 |
|
Eastern US (Virginia) na-ashburn |
Virginia Zone 1 (Virginia nodes cover services in Eastern US) na-ashburn-1 |
Virginia Zone 2 (Virginia nodes cover services in Eastern US) na-ashburn-2 |
|
Europe (Frankfurt) eu-frankfurt |
Frankfurt Zone 1 (Frankfurt nodes cover services in Europe) eu-frankfurt-1 |
Europe (Moscow) eu-moscow |
Moscow Zone 1 (Moscow nodes cover services Europe) eu-moscow-1 |
When selecting a region and availability zone, take the following into consideration:
The following table describes which Tencent Cloud resources are global, which are regional, and which are specific to availability zones.
Resource | Resource ID Format | Type | Description |
---|---|---|---|
User Account | No limit | Globally unique | Users can use the same account to access Tencent Cloud resources from around the world. |
SSH Keys | skey-xxxxxxxx | Global | Users can use an SSH key to bind a CVM in any region under the account. |
CVM Instances | ins-xxxxxxxx | Specific to an availability zone | A CVM instance created in an availability zone is not available to other availability zones. |
Custom Images | img-xxxxxxxx | Regional | Custom images created for the instance are available to all availability zones of the same region. Use the cross-region replication feature to copy a custom image if you need to use it in other regions. |
Elastic IPs | eip-xxxxxxxx | Regional | EIPs can only be associated with instances in the same region. |
Security Groups | sg-xxxxxxxx | Regional | Security Group can only be associated with instances in the same region. Tencent Cloud automatically creates three default security groups for users. |
Cloud Block Storage | disk-xxxxxxxx | Specific to an availability zone | Users can only create a cloud disk in a specific availability zone and mount it to instances in the same availability zone. |
Snapshots | snap-xxxxxxxx | Regional | A snapshot created from a cloud disk can be used for other purposes (such as creating cloud disks) in this region. |
Cloud Load Balancer | clb-xxxxxxxx | Regional | Cloud Load Balancer can be bound with CVMs in different availability zones of a single region for traffic forwarding. |
VPC | vpc-xxxxxxxx | Regional | A VPC in one region can have resources created in different availability zones. |
Subnets | subnet-xxxxxxxx | Specific to an availability zone | Users cannot create subnets across availability zones. |
Route Tables | rtb-xxxxxxxx | Regional | When creating a route table, users need to specify a VPC. Therefore, route tables are regional as well. |
Once launched, an instance cannot be migrated. However, you can create a custom image of your CVM instance and use the image to launch or update an instance in a different availability zone.
Operations such as launching and viewing instances are region-specific. If the image of the instance that you need to launch does not exist in the region, the image needs to be copied to the desired region. For more information, see Copying Images.
Was this page helpful?