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 in Singapore, including any export-control exposure that surfaces when the BIS Entity List touches a node above the facility in the chain.
As of 2026-06-12
Operator (or owner of record) per the Scrutica facility row.
Chain terminates at a publicly-listed entity (Alibaba). Subsequent ownership is observable via SEC filings or the equivalent national registry.
Alibaba, the documented owner of Alibaba Cloud in Singapore, 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.
Timeline
Operational
Jul 2, 2015
Notes
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-06-12. 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.
GIC Private
GIC is associated with Singapore’s Singapore: National AI Strategy 2.0 / AISG / NSCC Sovereign Compute. See actor profile →
Touches Alibaba (chain hop 1) via a private-market fund. Commitment dollar value not disclosed (2023-01-18).
Temasek Holdings
Temasek is associated with Singapore’s Singapore: National AI Strategy 2.0 / AISG / NSCC Sovereign Compute. See actor profile →
Touches Alibaba (chain hop 1) via a private-market fund. Commitment dollar value not disclosed (2020-01-01).
China Development Bank FOF
CDB is associated with China’s China: National AI Programs / Big Fund III / Eastern Data Western Computing. See actor profile →
Touches Alibaba (chain hop 1) via a private-market fund. Fund commitment disclosed (amount held under license) (2015-09-03).
Mubadala Investment Company
Mubadala is associated with United Arab Emirates’s UAE: Stargate UAE / G42 / Core42 / TII Sovereign AI + Microsoft Cumulative + Abu Dhabi Digital Strategy. See actor profile →
Touches Alibaba (chain hop 1) via a private-market fund. Commitment dollar value not disclosed.
Khazanah Nasional
Khazanah is associated with Malaysia’s Malaysia: National AI Roadmap 2030 / Sovereign AI Cloud. See actor profile →
Touches Alibaba (chain hop 1) via a private-market fund. Commitment dollar value not disclosed.
The walk for Alibaba Cloud in Singaporestarts 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-06-12. 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.
Alibaba Cloud in India
IN
Other Facilities in SG