Method 2026-09-26
Compute Leverage
Allied Coordination
Export-control alignment in facility ownership chains
Jurisdictions recorded in facility ownership chains, classified against the dated export-control regime map.
8 corrections · latest Sep 25, 2026
- Sep 25, 2026 · Visibility sheet: Google’s sites counted as having no controlling jurisdiction
- Sep 25, 2026 · Export-control alignment: four SEC filers read as unresolved because of their own subsidiaries
- Sep 23, 2026 · Cascade: relationships last disclosed five or more years before the latest filing wave no longer propagate
- Sep 23, 2026 · Cascade: partnerships no longer propagate as supply
- Sep 23, 2026 · Capacity totals: planned capacity counted as present capacity
- Sep 23, 2026 · Export-control alignment: ownership chains start where a source establishes the role
- Sep 22, 2026 · EDA market shares in scenario and coordination analysis
- Sep 22, 2026 · Foundry market shares for the second quarter of 2025
- STRONG
- 64
- chain reaches a non-aligned or restricted jurisdiction · ~391,057 H100-eq GPUs operating · ~163,247 more on records not operating
- OPAQUE
- 3,435
- unresolved endpoint, jurisdiction or coordination posture · ~1,329,958 H100-eq GPUs operating · ~7,789,627 more on records not operating
- MILD
- 25
- documented endpoint; classified jurisdictions include allied-partial, none non-aligned or restricted · ~4,368 H100-eq GPUs operating · ~151,592 more on records not operating
- NONE
- 742
- documented endpoint; every organisation jurisdiction allied-coordinated · ~11,287,129 H100-eq GPUs operating · ~4,670,048 more on records not operating
| Facility | Located | Site organisation | Severity | Status | Hops | H100-eq |
|---|---|---|---|---|---|---|
| Alibaba Zhangbei | CN | Alibaba | STRONG | Operational | 1 | ~132,895 |
| Huawei Horinger | CN | Huawei Technologies | STRONG | Operational | 1 | ~123,799 |
| VNET Bayin Ulanqab | CN | VNET Group ADR | STRONG | Operational | 1 | ~122,789 |
| Aramco Groq Inference Cluster | SA | Saudi Aramco | STRONG | Operational | 1 | ~7,475 |
| Core42 SuperPOD | AE | G42 | STRONG | Operational | 2 | ~1,272 |
| Yandex Chervonenkis | RU | Yandex | STRONG | Operational | 1 | ~502 |
| Saudi Aramco Dammam-7 | SA | Saudi Aramco | STRONG | Operational | 1 | ~500 |
| Saudi Aramco Tuwaiq-1 | SA | Saudi Aramco | STRONG | Operational | 1 | ~416 |
| Core42 AI-03 | AE | G42 | STRONG | Operational | 2 | ~395 |
| Yandex Lyapunov | RU | Yandex | STRONG | Operational | 1 | ~346 |
| Yandex Galushkin | RU | Yandex | STRONG | Operational | 1 | ~343 |
| Condor Galaxy 1 (CG-1) | US | G42 | STRONG | Operational | 2 | ~243 |
| G42 Artemis | AE | G42 | STRONG | Operational | 2 | ~82 |
| KAUST Shaheen-III | SA | King Abdullah University of Science and Technology | STRONG | Operational | 1 | — |
| Alibaba Cloud in Germany | DE | Alibaba | STRONG | Operational | 1 | — |
| Alibaba Cloud in Indonesia | ID | Alibaba | STRONG | Operational | 1 | — |
| Alibaba Cloud in Japan | JP | Alibaba | STRONG | Operational | 1 | — |
| Alibaba Cloud in Malaysia Phase 1 | MY | Alibaba | STRONG | Operational | 1 | — |
| Alibaba Cloud in Malaysia Phase 2 | MY | Alibaba | STRONG | Operational | 1 | — |
| Alibaba Cloud in Mexico | MX | Alibaba | STRONG | Operational | 1 | — |
| Alibaba Cloud in Philippines Phase 1 | PH | Alibaba | STRONG | Operational | 1 | — |
| Alibaba Cloud in Saudi Arabia | SA | Alibaba | STRONG | Operational | 1 | — |
| Alibaba Cloud in Silicon Valley | US | Alibaba | STRONG | Operational | 1 | — |
| Alibaba Cloud in Singapore | SG | Alibaba | STRONG | Operational | 1 | — |
| Alibaba Cloud in South Korea Phase 1 | KR | Alibaba | STRONG | Operational | 1 | — |
| Alibaba Cloud in South Korea Phase 2 | KR | Alibaba | STRONG | Operational | 1 | — |
| Alibaba Cloud in Thailand Phase 1 | TH | Alibaba | STRONG | Operational | 1 | — |
| Alibaba Cloud in Thailand Phase 2 | TH | Alibaba | STRONG | Operational | 1 | — |
| Alibaba Cloud in UAE | AE | Alibaba | STRONG | Operational | 1 | — |
| Alibaba Cloud in United Kingdom | GB | Alibaba | STRONG | Operational | 1 | — |
How the analyzer classifies each facility
The classification uses recorded ownership chains and the versioned regime map linked below.
1. Ownership chain
Start with the organisation a source establishes as the facility’s operator, owner or AI-hardware owner, the starting point the Compute Visibility attribution uses; a facility with none is unresolved, and no chain is walked from a recorded name no source supports. Parent records are ranked by source, confidence and date; an unresolved tie ends the chain, and a link reviewed as not establishing control is not followed. After the first organisation, an SEC identifier, a government entity or a qualifying source ends it, as do a missing parent, a cycle and the ten-organisation limit.
2. Posture lookup
Each organisation’s recorded headquarters country is matched to the regime map (version 2026-04-25, built from the Wassenaar participant list, EU 2021/821, EU Delegated Regulation 2025/2189, national export-control authorities, and CSIS Allen and Goldston, March 2025). A country the map does not cover is counted as unresolved, as is an organisation with no recorded country at all; neither is read as agreement with the rest of the chain.
3. Severity rule
Classes are applied in order. STRONG whenever the chain records a non-aligned or restricted jurisdiction, and no later gap in the evidence relaxes it. Otherwise an unresolved country, posture or ownership endpoint gives OPAQUE. Only a chain complete at every hop reaches MILD, for an allied-partial jurisdiction, or NONE.
4. Unresolved records
A documented non-aligned or restricted jurisdiction takes precedence over an unresolved chain. Facilities with no linked organisation remain identifiable within OPAQUE.
Severity reference
STRONGThe recorded chain includes a jurisdiction classified as non-aligned or restricted in the regime snapshot.
OPAQUEThe chain lacks a documented endpoint or contains unresolved jurisdictions or coordination postures, with no recorded non-aligned or restricted jurisdiction.
MILDEvery organisation jurisdiction is classified, at least one is allied-partial, none is non-aligned or restricted, and the chain reaches a public-filing or government endpoint.
NONEEvery organisation hop has a recorded jurisdiction classified as allied-coordinated, and the chain reaches a public-filing or government endpoint.
Regime classifications are versioned, so a citation can be re-run against the regime map as it stood: version 2026-04-25 (JSON).
The Center for a New American Security publishes a program-level Sovereign AI Index (Chavez, Chilukuri and Scanlon, April 2026): cnas.org.
Regime coverage, scenarios, and the export-control timeline
Which regimes cover which technologies, how the multilateral regimes are structured, the named coordination scenarios and the export-control timeline. The jurisdictions listed are supply-chain participants outside coordination, in no ranked order.