The data center fight in Cary, North Carolina
As of September 27, 2026, Cary, North Carolina has a data center moratorium in force (action taken August 28, 2026; documented end date 2028-02-28).
Status is derived, not stored — a pause with a documented end date flips to Expired on its own — and the source is right next to the claim.
Status today
18-month moratorium on all data center development, unanimously approved. Studies power demand, water consumption, noise/vibration, site design. Longest moratorium in the Triangle.
SourceNews
read 2026-09-11
An expiry date is the earliest a pause could have ended — extensions are common, so confirm with the clerk before citing it.
Recent news
Automated news aggregation, not human-verified — follow each link to the original outlet. Part of the story tracker, 1 headline archived.
What to do next
- Questions to ask at the hearing — force specific answers onto the record.
- Estimate the impact — electricity, water, and rate pressure for any facility size in North Carolina.
- Model CBA clauses — copy-paste language communities have actually won.
- North Carolina briefing — rates, grid carbon, PUC contacts, and every fight in the state.
Nearby in North Carolina
- Apex (6 mi) — Enactedexpires 2027-04-27
- Holly Springs (10 mi) — Enactedexpires 2027-06-16
- Durham (15 mi) — Enactedexpires 2027-06-15
- Durham County (18 mi) — Enactedexpires 2027-05-18
- Wendell (23 mi) — Enactedexpires 2026-12-31
- Orange County (27 mi) — Enactedexpires 2027-04-21
- Chatham County (28 mi) — Enactedexpires 2027-02-11
- Harnett County (29 mi) — Enactedexpires 2027-05-03
All 44 tracked actions in North Carolina are on the state page.
As of August 2026 · changes weekly — re-check before citing
Illustrative rather than exhaustive — dozens of localities churn weekly, and this tracks the ones we have read a source for. **Each row carries its own provenance.** Rows showing a verification date link to the ordinance, the enacting body's own page, or a datable report of the vote, and were read on that date. Rows marked *unverified* came from bulk compilation and have not been checked against a primary source — the locality, the year, and the status may all be off. Verify one of those with the town clerk before citing it as precedent. **Expiry is derived, not asserted.** A row with a documented end date flips to *Expired* on its own once that date passes. A time-limited moratorium whose start date was never documented keeps showing as enacted — that is a known gap, not a claim that it is still in force. Moratoriums are also routinely extended, so an expiry date is the earliest it could have ended, not proof that it did.
Part of the U.S. data center moratorium tracker — open data, CC BY 4.0.