Hyperscale DCOperational

Johns Hopkins Data Center

MD, US

Supply Chain

Not yet available

SCRUTICA.COM

im3_pnnlLast refreshed Apr 28, 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 Johns Hopkins Data Center, 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 →

Notes

From IM3/PNNL Open Source Data Center Atlas

Water Risk Score: 3
Water Risk Label: Medium-High
Baseline Water Stress: 2.86
Water Risk Source: wri-aqueduct
Water Risk Methodology: Country-level BWS from WRI Aqueduct 4.0

Nearby Facilities (within 100 km)

Expedient Tidepointcolocation Zayo Baltimore - 111 Market Plcolocation Crown Castle Baltimorecolocation AiNET One Market Centercolocation Lumen Baltimorecolocation TierPoint Baltimorecolocation

Energy Profile

Grid Carbon

Carbon Intensity

Grid Connection

Balancing Authority

NERC Region

eGRID Subregion

Other Facilities in US

1.5 GW700,000 GPUs

Sovereign AIGovernance

Government programs that deploy in these facilities

CompareTools

Compare two facilities side by side

Built for the AI governance research community