Scrutica
Supply Chain
Not yet available
Power capacity, hardware inventory, upstream suppliers, and downstream customers for the row owned by China Telecom; 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 China Telecom Cloud Computing Inner Mongolia Information Park, 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.
Ownership chain not yet documented in the available data (licensed corporate-ownership database, licensed supply-chain database, SEC filings, LEI registry; as of 2026-07-06). The chain may extend further once additional ingestion runs complete; absence here reflects coverage at this snapshot, not a documented apex.
Description
China Telecom Cloud Computing Inner Mongolia Information Park (中国电信云计算内蒙古信息园), sited ~25 km south of Hohhot city center on Yunzhan E St., Horinger County. China's largest single state-cloud information park per China Daily state-government portal disclosure. Anchors China Telecom Tianyi Cloud (天翼云) North China compute footprint at the Inner Mongolia hub-node of China's national Eastern Data Western Compute (东数西算) strategy ("Linger data center cluster" designation). Total campus footprint 1,006,000 m² designed across 42 data centers + 19 supporting facilities at full buildout, with cloud computing capacity 100,000+ racks at full buildout. Currently operational: 8 data centers + ~20,000 racks + ~270,000 servers per IDCNova 2022-10 reporting on Area B topping-out. Hosts >57 internet-company tenants per China Daily disclosure. Investment 17.35B yuan (~US$2.5B). First buildings operational 2013; Area B additional construction started 2022-06-07, topped out 2022-10.
Timeline
Operational
Jan 1, 2013
Notes
authority_tier=2: facility existence + Horinger / Hohhot Yunzhan E St. siting + 17.35B yuan investment + 1,006,000 m² campus + 42-data-center design + 270K-server operational scale + 57+ tenant count anchored to China Daily government portal (state-affiliated tier-2-leaning) + IDCNova 2022-10 trade-press corroboration. Per-facility MW capacity NOT disclosed at primary tier (150 MW figure circulates in secondary press but NOT primary-source confirmed; per anti-fabrication discipline, power_capacity_mw NULL). Lat/lng NULL — Horinger County / Yunzhan E St. siting only. Park-level record (DC1-DC8 are sub-facilities within the same campus). actual_operational_date=2013-01-01 placeholder for "2013 first buildings operational" framing.
Other China Telecom Facilities
No jurisdictions documented for this chain in the available data — at least one ancestor must carry an HQ country in the canonical organization record for jurisdictional exposure to compute. This section will populate automatically as additional ingestion adds HQ countries to the chain.
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 China Telecom Cloud Computing Inner Mongolia Information Parkstarts 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: 1 hop. 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