tencent cloud

Feedback

Regions and Availability Zones

Last updated: 2024-09-06 11:27:15

    Regions

    Overview

    A region is the physical location of an IDC. In Tencent Cloud, regions are fully isolated from each other, ensuring cross-region stability and fault tolerance. We recommend that you choose the region closest to your end users to minimize access latency and improve access speed.
    You can view the following table or use the DescribeRegions API to get a complete region list.

    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 communicate with each other through public IPs over the internet, while those in different VPCs can communicate with each other through Cloud Connect Network, which is faster and more stable.
    Cloud Load Balancer currently supports intra-region traffic forwarding and being bound to CVM instances in the same region by default. If you enable the cross-region binding feature, a CLB instance can be bound to CVM instances in another region.

    Availability Zones

    Overview

    An availability zone (AZ) is a physical IDC of Tencent Cloud with independent power supply and network in the same region. It can ensure business stability, as failures (except for major disasters or power failures) 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 availability zone list.

    Characteristics

    Tencent Cloud services in the same VPC are interconnected via the private network, which means they can communicate using private IPs, even if they are in different availability zones of the same region.
    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.

    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
    Guangzhou Zone 7
    ap-guangzhou-7
    East China (Shanghai)
    ap-shanghai
    Shanghai Zone 1 (Sold out)
    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
    Shanghai Zone 8
    ap-shanghai-8
    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 (Sold out)
    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 (Chengdu)
    ap-chengdu
    Chengdu Zone 1
    ap-chengdu-1
    Chengdu Zone 2
    ap-chengdu-2
    Southwest (Chongqing)
    ap-chongqing
    Chongqing Zone 1
    ap-chongqing-1
    Hong Kong/Macao/Taiwan (Hong Kong, China)
    ap-hongkong
    Hong Kong Zone 1 (Nodes in Hong Kong, China can cover services in Hong Kong/Macao/Taiwan regions) (Sold out)
    ap-hongkong-1
    Hong Kong Zone 2 (Nodes in Hong Kong, China can cover services in Hong Kong/Macao/Taiwan)
    ap-hongkong-2
    Hong Kong Zone 3 (Nodes in Hong Kong, China can cover services in Hong Kong/Macao/Taiwan)
    ap-hongkong-3
    Note:
    The product is in beta test for Jinan, Hangzhou, Fuzhou, Wuhan, Changsha, and Shijiazhuang regions. To try it out, contact the sales rep for application.

    Other Countries and Regions

    Region
    Availability Zone
    Southeast Asia Pacific (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
    Singapore Zone 3 (Singapore nodes cover services in Southeast Asia)
    ap-singapore-3
    Singapore Zone 4 (Singapore nodes cover services in Southeast Asia)
    ap-singapore-4
    Southeast Asia (Jakarta)
    ap-jakarta
    Jakarta Zone 1 (Jakarta nodes cover services in Southeast Asia)
    ap-jakarta-1
    Jakarta Zone 2 (Jakarta nodes cover services in Southeast Asia)
    ap-jakarta-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
    Tokyo Zone 2 (Tokyo node AZs cover services in Northeast Asia)
    ap-tokyo-2
    Southern Asia Pacific (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 Pacific (Bangkok)
    ap-bangkok
    Bangkok Zone 1 (Bangkok nodes cover services in Southeast Asia)
    ap-bangkok-1
    Bangkok Zone 2 (Bangkok nodes cover services in Southeast Asia)
    ap-bangkok-1
    South America (São Paulo)
    sa-saopaulo
    São Paulo Zone 1 (São Paulo nodes cover services in South America)
    sa-saopaulo-1
    West US (Silicon Valley)
    na-siliconvalley
    Silicon Valley Zone 1 (Silicon Valley nodes cover services in West US)
    na-siliconvalley-1
    Silicon Valley Zone 2 (Silicon Valley nodes cover services in West US)
    na-siliconvalley-2
    East US (Virginia)
    na-ashburn
    Virginia Zone 1 (Virginia nodes cover services in East US)
    na-ashburn-1
    Virginia Zone 2 (Virginia nodes cover services in East US)
    na-ashburn-2
    Europe (Frankfurt)
    eu-frankfurt
    Frankfurt Zone 1 (Frankfurt nodes cover services in Europe)
    eu-frankfurt-1
    Frankfurt Zone 2 (Frankfurt nodes cover services in Europe)
    eu-frankfurt-2

    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 end users when purchasing CVM instances to minimize access latency and improve access speed.
    Other Tencent Cloud services you use. When you select other Tencent Cloud services, we recommend 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 speed.
    High availability and disaster recovery. 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 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 servers in other countries or regions, we recommend that you select an instance in those other countries or regions. If you use a CVM instance in China to access servers in other countries or 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.
    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 around the world.
    skey-xxxxxxxx
    Global
    Users can use an SSH key to bind a CVM in any region under the account.
    ins-xxxxxxxx
    Available in a single availability zone of a region
    CVM instances can only be created in a specific availability zone.
    img-xxxxxxxx
    Available in multiple availability zones of a region
    Custom images created for the instance 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.
    eip-xxxxxxxx
    Available in multiple availability zones of a region
    EIPs can only be associated with instances in the same region.
    sg-xxxxxxxx
    Available in multiple availability zones of a region
    Security groups can only be associated with instances in the same region. Tencent Cloud automatically creates three default security groups for users.
    disk-xxxxxxxx
    Available in a single availability zone of a region
    Users can only create a Cloud Block Storage disk in a specific availability zone and attach it to instances in the same availability zone.
    snap-xxxxxxxx
    Available in multiple availability zones of a region
    A snapshot created from a cloud disk can be used for other purposes (such as creating cloud disks) in this region.
    clb-xxxxxxxx
    Available in multiple availability zones of a region
    Cloud Load Balancer can be bound with CVMs in different availability zones of a single region for traffic forwarding.
    vpc-xxxxxxxx
    Available in multiple availability zones of a region
    A VPC in one region can have resources created in different availability zones of the region.
    subnet-xxxxxxxx
    Available in a single availability zone of a region
    Users cannot create subnets across availability zones.
    rtb-xxxxxxxx
    Available in multiple availability zones of a region
    When creating a route table, users need to specify a VPC. Therefore, route tables are regional as well.

    Related Operations

    Migrating an instance to another availability zone

    Once launched, an instance cannot be migrated to another availability zone. However, you can create a custom image of the CVM instance and use the image to launch or update an instance in a different availability zone.
    1. Create a custom image for the current instance. For more information, see Creating a Custom Image.
    2. If the instance is on a VPC network environment 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 Creating Instances via CVM Purchase Page.
    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 instance is pay-as-you-go, you can choose to terminate it. For more information, see Terminating Instances.

    Copying images to other regions

    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, copy the image to the desired region. For more information, see Copying Images.
    Contact Us

    Contact our sales team or business advisors to help your business.

    Technical Support

    Open a ticket if you're looking for further assistance. Our Ticket is 7x24 avaliable.

    7x24 Phone Support