What does Watts see in Texas?
Dallas · Austin · San Antonio
Grid
75.8% of committed capacity in use
AWAITING BASELINE · ERCOT
River
Drought
Watts · a SIREN sub-index · does not feed the main number
The infrastructure index. The page is WATTS; the number on it is SUBSTRATE, five to one.
Intelligence is electricity with extra steps. You cannot train a frontier model without power, water and concrete, and unlike model weights, all three leave a public paper trail. Every input below is free, keyless and published by somebody with no interest in this question at all.
50.4 of 100 sits in the 35–54 band of this index’s own record. Ordinary. This is where most observations sit. That is a count of how loaded the substrate is, not a claim about what anyone is building on it.
Nothing on this page measures datacentre power or datacentre water. No public feed separates datacentre load from any other industrial load, and no arithmetic downstream can recover a split the input never contained. What is measured here is the condition of the substrate those datacentres are being built into: how much load never switches off, how much slack the grid has over it, how much water is in the rivers beside the clusters, and how much corporate and federal paperwork is moving.
A rising overnight floor in Texas is consistent with a new training cluster. It is equally consistent with a new smelter, a cold snap, an electrified rail yard, or a methodology change at the grid operator. A falling river is mostly rainfall. Correlation here is a hypothesis this page states and has not proved, and the honest version of that claim is much weaker than the exciting version.
This index does not feed the main SIREN number and never has. Its sources are not in the frozen reference distribution, so it is a separate instrument on a separate question. A page can be interesting without being load-bearing.
The grid
—
AWAITING BASELINE
How much load never switches off, and how little slack is left over it.
0 live · 4 awaiting baseline · 4 sources
The water
42.1 of 100
The state of the rivers and the ground the clusters were built beside.
2 live · 2 sources
The build-out
54.9 of 100
What companies had to write down, and what the government had to publish.
1 live · 2 awaiting baseline · 3 sources
Nine places where the American build-out actually is, and what each of the three pillars can and cannot see there. 3 of 9 have a free real-time demand feed. The other 6 say why not, in their own cell, rather than leaving a blank that reads as an oversight.
| Corridor | Grid | Driest gauge | Dev | D2+ | Signal |
|---|---|---|---|---|---|
| TexasDallas · Austin · San Antonio | 52,405 MW | 50%Colorado Rv at Austin | −50% | 52.4% | 2/2 river dry, drought +1 awaiting |
| Northern VirginiaLoudoun County · Data Center Alley | no free feed | 516%Potomac Rv at Little Falls | +416% | 14.7% | 1/2 river high |
| Central OhioNew Albany · Columbus | no free feed | 124%Scioto Rv at Columbus | +24% | 0.0% | 0/2 |
| Iowa & NebraskaCouncil Bluffs · Omaha | no free feed | — | — | 23.0% | 1/1 drought |
| GeorgiaAtlanta metro | no free feed | 81%Chattahoochee Rv near Norcross | −19% | 9.8% | 0/2 |
| ArizonaPhoenix metro | no free feed | 74%Colorado Rv at Lees Ferry | −26% | 16.9% | 1/2 river dry |
| OregonThe Dalles · Hillsboro | no free feed | 81%Columbia Rv at The Dalles | −19% | 57.6% | 1/2 drought |
| New YorkNYISO control region · reference | 13,172 MW | — | — | 0.0% | 0/1 +1 awaiting |
| CaliforniaSanta Clara · CAISO control region · reference | 20,351 MW | — | — | 0.0% | 0/1 +1 awaiting |
Driest gauge is the lowest of the corridor's gauges as a percentage of that gauge's own long-run median for the same day of the year, named in the cell — the minimum rather than the mean, because a cluster is constrained by its tightest water source and because averaging a creek in flood with a river at normal describes neither. Dev is the same number as a signed deviation. D2+ is the largest share of a corridor state's area the US Drought Monitor puts in severe drought or worse. Signal counts how many of the corridor's measurable series sit outside their band and names which, where the bands are ±25% of the median for a river and 20% of area for drought. Those two numbers are choices, not findings, and they are printed here so a reader can disagree with them. The river band is two-sided: a river far above its median is as unusual as one far below, and usually means rainfall rather than anything to do with a datacentre, so the cell says which side it fell on. A grid series joins the count only once it has a baseline to be unusual against — until then it reads awaiting, which is a different state from normal, and never a zero.
Dallas · Austin · San Antonio
Grid
AWAITING BASELINE · ERCOT
River
Drought
Loudoun County · Data Center Alley
Grid
NO FREE FEED · PJM
PJM publishes real-time demand only through Data Miner 2, which requires a registered subscription key. Keys are free; secrets in this repo are not permitted.
River
Drought
New Albany · Columbus
Grid
NO FREE FEED · PJM
Same PJM key wall as Northern Virginia.
River
Drought
Council Bluffs · Omaha
Grid
NO FREE FEED · MISO / SPP
MISO’s public data broker answered {"error": "no data"} on every message type tested on 2026-09-23. SPP has no equivalent keyless endpoint.
River
NO GAUGE
This corridor is in the index as a grid reference region, not a water one.
Drought
Atlanta metro
Grid
NO FREE FEED · Southern Co.
The Southeast is not an organised market. There is no independent system operator here and therefore no public real-time demand feed.
River
Drought
Phoenix metro
Grid
NO FREE FEED · APS / SRP
Vertically integrated utilities, no organised market, no public demand feed.
River
Drought
The Dalles · Hillsboro
Grid
NO FREE FEED · BPA
Bonneville publishes balancing-authority totals on a different cadence and format; not yet read by this collector.
River
Drought
NYISO control region · reference
Grid
AWAITING BASELINE · NYISO
River
NO GAUGE
This corridor is in the index as a grid reference region, not a water one.
Drought
Santa Clara · CAISO control region · reference
Grid
AWAITING BASELINE · CAISO
River
NO GAUGE
This corridor is in the index as a grid reference region, not a water one.
Drought
Every grid has a daily minimum — the hour when air conditioning, offices and traffic have all gone home. What is still drawing power at four in the morning is the load that never stops, and a datacentre is one of very few large loads that runs flat out at that hour. The overnight floor is the cleanest public proxy for always-on industrial demand that exists without a utility contract. It is also moved by smelters, cold snaps and pumping, which is why New York and California are here as reference regions rather than as subjects.
ERCOT · Texas
52,405MW
overnight floor · 00:00–06:00 CT · 2026-10-14
87% of the night’s high (60,321 MW) · range 7916 MW
AWAITING BASELINE22 of 30
72 of 72 five-minute intervals used
NYISO · New York
13,172MW
overnight floor · 00:00–06:00 ET · 2026-10-14
AWAITING BASELINE22 of 30
72 of 72 five-minute intervals used
CAISO · California
20,351MW
overnight floor · 00:00–06:00 PT
89% of the night’s high (22,946 MW) · range 2595 MW
AWAITING BASELINE21 of 30
72 of 72 five-minute intervals used
ERCOT headroom, right now
75.8% of committed capacity in use
57,992 MW of 76,509 MW committed · 18,517 MW spare · tick at 90%
Physical responsive capability 7092 MW now,
low of 6786 MW today across 149 samples.
ERCOT’s own reading of its own grid: There is enough power for current demand.
(Normal Conditions, emergency level 0).
AWAITING BASELINE22 of 30
Cooling a datacentre consumes water, and the argument about how much is one of the loudest live public fights about this industry. Nobody publishes the consumption. What is published, free and keyless, is the state of the water the clusters have to draw on: the flow in the river beside them, measured against the median for that same calendar date over that gauge’s whole record — 127 years at Austin, 116 at Leesburg. The denominator is the Geological Survey’s, not ours.
Median across the nine: -2.4% above normal. The mean is -196.3% and is deliberately not the scalar — one creek in flood moves a mean of ratios by hundreds of points and moves a median by nothing. Driest: Colorado Rv at Austin. Wettest: Goose Creek near Leesburg. USGS daily values settle the following morning, so this reads one day behind.
| Gauge | Flow | Normal | Of normal | Dry ← → Wet | Record |
|---|---|---|---|---|---|
| Colorado Rv at Austin Austin–San Antonio · TX | 238 | 476 | 50% | 1899–2026 | |
| Trinity Rv at Dallas Dallas–Fort Worth · TX | 528 | 388 | 136% | 1914–2026 | |
| Goose Creek near Leesburg Loudoun County · VA | 523 | 40 | 1308% | 1910–2025 | |
| Potomac Rv at Little Falls Northern Virginia · MD | 12,600 | 2440 | 516% | 1931–2026 | |
| Scioto Rv at Columbus Central Ohio · OH | 205 | 166 | 124% | 1921–2026 | |
| Chattahoochee Rv near Norcross Atlanta metro · GA | 1200 | 1480 | 81% | 1957–2026 | |
| Colorado Rv at Lees Ferry Phoenix metro · AZ | 6610 | 8910 | 74% | 1922–2026 | |
| Columbia Rv at The Dalles The Dalles · OR | 82,100 | 101,000 | 81% | 1879–2025 |
Share of each state’s area in D2 — severe drought or worse. D0 is on somewhere almost always and carries no information; D2 is roughly where water utilities start issuing restrictions, which is where a river stops being scenery and starts being a permit condition. The Drought Monitor is a weekly expert assessment produced by NDMC, USDA and NOAA. It is a judgement, not an instrument reading, and it is averaged here without area or population weighting.
| State | D2+ | Share of area | D3 / D4 |
|---|---|---|---|
| Oregon The Dalles, Hillsboro | 57.6% | 20.2 / 0.0 | |
| Texas Dallas, Austin, San Antonio | 52.4% | 13.5 / 1.1 | |
| Nebraska Omaha, Papillion | 23.0% | 6.4 / 0.9 | |
| Arizona Phoenix metro | 16.9% | 0.0 / 0.0 | |
| Virginia Loudoun County | 14.7% | 3.8 / 0.0 | |
| Georgia Atlanta metro | 9.8% | 0.0 / 0.0 | |
| Ohio New Albany, Columbus | 0.0% | 0.0 / 0.0 | |
| Iowa Council Bluffs, Des Moines | 0.0% | 0.0 / 0.0 | |
| New York the NYISO control region | 0.0% | 0.0 / 0.0 | |
| California Santa Clara, the CAISO control region | 0.0% | 0.0 / 0.0 |
Power and water are what a training cluster consumes. This is what it costs, and it is the one part of the story American public companies are legally obliged to write down. A company can decline to say how large its next model is. It cannot decline to tell its shareholders it has committed to buildings full of racks, or to sign a decade of electricity without the contract appearing in a filing.
data centers
1622
filings / 30d
2026-09-15 to 2026-10-15
AWAITING BASELINE20 of 30
efts.sec.gov full-text search; a count of matching filings, not of dollars, and it carries EDGAR’s own filing calendar — 10-K season lifts every phrase
power purchase agreement
305
filings / 90d
2026-07-17 to 2026-10-15
AWAITING BASELINE20 of 30
efts.sec.gov full-text search; PPAs are signed by every heavy industry, and nothing in a phrase count separates a datacentre’s from a smelter’s
data center
154
documents / 180d
2026-04-18 to 2026-10-15
65th percentile of 234 points (2022-04-16 to 2026-10-08)
LIVE
the noisiest source in this index: "data center" also matches the National Climatic Data Center, federal facility consolidation notices and every agency building with the words in its name
Three states, kept apart everywhere they appear. LIVE the feed answered and there is enough baseline to score it. AWAITING BASELINE the feed answered, the number is real and printed, and there is not yet enough history to say where it sits — it is in no average on this page. DARK the fetch failed; the reason is printed under the row and nothing is imputed in its place. Merging the second into the third would claim an outage that is not happening, which is the most common quiet lie in this whole category.
| Source | State | Value | Unit | Score | Pctile | n | Baseline |
|---|---|---|---|---|---|---|---|
CAISO overnight floor
caiso-baseload · CAISO · California |
AWAITING BASELINE | 20,351 | MW | — | — | 21 | accumulated |
| 21 of 30 points needed before this source can be scored. The reading above is real and is printed; it is simply not yet scored, and it is excluded from every average on this page. | |||||||
ERCOT overnight floor
ercot-baseload · ERCOT · Texas |
AWAITING BASELINE | 52,405 | MW | — | — | 22 | accumulated |
| 22 of 30 points needed before this source can be scored. The reading above is real and is printed; it is simply not yet scored, and it is excluded from every average on this page. | |||||||
ERCOT headroom used
ercot-tightness · ERCOT · Texas |
AWAITING BASELINE | 75.80 | % of committed capacity | — | — | 22 | accumulated |
| 22 of 30 points needed before this source can be scored. The reading above is real and is printed; it is simply not yet scored, and it is excluded from every average on this page. | |||||||
NYISO overnight floor
nyiso-baseload · NYISO · New York |
AWAITING BASELINE | 13,172 | MW | — | — | 22 | accumulated |
| 22 of 30 points needed before this source can be scored. The reading above is real and is printed; it is simply not yet scored, and it is excluded from every average on this page. | |||||||
Severe drought, ten cluster states
usdm-drought · ten states, weekly |
LIVE | 17.44 | % of area in D2+ | 47.0 | 40.6 | 260 | feed 2021-10-12 to 2026-09-29 |
Streamflow below normal, nine clusters
usgs-water-deficit · nine gauges, seven states |
LIVE | -2.39 | % below normal, median of 9 | 37.2 | 15.4 | 1094 | feed 2023-10-15 to 2026-10-12 |
Federal Register documents saying "data center"
fedreg-datacenter · US federal government |
LIVE | 154.00 | documents / 180d | 54.9 | 65.1 | 234 | feed 2022-04-16 to 2026-10-08 |
SEC filings saying "data centers"
sec-datacenter · US public companies |
AWAITING BASELINE | 1622 | filings / 30d | — | — | 20 | accumulated |
| 20 of 30 points needed before this source can be scored. The reading above is real and is printed; it is simply not yet scored, and it is excluded from every average on this page. | |||||||
SEC filings saying "power purchase agreement"
sec-power-contracts · US public companies |
AWAITING BASELINE | 305.00 | filings / 90d | — | — | 20 | accumulated |
| 20 of 30 points needed before this source can be scored. The reading above is real and is printed; it is simply not yet scored, and it is excluded from every average on this page. | |||||||
The difference between an instrument and a conspiracy chart is that the instrument publishes this list.
Eight candidate sources were requested against their live endpoints and left out. They are published here, rather than dropped quietly, because a list of what was tried is the only evidence a reader has that the included list was chosen and not just assembled from whatever returned 200.
EIA open data — hourly demand by balancing authority
api.eia.gov/v2 requires an api_key on every request checked 2026-09-23
Excluded. The key is free and instant, which would be tolerable if it were obtainable in an unattended build — it is not, and a key committed to this repository is a key on the public internet. This is the single biggest gap on the page: EIA-930 covers every balancing authority including PJM and MISO and would close six corridors at once.
PJM Data Miner 2 — Northern Virginia and Ohio
api.pjm.com HTTP 401 on every path tried checked 2026-09-23
Excluded. Requires a registered subscription key. This is why the largest datacentre cluster on earth has no grid cell on this page.
MISO real-time data broker — Iowa and Nebraska
misoenergy.org HTTP 200 carrying {"error": "no data"} on getfuelmix, gettotalload and getWindForecast; empty body on three others checked 2026-09-23
Excluded. A 200 with an error body is exactly the shape that becomes a silent zero, and there is nothing behind it to read.
US water-use statistics — the operator’s "water usage"
USGS national water-use programme published annually checked 2026-09-23
Excluded as a tempo series, and this is the exclusion most worth stating. An index of activity cannot be built on a number that changes once a year; it would be a step function with a multi-year lag dressed up as a live reading. Instantaneous streamflow IS sub-daily and is used instead — but it measures the water in the river, never the water a datacentre drew out of it. Those are different quantities and this page does not blur them.
poweroutage.us — the operator’s "power outages"
poweroutage.us API HTTP 401 checked 2026-09-23
Excluded. No free structured tier, and no other free machine-readable live outage feed for the United States was found. ERCOT headroom is the nearest honest substitute and it is not the same thing: it measures the margin BEFORE an outage, not the outage.
ERCOT todays-outlook.json
ercot.com HTTP 403 checked 2026-09-23
Excluded; supply-demand.json carries the same quantities and is used instead.
CAISO dated archive — /outlook/<YYYYMMDD>/demand.csv
caiso.com HTTP 404 on two dates checked 2026-09-23
No archive exists. This is the cause of the documented six-hour CAISO hole.
Vast.ai GPU spot pricing
vast.ai works checked 2026-09-23
Deliberately not duplicated. It is already live in the main index as the compute pillar’s GPU source. Running one series in two indices would make them look like two independent witnesses agreeing, which is the single easiest way to fake corroboration.
S = 50 + 12.5z, clamped to 0–100. This is the same code the
main SIREN index uses, imported rather than reimplemented.0.7 * mean(live pillars) + 0.3 * max(live pillars) over live pillars. The
max term is why one pillar at the top of its record moves the number even when the others
are ordinary.Two of the main index’s six anti-flap layers are deliberately absent here and are named rather than skipped: the dual-window dwell needs a dense observation history this index does not have — half its sources move once a day and one moves once a week — and the four-hour post-change lock is subsumed by the longer minimum interval.
Every number on this page is in
the JSON, including each source’s
baseline span, its percentile, and the raw reading behind it. The last build fired the rule
none.
50.4 of 100 sits in SUBSTRATE 4 · STEADY. That is a count of how loaded the substrate is, not a claim about what anyone is building on it. 3 of 9 keyless public feeds scored.
Nothing on this page measures datacentre power or datacentre water. No public feed separates datacentre load from any other industrial load. What is measured here is the condition of the substrate those datacentres are being built into.
9 places where the American build-out actually is, and what each of the three pillars can and cannot see there.
Every grid has a daily minimum — the hour when air conditioning, offices and traffic have all gone home. What is still drawing power at four in the morning is the load that never stops. The overnight floor is the cleanest public proxy for always-on industrial demand that exists without a utility contract.
Cooling a datacentre consumes water, and nobody publishes the consumption. What is published, free and keyless, is the state of the water the clusters have to draw on: the flow in the river beside them.
The same nine USGS gauges beside named datacentre clusters, measured against each gauge's long-run median for that calendar date. Flow is rainfall and reservoir operation, not datacentre draw.
Share of each state's area in D2 — severe drought — or worse. The Drought Monitor is a weekly expert assessment, not an instrument reading.
Power and water are what a training cluster consumes. This is what it costs, and it is the one part of the story American public companies are legally obliged to write down.
Three states, kept apart everywhere they appear: live, awaiting-baseline, and dark. Merging awaiting into dark would claim an outage that is not happening.
The difference between an instrument and a conspiracy chart is that the instrument publishes this list. It cannot separate a datacentre from a smelter, and it cannot measure water consumption.
Each source returns one scalar where higher always means more activity, then normalises against that source's baseline. This index does not feed the main SIREN number.
Candidate sources were requested against their live endpoints and left out. They are published here, rather than dropped quietly, because a list of what was tried is the only evidence a reader has that the included list was chosen.
Nothing on this page measures datacentre power or datacentre water. No public feed separates datacentre load from any other industrial load, and no arithmetic downstream can recover a split the input never contained. What is measured here is the condition of the substrate those datacentres are being built into.
This index does not feed the main SIREN number and never has. Its sources are not in the frozen reference distribution, so it is a separate instrument on a separate question.
SUBSTRATE 4 does not mean the grid is in trouble. It means the composite of these readings sits in that band of the distribution this index has observed. A young index has a short record, and a short record makes every reading look more ordinary than it may be.
No. Activity tempo, not probability of harm. Watts is an infrastructure tempo reading — not a probability of harm and not a forecast.
Dallas · Austin · San Antonio. Grid: ERCOT. What each of the three pillars can and cannot see there.
Loudoun County · Data Center Alley. Grid: PJM. What each of the three pillars can and cannot see there.
New Albany · Columbus. Grid: PJM. What each of the three pillars can and cannot see there.
Council Bluffs · Omaha. Grid: MISO / SPP. What each of the three pillars can and cannot see there.
Atlanta metro. Grid: Southern Co.. What each of the three pillars can and cannot see there.
Phoenix metro. Grid: APS / SRP. What each of the three pillars can and cannot see there.
The Dalles · Hillsboro. Grid: BPA. What each of the three pillars can and cannot see there.
NYISO control region · reference. Grid: NYISO (reference). What each of the three pillars can and cannot see there.
Santa Clara · CAISO control region · reference. Grid: CAISO (reference). What each of the three pillars can and cannot see there.
Search-shaped sibling: How many datacentres has SIREN mapped in the United States?.
SIREN is free and carries no display ads. Keep it running: Support SIREN on Ko-fi →