Datacenter regulatory-trace changes as of August 1, 2026

As of 2026-08-01, 10 of the 57 tracked announced sites had a changed phantom score, or entered the baseline, in this published comparison.

Compared with the immediately preceding sealed source report dated 2026-07-31. 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.

719permit applications in the source snapshot
25,895non-terminal FAA cases observed nationally
8.0 kmfixed airspace join radius

Sites that define this dated page

Announced sitePrior scoreCurrent scoreObserved trace
AWS Madison County Mega Site
Amazon · Canton, Madison County, MS
3050No bounded trace observed
AWS Richmond County Campus (Energy Way Industrial Park)
Amazon · Hamlet, Richmond County, NC
3050No bounded trace observed
AWS Ridgeland (Costas property) Campus
Amazon · Ridgeland, MS
2030FAA cases within 8.0km x1
Google Council Bluffs (East)
Google · Council Bluffs, IA
5030FAA cases within 8.0km x1
Google Fort Wayne Data Center
Google · Fort Wayne, IN
5030FAA cases within 8.0km x1
Google Kansas City (East)
Google · Kansas City, MO
5030FAA cases within 8.0km x1
Google Midlothian Data Center
Google · Midlothian, TX
2030FAA cases within 8.0km x1
Google West Memphis Campus (Groot LLC)
Google · West Memphis, AR
2030FAA cases within 8.0km x1
Meta Jeffersonville Data Center
Meta · Jeffersonville, IN
3020FAA cases within 8.0km x11; active construction (1 crane cases)
QTS Richmond (White Oak) Campus
QTS · Sandston, Henrico County, VA
3050No 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 August 1, 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 August 1, 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.

SHA-256: 1a1cbea03ce29160b987ca7737a80db20b6ad328baf5fc5ccb944ad67c509da0

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