TencentDB for Redis is available in various regions. It can be deployed wherever CVM instances are deployed.
Note：
When you purchase TencentDB for Redis, we recommend you select the same region as your CVM instance to reduce access delay.
| Region | Availability Zone | ZoneId |
|---|---|---|
| South China (Guangzhou) ap-guangzhou |
Guangzhou Zone 1 ap-guangzhou-1 |
100001 |
| Guangzhou Zone 2 ap-guangzhou-2 |
100002 | |
| Guangzhou Zone 3 ap-guangzhou-3 |
100003 | |
| Guangzhou Zone 4 ap-guangzhou-4 |
100004 | |
| Guangzhou Zone 6 ap-guangzhou-6 |
100006 | |
| East China (Shanghai) ap-shanghai |
Shanghai Zone 1 ap-shanghai-1 |
200001 |
| Shanghai Zone 2 ap-shanghai-2 |
200002 | |
| Shanghai Zone 3 ap-shanghai-3 |
200003 | |
| Shanghai Zone 4 ap-shanghai-4 |
200004 | |
| Shanghai Zone 5 ap-shanghai-5 |
200005 | |
| Shanghai Zone 6 ap-shanghai-6 |
200006 | |
| Shanghai Zone 7 ap-shanghai-7 |
200007 | |
| East China (Nanjing) ap-nanjing |
Nanjing Zone 1 ap-nanjing-1 |
330001 |
| Nanjing Zone 2 ap-nanjing-2 |
330002 | |
| North China (Beijing) ap-beijing |
Beijing Zone 1 ap-beijing-1 |
800001 |
| Beijing Zone 2 ap-beijing-2 |
800002 | |
| Beijing Zone 3 ap-beijing-3 |
800003 | |
| Beijing Zone 4 ap-beijing-4 |
800004 | |
| Beijing Zone 5 ap-beijing-5 |
800005 | |
| North China (Tianjin) ap-tianjin |
Tianjin Zone 1 ap-tianjin-1 |
360001 |
| Tianjin Zone 2 ap-tianjin-2 |
360002 | |
| Southwest China (Chengdu) ap-chengdu |
Chengdu Zone 1 ap-chengdu-1 |
160001 |
| Chengdu Zone 2 ap-chengdu-2 |
160002 | |
| Southwest China (Chongqing) ap-chongqing |
Chongqing Zone 1 ap-chongqing-1 |
190001 |
| Hong Kong/Macao/Taiwan (Hong Kong, China) ap-hongkong |
Hong Kong (China) Zone 1 (Hong Kong (China) nodes can cover the China regions of Hong Kong, Macao, and Taiwan) ap-hongkong-1 |
300001 |
| Hong Kong (China) Zone 2 (Hong Kong (China) nodes can cover the China regions of Hong Kong, Macao, and Taiwan) ap-hongkong-2 |
300002 | |
| Hong Kong/Macao/Taiwan (Taipei, China) ap-taipei |
Taipei (China) Zone 1 ap-taipei-1 |
390001 |
| Region | Availability Zone | ZoneId |
|---|---|---|
| Southeast Asia Pacific (Singapore) ap-singapore |
Singapore Zone 1 (Singapore nodes can cover Southeast Asia Pacific) ap-singapore-1 |
900001 |
| Southeast Asia Pacific (Bangkok) ap-bangkok |
Bangkok Zone 1 (Bangkok nodes can cover Southeast Asia Pacific) ap-bangkok-1 |
230001 |
| South Asia Pacific (Mumbai) ap-mumbai |
Mumbai Zone 1 (Mumbai nodes can cover South Asia Pacific) ap-mumbai-1 |
210001 |
| Mumbai Zone 2 (Mumbai nodes can cover South Asia Pacific) ap-mumbai-2 |
210002 | |
| Northeast Asia Pacific (Seoul) ap-seoul |
Seoul Zone 1 (Seoul nodes can cover Northeast Asia Pacific) ap-seoul-1 |
180001 |
| Northeast Asia Pacific (Tokyo) ap-tokyo |
Tokyo Zone 1 (Tokyo nodes can cover Northeast Asia Pacific) ap-tokyo-1 |
250001 |
| West US (Silicon Valley) na-siliconvalley |
Silicon Valley Zone 1 (Silicon Valley nodes can cover West US) na-siliconvalley-1 |
150001 |
| Silicon Valley Zone 2 (Silicon Valley nodes can cover West US) na-siliconvalley-2 |
150002 | |
| East US (Virginia) na-ashburn |
Virginia Zone 1 (Virginia nodes can cover East US) na-ashburn-1 |
220001 |
| Virginia Zone 2 (Virginia nodes can cover East US) na-ashburn-2 |
220002 | |
| North America (Toronto) na-toronto |
Toronto Zone 1 (Toronto nodes can cover North America) na-toronto-1 |
400001 |
| Europe (Frankfurt) eu-frankfurt |
Frankfurt Zone 1 (Frankfurt nodes can cover Europe) eu-frankfurt-1 |
170001 | Europe (Moscow) eu-moscow |
Moscow Zone 1 (Moscow nodes can cover Europe) eu-moscow-1 |
240001 |
Was this page helpful?