Datacenter regulatory-trace changes as of July 10, 2026
As of 2026-07-10, 12 of the 57 tracked announced sites had a changed phantom score, or entered the baseline, in this published comparison.
This is the archive baseline, so all tracked sites establish their first comparison point. The score reports how much trace was observed in bounded public air-permit and FAA airspace sources. A higher score is a diligence prompt, not a verdict about whether a datacenter will be built.
Sites that define this dated page
| Announced site | Prior score | Current score | Observed trace |
|---|---|---|---|
| Cipher Mining Barber Lake (Fluidstack/Google-backed) Cipher Mining/Fluidstack · Colorado City, Mitchell County, TX | baseline | 65 | TX site with zero regulatory trace |
| Meta El Paso Data Center Meta · El Paso, TX | baseline | 65 | TX site with zero regulatory trace |
| poolside Project Horizon (Longfellow Ranch) poolside · Pecos County, TX | baseline | 65 | TX site with zero regulatory trace |
| TeraWulf Abernathy Campus (Fluidstack JV; reported Anthropic TX site) TeraWulf/Fluidstack (Google-backed) · Abernathy, Hale County, TX | baseline | 65 | TX site with zero regulatory trace |
| AWS Project Rainier Amazon (AWS, for Anthropic) · New Carlisle, IN | baseline | 50 | No bounded trace observed |
| AWS Susquehanna Nuclear Campus (former Cumulus) Amazon · Salem Township, Luzerne County, PA | baseline | 50 | No bounded trace observed |
| CoreWeave Marble (Core Scientific site) CoreWeave/Core Scientific · Marble, Cherokee County, NC | baseline | 50 | No bounded trace observed |
| Google Columbus Data Center Google · Columbus, OH | baseline | 50 | No bounded trace observed |
| Google Council Bluffs (East) Google · Council Bluffs, IA | baseline | 50 | No bounded trace observed |
| Google Fort Wayne Data Center Google · Fort Wayne, IN | baseline | 50 | No bounded trace observed |
| Google Kansas City (East) Google · Kansas City, MO | baseline | 50 | No bounded trace observed |
| Google Lincoln Data Center Google · Lincoln, NE | baseline | 50 | No bounded trace observed |
Rows not shown retained the same score and are intentionally omitted. That keeps this page about what changed instead of reproducing a 57-row table every day. Score bands are heuristic and depend on coverage: TCEQ pending applications cover Texas, while the FAA case layer is national. An issued permit, a local permit outside the collected sources, or construction that needs no sampled FAA filing can all be absent from this view.
Method, source, and content seal
The July 10, 2026 comparison is derived from public records published by TCEQ and the FAA Part 77 archive. The scorer joins those bounded records to publicly announced site locations. Name-token matches that are merely contextual do not count as direct permit evidence. Distance matches use the fixed radius shown above. The method does not infer power, capacity, financing, completion, or operator intent.
The July 10, 2026 source artifact reproduced its declared SHA-256 seal before this response was rendered. The seal excludes only the machine-local database path; dates, source counts, site rows, scores, and reasons remain bound.
Need the decision brief, not just the public evidence?
The archive is the proof layer. The Datacenter Materialization Watch turns the same two signals into a fixed monthly diligence deliverable for site-selection and infrastructure teams. Terms and coverage are on the archive hub.
See the watch offer