Scrutica
GPUs
Supply Chain
Power capacity, hardware inventory, upstream suppliers, and downstream customers for the row owned by xAI; 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 xAI Colossus 2, 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.
Ownership chain not yet documented in the available data (licensed corporate-ownership database, licensed supply-chain database, SEC filings, LEI registry; as of 2026-06-12). The chain may extend further once additional ingestion runs complete; absence here reflects coverage at this snapshot, not a documented apex.
Description
xAI Colossus 2 is the follow-up to Colossus 1. Like its predecessor, it is located in Memphis and was converted from an existing building. To start powering the data center, xAI made the unusual choice to install natural gas turbines across the border in Mississippi, possibly to get faster approval for their operation. We use a combination of satellite/aerial images and announcements to estimate the timeline and compute capacity of the data center.
Nearby Facilities (within 100 km)
flop_epoch_divergence_>50pct — Scrutica's peak_pflops_fp16 = 569,705 on this facility-level row (Frontier-DC ingest, data_source=epoch-ai) is the SUM of three OPERATIONAL Memphis cluster phases: dep-epoch-xai-colossus-memphis-phase-1 (98,940) + phase-2 (197,885) + phase-3 (272,880) = 569,705. Two ANNOUNCED Colossus 2 phases (1+2 of GB200, status=announced) do not contribute to the rollup by design (link-deployments-to-facilities.ts:255 OPERATIONAL_STATUSES filter). The killed validation table matched four Epoch GPU-cluster rows against this same rollup, producing -58.6% / +107.2% / +108.8% / +187.9% divergence — apparent disagreement that was actually rollup-vs-component on the same data Scrutica had already ingested per-phase as fac-epoch-gc-* rows.United States (US)
Operates the Export Administration Regulations (EAR) and the BIS Entity List under 15 CFR 730–774; deemed-export rules extend reach to foreign nationals on US soil.
Regimes: Wassenaar Arrangement; US EAR (BIS Entity List authority)
Established via: xAI
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.
Saudi Arabia's Public Investment Fund
PIF is associated with Saudi Arabia’s Saudi Arabia: HUMAIN / Project Transcendence. See actor profile →
Touches xAI (chain hop 1) via a private-market fund. Commitment dollar value not disclosed (2023-05-10).
Temasek Holdings
Temasek is associated with Singapore’s Singapore: National AI Strategy 2.0 / AISG / NSCC Sovereign Compute. See actor profile →
Touches xAI (chain hop 1) via a private-market fund. Commitment dollar value not disclosed (2020-01-01).
GIC Private
GIC is associated with Singapore’s Singapore: National AI Strategy 2.0 / AISG / NSCC Sovereign Compute. See actor profile →
Touches xAI (chain hop 1) via a private-market fund. Commitment dollar value not disclosed (2006-08-08).
Kuwait Investment Authority
KIA is a KW-domiciled sovereign vehicle (no Scrutica-tracked sovereign AI program for this country yet). See actor profile →
Touches xAI (chain hop 1) via a private-market fund. Commitment dollar value not disclosed (1999-11-01).
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 xAI (chain hop 1) via a private-market fund. Commitment dollar value not disclosed.
The walk for xAI Colossus 2starts 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.
xAI Colossus Memphis
Memphis, Tennessee, US