Contents：
TencentDB for Redis is available in various regions in and outside Mainland China. It can be deployed wherever CVM are deployed.
Network Descriptions
- Tencent Cloud services in the same region can communicate with one another over private networks.
- A CVM instance in a VPC can communicate with a TencentDB for Redis instance on a basic network in a different availability zone in the same region, only after a subnet is configured and a VPC IP is assigned.
- Tencent Cloud services in different regions cannot communicate with one another over the private network. They can communicate over a VPC only after a peering connection is configured.
It is recommended to select the same region for the TencentDB for Redis instance as for the CVM instance so as to reduce access latency.
Regions and AZs
Mainland China
| Region | AZ |
|---|---|
| South China (Guangzhou) ap-guangzhou |
Guangzhou Zone 1 (sold-out) ap-guangzhou-1 |
| Guangzhou Zone 2 ap-guangzhou-2 |
|
| Guangzhou Zone 3 ap-guangzhou-3 |
|
| Guangzhou Zone 4 ap-guangzhou-4 |
|
| 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 (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 |
Outside Mainland China
| Region | AZ |
|---|---|
| Southeast Asia (Hong Kong, China) ap-hongkong |
Hong Kong Zone 1 (Nodes in Hong Kong, China can cover services in Southeast Asia) ap-hongkong-1 |
| Hong Kong Zone 2 (Nodes in Hong Kong, China can cover services in Southeast Asia) ap-hongkong-2 |
|
| Southeast Asia (Singapore) ap-singapore |
Singapore Zone 1 (Nodes in Singapore can cover services in Southeast Asia) ap-singapore-1 |
| Asia Pacific (Seoul) ap-seoul |
Seoul Zone 1 (Nodes in Seoul can cover services in Northeast Asia) ap-seoul-1 |
| Asia Pacific (Tokyo) ap-tokyo |
Tokyo Zone 1 (Nodes in Tokyo cover services in Northeast Asia) ap-tokyo-1 |
| Asia Pacific (Mumbai) ap-mumbai |
Mumbai Zone 1 (Nodes in Mumbai can cover services in South Pacific Asia) ap-mumbai-1 |
| Asia Pacific (Bangkok) ap-bangkok |
Bangkok Zone 1 (Nodes in Bangkok cover services in Southeast Asia Pacific) ap-bangkok-1 |
| North America (Toronto) na-toronto |
Toronto Zone 1 (Nodes in Toronto can cover services in North America) na-toronto-1 |
| West US (Silicon Valley) na-siliconvalley |
Silicon Valley Zone 1 (Nodes in Silicon Valley can cover services in West US) na-siliconvalley-1 |
| Silicon Valley Zone 2 (Nodes in Silicon Valley can cover services in West US) na-siliconvalley-2 |
|
| East US (Virginia) na-ashburn |
Virginia Zone 1 (Nodes in Virginia can cover services in East US) na-ashburn-1 |
Europe (Frankfurt) eu-frankfurt |
Frankfurt Zone 1 (Nodes in Frankfurt can cover services in Europe) eu-frankfurt-1 |
Europe (Moscow) eu-moscow |
Moscow Zone 1 (Nodes in Moscow can cover services in Europe) eu-moscow-1 |
