# Tencent Cloud — `tencent-regions`

| | |
|---|---|
| Source | `https://www.tencentcloud.com/document/product/213/6091` ("Regions and Availability Zones" docs table) |
| Kind / mode | `cloud_provider` / `html`, implementation `cloud_regions`, parser `cloud_tencent_regions_v1` |
| Fetch | L1 direct, 0 credits. A plain `curl` with the bot UA receives a 29 KB anti-bot JavaScript page (robots.txt too), but the SDK's direct fetcher (HTTP/2, full browser-like Accept headers) gets the 760 KB server-rendered document at level 1 — verified live. If that ever flips, `looksBlockedOrEmpty` escalates to L2 (maxLevel 2; no Scrapfly). |
| Schedule | weekly |
| License / attribution | Publicly published provider documentation; facts only — "Tencent Cloud — tencentcloud.com/document" |
| Verified live | 2026-09-11: 26 regions, 26 valid, 0 rejected (21 operational, 5 restricted) |

Table `Region | Region ID | Number of AZs | AZ` — the first row of a region carries name/id/count, following rows only
AZ names (skipped). Names: "North China (Beijing)", "Asia Pacific and the Middle East (Singapore) Coverage: Southeast
Asia" (coverage kept in `externalIds.coverage`), "Beijing Finance Available only to finance institutions…" →
status `restricted`, `externalIds.realm = finance`; "Shanghai Self-driving Cloud" → `restricted`, `realm =
self_driving_cloud`. "Hong Kong (China), Macao (China), and Taiwan (China)" → Hong Kong HK.

Spot checks: `ap-beijing` → Beijing CN, 6 AZs; `ap-singapore` → Singapore SG, 4 AZs; `eu-frankfurt` → Frankfurt DE,
3 AZs; `na-ashburn` ("Virginia") → Northern Virginia US (metro); `me-saudi-arabia` → SA, no city published.
`launchedOn` is not published.