# Alibaba Cloud — `alibaba-regions`

| | |
|---|---|
| Sources | `https://www.alibabacloud.com/help/en/ecs/product-overview/regions-and-zones` (docs table, primary) + `https://www.alibabacloud.com/global-locations` (static `<li>` list with "Availability Zone: N · Released in YYYY", fetched once per run for launch years) |
| Kind / mode | `cloud_provider` / `html`, implementation `cloud_regions`, parser `cloud_alibaba_regions_v1` |
| Fetch | L1 direct, 0 credits, 2 fetches/run (robots.txt disallows `/*.json`, `/api/*` — not used) |
| Schedule | weekly |
| License / attribution | Publicly published provider documentation; facts only — "Alibaba Cloud — alibabacloud.com/help" |
| Verified live | 2026-09-11: 33 regions, 33 valid, 0 rejected; 31/33 launch years joined |

Table `Region name | Region ID | Number of zones | Zone name | Zone ID` → name ("Germany (Frankfurt)"), code
(`eu-central-1`), `availabilityZones`. City = parenthetical (curated coordinates; "Silicon Valley" and "Virginia" are
metro-level markers), country from the name prefix (China / SAU / UK / US / UAE / Mexico) or the country word.
`China (Hong Kong)` → HK. Launch year joined on the display name from global-locations (`launchedOn = "2016"`).

Spot checks: `cn-hangzhou` → Hangzhou, Zhejiang CN, 8 zones, 2011; `ap-northeast-1` → Tokyo JP, 5 zones, 2016;
`eu-central-1` → Frankfurt DE, 3 zones, 2016.

**Quirks.** "China (Nanjing - Local Region) Closing Down" / "Fuzhou" → status kept `operational` with
`externalIds.lifecycle = closing_down` and `kind = local_region` (they still exist; retirement is not dated).
"SAU (Riyadh - Partner Region)" → `externalIds.operated_by = partner`. "Brazil (Sau Paulo)" typo → São Paulo alias.
"Mexico" (`na-south-1`) publishes no city → country only, no coordinates.