Tencent Cloud Ping Test
Find your closest, lowest-latency Tencent Cloud region. Tencent Cloud latency test from your browser using regional COS endpoints. No account or install required.
17 Tencent Cloud regions measured · browser-based · no signup
17regions
- Tencent CloudThailand (Bangkok)ap-bangkokBangkok, TH—
- Tencent CloudChina (Beijing)ap-beijingBeijing, CN—
- Tencent CloudChina (Chengdu)ap-chengduChengdu, CN—
- Tencent CloudChina (Chongqing)ap-chongqingChongqing, CN—
- Tencent CloudChina (Guangzhou)ap-guangzhouGuangzhou, CN—
- Tencent CloudHong Kongap-hongkongHong Kong, HK—
- Tencent CloudIndonesia (Jakarta)ap-jakartaJakarta, ID—
- Tencent CloudChina (Nanjing)ap-nanjingNanjing, CN—
- Tencent CloudSouth Korea (Seoul)ap-seoulSeoul, KR—
- Tencent CloudChina (Shanghai)ap-shanghaiShanghai, CN—
- Tencent CloudSingaporeap-singaporeSingapore, SG—
- Tencent CloudJapan (Tokyo)ap-tokyoTokyo, JP—
- Tencent CloudGermany (Frankfurt)eu-frankfurtFrankfurt, DE—
- Tencent CloudSaudi Arabia (Riyadh)me-saudi-arabiaRiyadh, SA—
- Tencent CloudUS East (Virginia)na-ashburnAshburn, US—
- Tencent CloudUS West (Silicon Valley)na-siliconvalleySan Jose, US—
- Tencent CloudBrazil (São Paulo)sa-saopauloSão Paulo, BR—
| # | Provider | Region | Location | Latency |
|---|---|---|---|---|
| Tencent Cloud | Thailand (Bangkok) ap-bangkok | Bangkok, TH | — | |
| Tencent Cloud | China (Beijing) ap-beijing | Beijing, CN | — | |
| Tencent Cloud | China (Chengdu) ap-chengdu | Chengdu, CN | — | |
| Tencent Cloud | China (Chongqing) ap-chongqing | Chongqing, CN | — | |
| Tencent Cloud | China (Guangzhou) ap-guangzhou | Guangzhou, CN | — | |
| Tencent Cloud | Hong Kong ap-hongkong | Hong Kong, HK | — | |
| Tencent Cloud | Indonesia (Jakarta) ap-jakarta | Jakarta, ID | — | |
| Tencent Cloud | China (Nanjing) ap-nanjing | Nanjing, CN | — | |
| Tencent Cloud | South Korea (Seoul) ap-seoul | Seoul, KR | — | |
| Tencent Cloud | China (Shanghai) ap-shanghai | Shanghai, CN | — | |
| Tencent Cloud | Singapore ap-singapore | Singapore, SG | — | |
| Tencent Cloud | Japan (Tokyo) ap-tokyo | Tokyo, JP | — | |
| Tencent Cloud | Germany (Frankfurt) eu-frankfurt | Frankfurt, DE | — | |
| Tencent Cloud | Saudi Arabia (Riyadh) me-saudi-arabia | Riyadh, SA | — | |
| Tencent Cloud | US East (Virginia) na-ashburn | Ashburn, US | — | |
| Tencent Cloud | US West (Silicon Valley) na-siliconvalley | San Jose, US | — | |
| Tencent Cloud | Brazil (São Paulo) sa-saopaulo | São Paulo, BR | — |
Frequently asked questions
Everything below is the precise methodology behind the numbers on this page.
What does this Tencent Cloud ping test measure?
regionping measures HTTPS round-trip latency from your browser to public Tencent Cloud COS regional endpoints. It requires no Tencent Cloud account and helps you compare network paths to the regions listed on this page.
How does regionping test Tencent Cloud regions?
Your browser sends one warmup HEAD request to https://cos.{region}.myqcloud.com, then collects five timed samples. The highest and lowest are dropped and the median of the remaining three is shown. Up to 16 regions run in parallel. Global acceleration and finance-region endpoints are excluded.
How does regionping measure latency?
Your browser sends one warmup HEAD request per region to prime DNS, TCP, and TLS, then issues five timed HEAD requests. The highest and lowest samples are dropped and the median of the remaining three is shown. Up to 16 regions are measured in parallel.
Why are the numbers higher than what ICMP ping shows?
regionping runs inside a browser, which cannot send ICMP packets. Every sample is an HTTPS HEAD request, so the measured time includes TCP and TLS overhead. Expect regionping numbers to sit roughly 10–30 ms above ICMP ping from the same machine. The ordering between regions is still faithful, which is what matters when choosing one.
Which cloud providers and regions are supported?
AWS (33 regions), Google Cloud (43 regions), Azure (40 regions), Oracle Cloud (43 regions), DigitalOcean (13 regions), IBM Cloud (13 regions), Alibaba Cloud (30 regions), Akamai Cloud (23 regions), OVHcloud (13 regions), Vultr (14 regions), Hetzner (3 regions), Huawei Cloud (26 regions), Exoscale (8 regions), Scaleway (4 regions), Gcore (3 regions), Contabo (3 regions), Tencent Cloud (17 regions), IONOS Cloud (4 regions), and Backblaze B2 (4 regions). 337 public regions in total.
What do the green, yellow, and red latency values mean?
Green (under 80 ms) is what you want for interactive workloads — API calls, real-time messaging, game servers. Yellow (80–149 ms) is acceptable for most web apps but noticeable in chatty request patterns. Red (150 ms and above) signals a region that is likely far from your network path; usable for batch and background jobs but a poor choice for anything user-interactive.
Why did a region return “failed”?
Most common causes, in roughly decreasing order of likelihood: a corporate firewall or enterprise proxy blocking the provider domain, an active VPN routing the request through a path that drops it, ISP-level blocks on cloud object-storage hostnames, the provider not yet deploying (or having deprecated) the public endpoint in that region, or a browser extension such as an ad blocker or privacy tool intercepting the request. Failures are surfaced explicitly instead of hidden so you can cross-check from a different network.