SitePathInsights › The data-center backlash hits PJM: four New Jersey towns move to ban or freeze data centers, with York County (SC) and Wilson County (TN) close behind
SitePath Research · Field Note · June 28, 2026

The data-center backlash hits PJM: four New Jersey towns move to ban or freeze data centers, with York County (SC) and Wilson County (TN) close behind

A coordinated wave of local data-center restrictions surfaced in SitePath's news layer this cycle. The trigger headline (GovTech, 2026-06-22, in SitePath's news index) was "Data Center Bans Emerge in 4 More New Jersey Communities." The…

Every claim sourced to a primary document · SitePath Intelligence editorial desk

What changed

A coordinated wave of local data-center restrictions surfaced in SitePath's news layer this cycle. The trigger headline (GovTech, 2026-06-22, in SitePath's news index) was "Data Center Bans Emerge in 4 More New Jersey Communities." The meeting-researcher pass identified and sourced the four municipalities to primary records — and the picture is sharper than the headline:

All four sit in PJM; Warren Township is confirmed in PSE&G electric territory, the others in JCP&L (FirstEnergy) — still PJM load. The GovTech "bans" framing is loose: only Warren and Red Bank are enacted bans; Asbury Park is a resolution and Sayreville is a moratorium not yet adopted.

Two more counties outside NJ are on the same track:

Why it matters

New Jersey is a PJM state. A four-town wave there — two outright bans already on the books, one local freeze, one 18-month moratorium pending — is the clearest sign yet that the Virginia-style data-center siting backlash is now a region-wide PJM phenomenon, not a Virginia exception. The pattern is also explicitly statewide-minded: Asbury Park and Red Bank didn't just protect their own borders, they passed resolutions pressing Trenton (and Governor Sherrill) for a statewide moratorium. SitePath's own SitePath's data-center dataset already carries a state-rollup note that a NJ data-center bill "passed both chambers (Assembly 55-18), awaits Governor Sherrill signature" — consistent with, but not yet confirmation of, a statewide measure.

The opposition is load-specific, not anti-growth. York County, SC froze data centers in the same session it advanced a $1.5B biopharmaceutical project — a county sorting large loads by water draw, power demand, and tax terms rather than rejecting industry. That is the same calculus driving Virginia's data-center politics, and it travels.

For the dataset, this is a freshness gap to close. The curated SitePath's data-center dataset has not caught up: the relevant NJ counties still read status: "No Specific Activity", York County (SC) still reads "No confirmed county-specific data center ordinance" (lastActionDate 2025-11-10), and Wilson County (TN) is absent from the counties array. The tracked counters (moratoriumActive 22, banEnacted 1, townshipMoratorium 10) were unchanged day-over-day. The news and meeting layers are ahead of the structured layer — these confirmed actions should be promoted into the county records and counters (Warren Township alone is a clean new banEnacted).

Recommended next steps (human)

  1. Promote the confirmed actions into SitePath's data-center dataset county records and increment counters — Warren Township → banEnacted, Red Bank → ban, Asbury Park/Sayreville → moratorium/township-moratorium, York SC + Wilson TN → proposed/active per stage.
  2. Resolve NJ jurisdiction tagging to the municipal level (records currently sit at county FIPS).
  3. Confirm the NJ statewide bill status before any "state permitting rule change" claim is made publicly.
  4. Calendar the 2026-07-20 Sayreville and Wilson County votes and the York County July 13 final hearing for follow-up.

Published from the SitePath editorial desk on June 28, 2026. Claims are traced to primary documents and to records already in the SitePath dataset; source links appear inline. Material the source review could not confirm has been withheld from this page rather than published with a caveat — see methodology for how SitePath sources and scores what it publishes.

← All SitePath insights