Data Center Watch
Data Center Watch › Patterns

Buildout patterns & signals

Commonalities across the site’s sourced data, and the directional predictions they support. Two lanes: Observed (primary-sourced facts) and Derived (arithmetic on those facts). Every derived figure shows its formula, the exact source numbers, and a defensibility tier — grounded (a ratio of two sourced figures) or directional (a trend to read as “at the recent observed pace”). Nothing is estimated to fill a gap.

Observed — the ERCOT large-load funnel

438.0 GWRequested (queue)
9.0 GWApproved to energize
3.9 GWObserved operating peak

ERCOT large-load interconnection queue, snapshot 2026-03-31. Source: ERCOT LLI.

Derived — what the funnel implies

2.1%
grounded
Approval rate — share of the requested queue cleared to energize
approved_to_energize ÷ requested = 9,042 ÷ 438,000 MW. The queue is a demand signal, not a delivery schedule.
Inputs: ERCOT LLI
43%
grounded
Realization rate — approved capacity that is actually drawing power
observed_peak ÷ approved_to_energize = 3,883 ÷ 9,042 MW.
Inputs: ERCOT LLI
0.89%
grounded
Realized-to-queue — real operating load vs the headline queue
observed_peak ÷ requested = 3,883 ÷ 438,000 MW. Under 1% of the headline queue is metered load today.
Inputs: ERCOT LLI
4.8×
grounded
“Paper gigawatts” multiple — requested queue vs the whole metered grid
requested_queue ÷ metered_system_peak = 438,000 ÷ 91,075 MW. The requested queue exceeds ERCOT's entire current peak by this multiple — full realization would require the grid to grow several-fold.
Inputs: ERCOT LLI · EIA-930
-3,967 MW
directional
Firm-capacity headroom before any new large load lands
firm_dispatchable − metered_peak = 87,108 − 91,075 MW. A thin cushion on the dispatchable fleet alone; intermittent nameplate is excluded. Point-in-time, not a forecast.
Inputs: EIA-860M · EIA-930
flat vs surging
directional
Approvals have stalled while requests surged
approved_to_energize sits at 9,042 MW at the latest snapshot with a value, while requested has climbed toward 438,000 MW — each incremental GW requested converts to a smaller share of real approval. Extrapolating headline queue growth to future load is unreliable.
Inputs: ERCOT LLI

Operators by attributed capacity

Sum of per-facility disclosed/attributed power (gross MW, falling back to IT MW) by operator. Disclosure-biased: only 636 of 27,647 tracked facilities state any power figure, and rows mix operational, announced, and third-party-estimated capacity — read as a coverage-weighted ranking, not an operational-MW census.

OperatorFacilitiesAttributed capacity
Amazon1517.1 GW
Crusoe312.5 GW
Softbank/Open AI (unconfirmed)19.2 GW
TransGas Development, LLC24.8 GW
Homer City Redevelopment (with Kiewit as contractor/partner)14.5 GW
Meta204.4 GW
Google244.1 GW
Balico LLC13.5 GW
Open AI13.2 GW
Vermaland LLC13.0 GW
Stak13.0 GW
IREN22.8 GW
Microsoft142.5 GW
VALCO HANOVER COUNTY12.4 GW
Hut 842.1 GW
Tract22.1 GW
Rubix12.0 GW
Poolside/CoreWeave12.0 GW
Granite Renewables12.0 GW
Eneus Energy12.0 GW

Counties by tracked capacity

Where disclosed capacity concentrates — a directional “next-hotspot” read, same disclosure caveat as above.

CountyAttributed capacity
Laramie, WY, United States10.2 GW
Pike, OH, United States9.2 GW
Box Elder, UT, United States9.0 GW
Lea County, NM, United States7.0 GW
Pecos, TX, United States7.0 GW
Mingo, WV, United States4.8 GW
Indiana, PA, United States4.5 GW
Lackawanna, PA, United States4.3 GW
Hanover, VA, United States4.2 GW
Pittsylvania, VA, United States3.8 GW
Maricopa, AZ, United States3.8 GW
Effingham, GA, United States3.2 GW
North Slope, AK, United States3.1 GW
Lake, IN, United States3.1 GW
Pinal, AZ, United States3.0 GW

Derived — connectivity & measurement presence

Cross-referencing the facility registry against 1,065 RIPE Atlas anchors (measurement servers hosted inside data centres) locates where the buildout has confirmed, measured internet presence — and where it doesn't yet. Source: RIPE Atlas / RIPE NCC.

741 data centers
grounded
Data centers with confirmed measurement presence
943 of 1,065 RIPE anchors (88.5%) geo-match a tracked facility within 8 km (haversine spatial join). A hosted anchor is hard evidence of live, carrier-grade connectivity on-site — a signal a greenfield announcement can't fake.
Inputs: RIPE Atlas
Cross-source accuracy check: only 4 of the 943 matched anchors disagree on country between RIPE and our registry — independent corroboration that both geolocations are sound.

DNS root-server latency (global reachability)

DNS rootProbesMedian RTT (ms)p10p90
A-root13,94419.692.55117.08
B-root2,00035.7113.99171.5
C-root4,24744.4715.48191.49
D-root13,9446.331.0423.79
E-root13,94417.121.75143.24
F-root13,94428.878.16170.47
G-root2,03532.171.49245.97
H-root13,94526.375.5106.8
I-root13,94621.414.53134.56
J-root13,94626.938.08120.18
K-root13,94719.785.15114.74
L-root13,94510.631.1465.41
M-root13,9456.770.9728.24

Networks hosting the most measurement infrastructure

Network (AS holder)Anchors hosted
DigiCert21
Vultr LLC18
G-Core Labs S.A.16
Console Connect13
Misaka Network, Inc.12
Tele2 Kazakhstan12
DigitalOcean8
NetActuate7
OVHcloud7
marbis GmbH6
These are analytical readings, not investment advice or a delivery forecast. ERCOT is the deepest-covered region today; the same funnel math generalizes to PJM/MISO/CAISO and other ISOs as their queues are ingested (each with its own source). Derived figures update every build as the underlying sourced data refreshes.