Datacenter regulatory-trace changes as of September 1, 2026
As of 2026-09-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-08-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.
Sites that define this dated page
| Announced site | Prior score | Current score | Observed trace |
|---|---|---|---|
| AWS Richmond County Campus (Energy Way Industrial Park) Amazon · Hamlet, Richmond County, NC | 30 | 50 | No bounded trace observed |
| AWS Ridgeland (Costas property) Campus Amazon · Ridgeland, MS | 30 | 20 | FAA cases within 8.0km x7; active construction (4 crane cases) |
| Google Council Bluffs (East) Google · Council Bluffs, IA | 30 | 20 | FAA cases within 8.0km x2; active construction (1 crane cases) |
| Google Fort Wayne Data Center Google · Fort Wayne, IN | 30 | 20 | FAA cases within 8.0km x3; active construction (2 crane cases) |
| Google Kansas City (East) Google · Kansas City, MO | 20 | 30 | FAA cases within 8.0km x2 |
| Google Lincoln Data Center Google · Lincoln, NE | 50 | 30 | FAA cases within 8.0km x1 |
| Google Omaha Data Center Google · Omaha, NE | 20 | 30 | FAA cases within 8.0km x1 |
| Microsoft Fairwater Atlanta Microsoft · Fayetteville/South Fulton, GA | 50 | 30 | FAA cases within 8.0km x1 |
| Nebius/DataOne Vineland Campus Nebius/DataOne · Vineland, Cumberland County, NJ | 50 | 30 | FAA cases within 8.0km x1 |
| xAI Colossus 1 (former Electrolux plant) xAI · Memphis, TN | 50 | 20 | FAA cases within 8.0km x2; active construction (2 crane cases) |
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 September 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 September 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.
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