The data center fight in Pilesgrove Township, New Jersey
As of September 27, 2026, Pilesgrove Township, New Jersey has a data center moratorium in force (action taken Listed Aug 2026).
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
Listed among the 69 New Jersey municipalities with an enacted data center ban on the Pinelands Preservation Alliance's tracker, last updated Aug 27, 2026. The adoption date and ordinance number are not given in that source -- confirm with the municipal clerk before citing this row at a hearing.
SourceRoundup
read 2026-08-30
An expiry date is the earliest a pause could have ended — extensions are common, so confirm with the clerk before citing it.
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.
Nearby in New Jersey
- Woodstown (2 mi) — Enactedterm not documented
- Harrison Township (6 mi) — Enactedno end date — permanent
- Mannington Township (6 mi) — Enactedterm not documented
- Upper Pittsgrove Township (6 mi) — Enactedterm not documented
- Logan Township (9 mi) — Enactedno end date — permanent
- Oldmans Township (9 mi) — Enactedterm not documented
- East Greenwich Township (10 mi) — Enactedterm not documented
- Quinton Township (10 mi) — Enactedno end date — permanent
All 74 tracked actions in New Jersey 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.