QTS Cedar Rapids

Cedar Rapids, Iowa, US

Supply Chain

Not yet available

SCRUTICA.COM

epoch-aiLast refreshed May 19, 2026

Power capacity, hardware inventory, upstream suppliers, and downstream customers for the row owned by ; 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 QTS Cedar Rapids, including any export-control exposure that surfaces when the BIS Entity List touches a node above the facility in the chain.

Ownership & Control

Visibility Data Gap

As of 2026-06-12

Ownership chain not yet available; the facility row has no documented operator or owner org. The panel will populate once a primary or secondary source assigns one and the next refresh lands.

Allied Coordination Gap · OPAQUE

Facility has neither an operator nor an owner organization populated. Coordination-gap classification cannot proceed.

View on the Allied Coordination Gap analyzer →

Description

QTS Cedar Rapids sits alongside a Google data center in Big Cedar Industrial Center. It is divided into two phases which are expected to be completed in late 2026 and late 2027. We estimate its power capacity based on satellite images and 3D renderings of the air-cooled chillers lining each building. The compute capacity is based on this power capacity and the assumption that the best available NVIDIA AI servers will be used for each phase. The estimated power for phase 1 is consistent with a 6

Nearby Facilities (within 100 km)

Google Cedar Rapidsai training Cologix DSM2colocation

Other Facilities in US

Verification provenance

Cited

Frontier Data Centers — methodology

Epoch AI · Epoch AI · published November 1, 2025 · Scrutica accessed May 19, 2026 · CC-BY 4.0

This row enters Scrutica via Epoch's Frontier Data Centers corpus (data_source: epoch-ai). Epoch's published methodology derives estimates from satellite imagery (SkyFi, Sentinel-2, Google Earth), permitting documents, and corporate disclosures; the page's own uncertainty framing is bounded to cooling-model error — as much as 2× higher or lower than model estimates in theory, with validated error of 1% on the two ground-truth cases Epoch holds and ≤50% against indirect references such as chip-quantity-derived IT power. Epoch does not publish quantified compute-, cost-, or timing-confidence bounds on this page. Scrutica preserves Epoch's authority_tier (2) and source_url so the chain back to the originating verification work is auditable from this page.