Regions and availability zones

Last updated: 2020-12-14 10:59:25

    Regions

    A region is the physical location of an IDC. In Tencent Cloud, different regions are fully isolated, ensuring cross-region stability and fault tolerance. When purchasing Tencent Cloud services, we recommend selecting the region closest to your end users to minimize access latency and improve download speed.
    Regions have the following characteristics:

    • The networks of different regions are fully isolated. Tencent Cloud services in different regions cannot communicate via a private network by default.
    • Tencent Cloud services in different regions can access the Internet through public IPs, while those in a VPC can use peering connection to communicate with each other via Tencent Cloud’s high-speed network, which is faster and steadier.
    • Cloud Load Balancer currently supports intra-region traffic forwarding by default. If cross-region binding is enabled, a CLB instance can be bound to CVM instances in another region.

    Availability Zones

    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.
    Availability zones have the following characteristics:

    • Tencent Cloud services under the same account 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.
    • Resources under different Tencent Cloud accounts are availability zone-specific, meaning they cannot communicate via a private network, even if they are in the same region.

    China

    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
    North 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
    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 China regions of Hong Kong, Macao, and Taiwan)
    ap-hongkong-1
    Hong Kong Zone 2 (Hong Kong nodes cover services in the China regions of Hong Kong, Macao, and Taiwan)
    ap-hongkong-2

    Other Countries and Regions

    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

    How to Select Regions and Availability Zones

    When selecting a region and availability zone, you need to consider the following factors:

    • The limits on where cloud disks can be mounted. A cloud disk can only be mounted to a CVM in the same availability zone.
    • The region of the CVM on which the cloud disk will be used, your location, and the location of your users. We recommend that you choose the region closest to your users when purchasing the Tencent Cloud services to minimize access latency and improve access speed.
    • The relationship between the CVM on which the cloud disk will be used and other Tencent Cloud services. 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.
    • Business high availability and disaster recovery considerations. 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.

    Relevant Operations

    Actions such as the use and viewing of cloud disks are availability zone and region-specific. To easily migrate data and services to other regions or construct a cross-region disaster recovery system, you can copy snapshots to other regions. For more information, see Cross-region Snapshot Replicating.

    Was this page helpful?

    Was this page helpful?

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