An independent, deterministic record of where AI infrastructure is, who operates it, what it draws, and what no instrument can reach. Every reading carries its error bar. No figure on this page is produced by a language model.
AI runs in buildings full of computers. Those buildings need enormous amounts of electricity, and electricity leaves paperwork: permits, grid filings, pollution reports, equipment orders. WAPR collects that paperwork every day and publishes what it adds up to.
Each panel below is one instrument. It shows a number, where the number came from, how fresh it is, and what is wrong with it. The coloured tag in the corner says whether the instrument is working: Live is current, Degraded is stale or uncalibrated, Blind means it cannot see right now, Contested means the method itself is disputed. Panels also list their own known defects: FATAL breaks the method, BIAS skews the answer, GAP means something needed is missing.
If an instrument cannot see, this page says so rather than printing a zero — a quiet instrument is not the same as a quiet world. Numbers carry an drawn to scale: a wide bar means do not trust the number. No number on this page is produced or estimated by an AI.
WAPR is operated by BATECH LLC, a private company. It is not run for profit, carries no advertising, and nobody pays to appear here or to be left out. It is also young: several of the daily records below began collecting in September 2026. Where a panel speaks about change over time it is either drawing on an older published figure — labelled a — or saying plainly that it cannot yet. A long-run record has to start somewhere. How this is kept independent →
In plain terms: one overall reading, from 5 (nothing open) down to 1 (critical). It moves only when a verified finding is entered in the registers — never because a scan noticed something unusual. The lines beside it say what is currently open at each rung of the , and how much of the instrument is currently .
| Level | Rule — first match wins, top down |
|---|---|
| 1 · CRITICAL | Any open L3-published finding of an uncontrolled agent, or a verified multi-channel critical event (two independent channels agreeing, per MV-1.8 and the TRACKER §0 escalation rule), ≤ 90 days old. |
| 2 · SEVERE | ≥ 1 open L2 candidate on a critical claim, or ≥ 2 open L2 candidates of any kind. |
| 3 · ELEVATED | ≥ 1 open L2 candidate. |
| 4 · ATTENTION | ≥ 1 open L1 watchlist item, OR more than 2 panels blind — the index degrades when the instrument cannot see. Blindness is never "all clear". |
| 5 · NOMINAL | None of the above. |
Ladder terms are protocol MV-1.8: L1 = watchlist (one channel at p<0.01, or a BH survivor) · L2 = candidate (two independent channels at p<0.01, in band, controls flat) · L3 = published (the full gate, registration hash cited). The registers live in the repository at data/wci/, are hand-curated with provenance, and scan output never enters them directly (MV-1.0). Watchlist deltas could at most separate level 5 from 4, and only with a null-expected count beside them (MV-1.1); no null model exists yet — the archive is too young — so today they are shown as context and move nothing.
An instrument, not a report. Panels set their own lamp from data age. A wide means do not trust the number. A panel says blind rather than zero when it cannot see.
In plain terms: these sentences are produced by fixed rules applied to the numbers below — not by someone deciding what to say, and not by an AI. When a rule’s inputs are missing, its sentence simply does not appear.
How many AI models are being published to the public model-sharing site this instrument tracks, and how many of those are packaged to run on ordinary hardware.
Quantization mechanically precedes deployment. A safety-stripped repository is a census dimension, not an accusation — abliteration is legal and published.
huggingface.co/api/models · keyless ·Whether the major AI companies still publish the address lists that let a website tell their web-crawling apart from an impostor.
OpenAI's Web Bot Auth directory recomputes exp = now + 7 days on every request. Hashing the document reports a key rotation on every fetch, always falsely. The detector hashes key material only. The 7-day window is not documented publicly.
5 operators · WBA JWKS + crawler CIDRs ·Data-centre buildings that volunteer mappers have recorded, and how often the map also records who operates them.
A declared frame, not a world total. Open the plot →
OpenStreetMap telecom=data_center · ODbL ·Virginia’s regulator publishes air-pollution figures for individual data-centre sites — figures the . At a site whose permit has not changed, a rise means its ran.
The regulator already tracks the fuel — as NOx. Reported tonnes are fuel burned × emission factor, filed under penalty. Year-over-year NOx at a site with no permit change is "did the generators run." The emissions table holds the current year only and overwrites itself; this record began 2026-09-14.
VA DEQ ArcGIS layers 294 / 298 / table 292 · keyless ·Campuses that intend to generate their own electricity instead of drawing it from the public grid. Announced capacity is what a permit or filing carries; operating capacity is what a document says is actually running — and where a document says a plant runs but none states the megawatts, the reading is left blank rather than written as zero.
Electricity demand at night across ’s Virginia territory, against the same months six years earlier. Night is when ordinary demand falls away and steady industrial loads stand out.
Jul–Dec 2019 vs 2025. 15 of 18 other PJM sub-regions flat or negative — a built-in placebo set.
Power plants to the , and how much of that capacity has actually signed a .
Large new electricity users approved to connect in Texas, against how much of that demand ever showed up.
57% of approved load has never appeared. Phantom demand — the same project shopped across utilities — quantified from the operator's own figures. Grid planners cannot currently separate real from speculative.
Can a data centre’s waste heat be seen from space? Largely no. This panel records why the method fails, so that no claim gets built on it.
Still worth measuring: within-site change over time. Differencing a site against itself cancels the offset, and the waste-heat quadrant — night-positive, day-neutral — is discriminating. The off-site claim is bounded at 0.079 K; the on-site change is not.
Landsat C2 ST_B10 · ECOSTRESS via LP DAACTurning of power into a count of AI chips. The arithmetic is possible; the answer would be wrong by a factor of several — so the reason is published instead of the number.
A facility estimated at 30 MW has a 95% interval of 8 to 118 MW. Published only as a screening bound with the interval attached — never as a point estimate, never without this list beside it.
error propagation · wapr-system-design · interconnection + disclosure + Nvidia denominatorWhat kinds of power station are actually running on the grid where each company's data centres sit. This is the electricity physically flowing in those places, not what a company says it buys.
Unusual conditions happening right now near the mapped sites. These are things happening to the sites, not things the sites cause.
Deliberately not scored. This list is never totted up into a severity total — many things happening at once is what ordinary chance looks like, and level-setting belongs to the WAPR Condition rules alone.
Ireland is the only country that officially counts data-centre electricity as its own category. Everywhere else the sector disappears into general business use.
People expect a data centre to warm the land around it, and to see that heat spreading on a map. Drawn at true size, there is no plume to draw — this panel is the honest version of that picture.
Before a tall crane goes up, someone has to file a public notice with the aviation authority — so the paperwork appears months before a building does.
A watchlist signal, not a finding. It suggests where to look and settles nothing on its own.
Things nobody can currently measure, each with the precise reason it is out of reach and the search that proves it.
The most defensible output of this instrument is a precise account of what no instrument can reach. It cannot be scooped by a commercial database, because the commercial databases are part of the finding.
| What is unknowable | Mechanism | Evidence |
|---|---|---|
| Data centre emissions, US federal | GHGRP Subpart C excludes "emergency generators and emergency equipment" from the source category, so the sector never crosses the reporting threshold. Virginia publishes CO₂e per site anyway — at state level. | 40 CFR 98.30(b)(2), verbatim GHGRP NAICS 518210 → 6 facilities all 6 are flare-gas sites (re-run 2026-09-14) VA DEQ table 292 → CO2E present |
| Data centre water withdrawal | No federal category has ever existed and none is coming: USGS county compilations ended 2015, the modeled replacement (2000–2020 only) has no DC class, and municipally supplied sites are absorbed into "public supply". Exception, one region: Loudoun Water meters its data-centre class — 4.5 MGD avg / 10.9 MGD peak-day 2024, disclosed via ICPRB's five-yearly Potomac study. | USGS NWIS + ScienceBase reanalysis → no DC class ICPRB WMA study 2025 §6.2 (re-run 2026-09-14) |
| Per-site load, Texas | Aggregated by the operator's stated policy "to protect Customer data". | ERCOT → zone totals only |
| Hyperscaler site water | Of the four hyperscalers checked, one publishes it. Owned sites only, consumption only, PDF only, layout changes annually. | Google → 36 cities, 2024 AWS · Meta · MSFT → none |
| Discharge volumes | The operator states most sites are not metered for it. | Microsoft, in writing |
| Runaway agent behaviour | Account-scoped by construction. No cross-account read path exists at any price. | AWS docs, verbatim: "same account and Region" |
| Self-directed AI loose on the web | No confirmed public case; no scanner would find one. A capable system trying not to be found would not leave a homepage. | Palisade: 24,111,509 → 3 |