The data center fight in Monroe Township (Gloucester Co.), New Jersey
Monroe Township (Gloucester Co.) has an active data center moratorium on this tracker. 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
Two ordinances banning data centers township-wide. Hexa Builders is suing for more than $300M in federal court — the test case for whether a small municipality can absorb the litigation risk of a ban
Source
read 2026-08-04
An expiry date is the earliest a pause could have ended — extensions are common, so confirm with the clerk before citing it.
Recent news
- Monroe Township has requested the dismissal of a $300 million lawsuit against its data center ban
- Monroe Township faces $300M lawsuit after banning AI data centers
- Developer suing Monroe Township for $300M over ban on data centers
Automated news aggregation, not human-verified — follow each link to the original outlet. Part of the story tracker, 3 headlines 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 New Jersey.
- Model CBA clauses — copy-paste language communities have actually won.
- New Jersey briefing — rates, grid carbon, PUC contacts, and every fight in the state.
Elsewhere in New Jersey
- Phillipsburg — Enacted
- Warren — Enacted
- Jersey City — Proposed
- Howell Township — Proposed
- Andover Township — Proposed
- Summit — Enacted
- Cherry Hill — Enacted
- Medford — Enacted
- Mansfield Township (Burlington Co.) — Enacted
- Chesterfield — Enacted
- Berkeley Heights — Enacted
- East Brunswick — Proposed
- Waterford Township (Camden Co.) — Enacted
- Plainfield — Proposed
- North Plainfield — Proposed
- Red Bank — Enacted
- Asbury Park — Enacted
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.