Scrutica
Supply Chain
Power capacity, hardware inventory, upstream suppliers, and downstream customers for the row owned by Alibaba; any BIS Entity List exposure is walked through the canonical org graph rather than asserted at the facility row.
Capacity, ownership chain, and supply-chain position for Alibaba Cloud Nantong Super Data Center, including any export-control exposure that surfaces when the BIS Entity List touches a node above the facility in the chain.
As of 2026-05-22
Operator (or owner of record) per the Scrutica facility row.
Alibaba, the documented owner of Alibaba Cloud Nantong Super Data Center, sits as a seed node in 1 pre-built cascade scenario. Severity is the scenario's seed-impact value (per-node override where one is defined); decay reflects the curator's substitutability assessment for the disrupted role. Run any scenario to walk the propagation through the full supply-chain graph.
Upstream dependency on US tools (EDA, advanced equipment, foundry access) is structural for Chinese AI compute consumers — domestic substitutes exist but cover narrow node ranges, so impact propagates with little dampening per hop.
Description
Alibaba Cloud's Nantong super data center (Jiangsu Province), one of three super data centers (Hangzhou + Nantong + Ulanqab) put into production simultaneously by Alibaba Cloud in July 2020, collectively adding capacity for >1M servers. Self-designed self-built, hosting Alibaba's X-Dragon server architecture, Hanguang 800 AI inference chip, and Apsara distributed OS. Distinguished by an Alibaba-self-developed uninterruptible power supply (UPS) solution to improve PUE per Alibaba Cloud Community blog 2020-07.
Timeline
Operational
Jul 1, 2020
Notes
authority_tier=2: facility existence + Nantong siting + July 2020 operational launch anchored to Alibaba Cloud corporate blog. Per-facility MW capacity, exact square-footage, and server count NOT disclosed at facility precision in primary source — the trio-aggregate (>1M additional servers across Hangzhou + Nantong + Ulanqab) is what Alibaba publicly disclosed. Coordinates NULL.
Parent / controlling entity, documented through a secondary structural source.
Source: factset-entity-structure-2026-05-14 · Confidence HIGH
Chain reaches Intime Retail; ownership beyond that point is not documented in Scrutica’s available data (as of 2026-05-22). Further hops may exist but are not yet ingested.
China (CN)
Not a Wassenaar participant; operates its own Export Control Law (2020) and Unreliable Entity List; MOFCOM and the Ministry of Commerce administer dual-use catalogues.
Regimes: Chinese Export Control Law (2020); MOFCOM Unreliable Entity List authority
Established via: Intime Retail
No flags found across the chain (BIS Entity List, designation-cascade closures, or compute-threshold reporting obligations) as of 2026-05-22. Cascade closures evaluated: 0.
No ownership-change events documented in the available data for any entity in this chain over the last 5 years. Events draw from PitchBook deal records (M&A, buyout, divestiture, asset sale, JV formation); PitchBook coverage is strongest for private US/EU transactions and partial for state-owned-enterprise restructurings or non-Western private deals. Subsequent ingestion runs may add events here.
No documented sovereign or state-linked LP investment touches any entity in this chain. PitchBook LP-disclosure rate is partial; absence of evidence here is not evidence of absence.
The walk for Alibaba Cloud Nantong Super Data Centerstarts at the operator org id (or owner org id when no operator is recorded) and climbs upward through the unified affiliate graph, normalized to trace child-to-parent relationships. At each hop, the highest-authority parent edge wins (priority ordering: SEC EDGAR / 10-K / LEI registry > FactSet Workstation / Revere > Compustat > BIS / Federal Register > PitchBook). Confidence and recency break ties.
The walk terminates on (a) a node with a public-filing-grade ancestor edge — a SEC filer, an LEI-registered listed entity, or a 10-K-disclosed parent — (b) a government entity, (c) a 10-hop limit, or (d) a detected cycle. When termination is not at a public filer or government, the panel labels the chain's end-state as opaque beyond that point. Opacity is reported, never implied.
Per-source confidence (PitchBook): HIGH for Parent / Subsidiary edges; MEDIUM for JV and AFFILIATE edges. Known limitations: (1) shell companies with undisclosed principals terminate the public-record walk; (2) recent transactions reach the panel after PitchBook's weekly refresh; (3) cross-jurisdiction private holding structures may carry intermediate hops that are not in any ingested source. Each row carries an edge-level as of date so freshness is auditable per hop.
Two further caveats are inherent to how the walker and the underlying data compose. The walker selects a single highest-authority parent per hop, so JV or multi-parent ownership structures collapse to one displayed path; alternate parents exist in the ingested sources but are not surfaced on this card. And some PitchBook edges encode parent-of relations against entity-resolved stub IDs whose display name reflects a sub-entity (a business unit, an acquired-then-renamed line) rather than the canonical parent — when a chain reads structurally surprising, the per-row source citation is the authoritative reference, not the chain's narrative shape.
Computed at: 2026-05-22. Walk depth observed: 2 hops. Sources combined: Scrutica facility record + PitchBook affiliate graph + SEC CIK cross-reference + LEI registry + (where applicable) FactSet Revere supply-chain graph + Federal Register designation closures.
Alibaba Cloud in India
IN
Other Facilities in CN