Scrutica
PUE
Supply Chain
Power capacity, hardware inventory, upstream suppliers, and downstream customers for the row owned by Baidu; 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 Baidu Cloud Computing (Yangquan) 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-07-06
Operator (or owner of record) per the Scrutica facility row.
Baidu, the documented owner of Baidu Cloud Computing (Yangquan) 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
Baidu's flagship self-built data center, the first large-scale Baidu Cloud Computing facility, located in the Eastern District of Yangquan Economic Development Zone, Shanxi Province. Phase 1 includes eight high-standard module buildings, ~6,000 cabinets, ~700,000 CPUs (3M+ cores), 160,000+ servers, 4,000 PB storage. Annual-average PUE ~1.09 (43% energy savings vs baseline) per Baidu corporate disclosures. Disclosed at the March 2023 ERNIE Bot launch event as "currently the largest single intelligent computing center in Asia" for AI workloads, with 40-quintillion-FLOP/s compute claim. Total project investment ¥47.08 billion per state-affiliated reporting.
Notes
authority_tier=2: facility existence + Yangquan siting + Phase 1 specifications (6K cabinets, 160K servers, 4000 PB, PUE 1.09) anchored to Baidu Wiki corporate page + Shanxi Daily / Xinhua state-media corroboration + Yicai Global. The 40-quintillion-FLOP/s claim is Baidu's own (March 2023 ERNIE Bot event); per-architecture / per-GPU breakdown NOT disclosed in primary source. Coordinates NULL — Yangquan Eastern District EDZ siting only. Per-facility MW NOT disclosed.
Other Baidu Facilities
Parent / controlling entity, documented through a public filing or LEI registry.
Source: HKEX / SSE public filing · Confidence HIGH
Chain terminates at a publicly-listed entity (Handsome Reward Limited). Subsequent ownership is observable via SEC filings or the equivalent national registry.
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: Baidu
No flags found across the chain (BIS Entity List, designation-cascade closures, or compute-threshold reporting obligations) as of 2026-07-06. 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 a licensed corporate-ownership database’s deal records (M&A, buyout, divestiture, asset sale, JV formation); 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. The licensed fund/LP database’s LP-disclosure rate is partial; absence of evidence here is not evidence of absence.
The walk for Baidu Cloud Computing (Yangquan) 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 > licensed corporate-ownership database > licensed supply-chain database > BIS / Federal Register > licensed affiliate graph). 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 (licensed corporate-ownership database): 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 the database'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 licensed-database 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-07-06. Walk depth observed: 2 hops. Sources combined: Scrutica facility record + licensed corporate-ownership database + SEC CIK cross-reference + LEI registry + (where applicable) licensed supply-chain database + Federal Register designation closures. The licensed databases are held under subscription and not redistributed; per-hop labels name no vendor.
4
CN