Scrutica
Supply Chain
Not yet available
Power capacity, hardware inventory, upstream suppliers, and downstream customers for the row owned by JD.com, Inc.; 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 JD Cloud North China (Langfang) Cloud 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-07-06
Operator (or owner of record) per the Scrutica facility row.
Description
JD.com / JD Cloud (京东云) North China hub-node self-built hyperscale data center at No. 66 Runhui Road, Langfang, Hebei Province. Operational Q4 2022 per DatacenterMap + JD Corporate Blog "ramps up construction" Feb 2022. Designated as one of the Beijing-Tianjin-Hebei (京津冀) regional hub-node data centers under China's national Eastern Data Western Compute (东数西算) project. Engineered with large-scale liquid cooling + heat recovery via high-temperature water system, targeting >10% carbon emission reduction + design PUE <1.1 per JD Corporate Blog. Operator: JD Cloud, the cloud computing subsidiary of JD.com, Inc.
Timeline
Operational
Oct 1, 2022
Notes
authority_tier=2: facility existence + Langfang Runhui Road siting + Q4 2022 operational date + liquid-cooling + PUE <1.1 design target anchored to JD Corporate Blog (Feb 2022) + DatacenterMap directory + W.Media trade press. Per-facility MW capacity: DatacenterMap directory lists 66 MW IT load (tier-3 editorial only); direct primary source (glory-bj.net contractor page) returned connection refused in research session; per anti-fabrication discipline, power_capacity_mw left NULL — do NOT inherit the 66 MW figure without primary-source verification. actual_operational_date=2022-10-01 placeholder for Q4 2022 framing (no specific date disclosed). Lat/lng NULL — Runhui Road only.
Other JD.com, Inc. 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 (Max Smart 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: JD.com, Inc.
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 JD Cloud North China (Langfang) Cloud 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 > 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