Regions and Availability Zones

Last updated: 2020-12-15 10:17:16



    A region is the physical location of an IDC. In Tencent Cloud, different regions are fully isolated, ensuring maximum stability and fault tolerance among regions. To reduce access latency and increase download speeds, we recommend you select the region nearest to your customers.

    You can view the following table or use the DescribeRegions API to view a complete list of regions.


    • The networks of different regions are fully isolated. Tencent Cloud products in different regions cannot communicate via private network by default.
    • Tencent Cloud services across regions can communicate with each other through public IPs over the Internet, while those in different VPCs can communicate with each other through CCN that is more faster and steadier.
    • Cloud Load Balancer currently supports intra-region traffic forwarding by default. If Cross-region binding is enabled, cross-region binding of load balancers and CVMs is supported.

    Availability Zones


    Availability zones refer to Tencent Cloud physical IDCs in the same region with independent power supplies and network resources. They are designed to ensure that a failure within one availability zone can be contained (except for large-scale disasters or major power failures) without spreading to and affecting other zones. This ensures the stability of the businesses we host. By starting an instance in an independent availability zone, users can protect their applications from being affected by failures that occur in a single location.
    You can use DescribeAvailabilityZones to get a complete list of availability zones.


    Tencent Cloud products 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.


    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 AZ
    South China (Guangzhou)
    Guangzhou Zone 1 (sold out)
    Guangzhou Zone 2 (sold out)
    Guangzhou Zone 3
    Guangzhou Zone 4
    Guangzhou Zone 6
    East China (Shanghai)
    Shanghai Zone 1
    Shanghai Zone 2
    Shanghai Zone 3
    Shanghai Zone 4
    Shanghai Zone 5
    East China (Nanjing)
    Nanjing Zone 1
    Nanjing Zone 2
    North China (Beijing)
    Beijing Zone 1
    Beijing Zone 2
    Beijing Zone 3
    Beijing Zone 4
    Beijing Zone 5
    Southwest China (Chengdu)
    Chengdu Zone 1
    Chengdu Zone 2
    Southwest China (Chongqing)
    Chongqing Zone 1
    Hong Kong/Macao/Taiwan (Hong Kong, China)
    Hong Kong Zone 1 (Nodes in Hong Kong, China can cover Hong Kong/Macao/Taiwan)
    Hong Kong Zone 2 (Nodes in Hong Kong, China can cover Hong Kong/Macao/Taiwan)

    Other Countries and Regions

    Region AZ
    Southeast Asia Pacific (Singapore)
    Singapore Zone 1 (Singapore nodes can cover Southeast Asia Pacific)
    Singapore Zone 2 (Singapore nodes can cover Southeast Asia Pacific)
    Northeast Asia Pacific (Seoul)
    Seoul Zone 1 (Seoul nodes can cover Northeast Asia Pacific)
    Seoul Zone 2 (Seoul nodes can cover Northeast Asia Pacific)
    Northeast Asia Pacific (Tokyo)
    Tokyo Zone 1 (Tokyo nodes can cover Northeast Asia Pacific)
    South Asia Pacific (Mumbai)
    Mumbai Zone 1 (Mumbai nodes can cover South Asia Pacific)
    Mumbai Zone 2 (Nodes in Mumbai can cover South Asia Pacific)
    Southeast Asia Pacific (Bangkok)
    Bangkok Zone 1 (Bangkok nodes can cover Southeast Asia Pacific)
    North America (Toronto)
    Toronto Zone 1 (Toronto nodes can cover North America)
    Western US (Silicon Valley)
    Silicon Valley Zone 1 (Silicon Valley nodes can cover Western US)
    Silicon Valley Zone 2 (Silicon Valley nodes can cover Western US)
    East US (Virginia)
    Virginia Zone 1 (Virginia nodes can cover Eastern US)
    Virginia Zone 2 (Virginia nodes can cover Eastern US)
    Europe (Frankfurt)
    Frankfurt Zone 1 (Frankfurt nodes can cover Europe)
    Europe (Moscow)
    Moscow Zone 1 (Moscow nodes can cover Europe)

    How to Select Regions and Availability Zones

    When selecting a region and availability zone, take the following into consideration:

    • Your location, the location of your users, and the region of the CVM instances.
      We recommend that you choose the region closest to your users when making the decision to minimize access latency and improve access speed.
    • Other Tencent Cloud products you use.
      We recommend that, when you select other Tencent Cloud products, you try to locate them all in the same region and availability zone to allow them to communicate with each other through the private network, reducing access latency and increasing access speeds.
    • High availability and fault tolerance.
      Even if you have just one VPC, we still recommend that you deploy your businesses in different availability zones to prevent a single point of failure and enable cross-AZ disaster recovery.
    • There may be higher network latency among different availability zones. We recommend that you assess your business requirements and find the optimal balance between high availability and low latency.
    • If you need access to CVM instances in other countries or regions, we recommend you select a CVM in those other countries or regions. If you use a CVM instance in Mainland China to access servers in other countries and regions, you may encounter much higher network latency.

    Resource Availability

    The following table describes which Tencent Cloud resources are global, which are regional, and which are specific to availability zones.

    ResourceResource ID format
    8-digit string of numbers and letters
    User Accounts 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 CVM instances are 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 are available to all availability zones of the same region. Use **Copy Image** to copy a custom image if you need to use it in other regions.
    EIPs 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 CSB disks are specific to an availability zone. Users can only create a Cloud Block Storage disk in a specific availability zone and can mount it to instances in the same availability zone.
    Snapshots snap-xxxxxxxx Regional After creating a snapshot for a specific cloud disk, users can use this snapshot in this region for other operations (such as creating cloud disks).
    Cloud Load Balancers clb-xxxxxxxx Regional Cloud Load Balancer can be bound with CVMs in different availability zones in the same region for traffic forwarding.
    VPC vpc-xxxxxxxx Regional A VPC is created under a certain region. You can create resources in different AZs but in the same VPC.
    Subnets subnet-xxxxxxxx Subnets are specific to availability zones. Users cannot create subnets across availability zones.
    Routing Tables rtb-xxxxxxxx Regional When creating a routing table, users need to specify a VPC. Therefore, routing tables are regional as well.

    Migrating an Instance to another availability zone

    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.

    1. Create a custom image from the current instance. For more information, see Creating a Custom Image.
    2. If the instance is on a VPC and you want to retain its current private IP address after the migration, first delete the subnet in the current availability zone and then create a subnet in the new availability zone with the same IP address range. Note that a subnet can be deleted only when it contains no available instances. Therefore, all the instances in the current subnet should be migrated to the new subnet.
    3. Create a new instance in the new availability zone by using the custom image you have just created. You can choose the same type and configuration as the original instance, or choose new settings. For more information, see Purchasing and Launching Instances.
    4. If an Elastic IP is associated with the original instance, dissociate it from the old instance and associate it with the new instance. For more information, see EIPs.
    5. (Optional) If the original CVM instance is pay as you go, you can choose to terminate it. For more information, refer to Terminate Instances.

    Copying Images to Other Regions

    Actions such as launching and viewing instances have region attributes. 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?

    Was this page helpful?

    • Not at all
    • Not very helpful
    • Somewhat helpful
    • Very helpful
    • Extremely helpful
    Send Feedback