Ep. 032 - 300 Datacenter Bans, 6 Projects Delayed: Moratoriums Explained (Datacenter, Energy)

Summary

SemiAnalysis breaks down the surge in data-center moratoriums and argues that the practical impact is far smaller than the headline count suggests. Maya explains that most restrictions are local, short-lived zoning or permitting pauses meant to buy time for new rules and manage political opposition, not to stop existing builds. The team’s database of 400+ local instruments across 17 states, when mapped against a 3,500-entry U.S. pipeline, leaves only 3 campuses meaningfully exposed after legal and project-specific filters. They also compare state actions: New York’s statewide permit pause is the most material, but it still mostly delays speculative capacity rather than causing cancellations, while Pennsylvania and Oregon are framed as narrower permitting changes with limited market impact. The discussion closes with a strategic takeaway for developers: grid-connected sites are becoming riskier, behind-the-meter power is more attractive, and durable legislative action matters more than revocable executive orders.

Notes

• A data-center moratorium is a temporary legal pause that freezes approval, permitting, and new construction without affecting existing facilities.
• Most U.S. moratoriums are local at the county, city, or township level.
• Recent state-level action has mostly taken the form of executive orders rather than legislation.
• The main policy motive is to buy time to write data-center-specific zoning rules.
• Moratoriums also function as a low-cost political response to local opposition.
• The show describes the current wave as a recent phenomenon, with more than 300 local governments voting to pause data centers.
• Enacted moratoriums peaked visibly in May and June, while July remained high.
• The database starts with 400+ local instruments across 17 U.S. states and tracks their full lifecycle.
• The dataset includes proposed, enacted, rejected, expired, and lifted actions.
• Permanent bans and zoning-code restrictions were included because they constrain development similarly to moratoriums.
• The local restriction map was tested against a U.S. pipeline of about 3,500 project entries.
• The first screen found about 77 campuses above 20 MW inside restricted jurisdictions.
• Those 77 campuses represented about 20 GW in total.
• A second screen checks whether the rule reaches the parcel, whether carveouts apply, and whether the project already has other required permits or approvals.
• Projects can also fall out if they can be redesigned around the rule or use separate permitting pathways.
• After the full screen, 74 of 77 campuses dropped out and only 3 remained.
• The three materially affected projects are AWS near Commercial Point in Ohio, North Point in Pennsylvania, and a CoreSite expansion in Colorado.
• Most live restrictions are preemptive: around 80% have no capacity under construction or attached.
• That is why the practical impact is small: many target speculative capacity rather than active builds.
• The hosts argue the headline moratorium count overstates actual market disruption.
• Grid-connected sites create political and utility-risk exposure because developers are seen as raising local power prices.
• Behind-the-meter projects avoid direct grid interaction and therefore reduce the risk of local electricity-price backlash.
• Behind-the-meter siting is becoming more attractive, especially in Texas.
• Texas offers more behind-the-meter options because of gas, land, and permissive fuel-burn conditions.
• The team says it is not worried about the near-term U.S. buildout trajectory from these restrictions.
• A legislature-passed moratorium would be more durable than an executive order.
• New York’s statewide moratorium pauses state environmental permits for new data centers of 50 MW or more until July 2027.
• The New York rule gives the state time to write a generic environmental impact statement.
• It touches about 1.4 GW of plant capacity, all of it scheduled for 2028 or later.
• The estimated delay from New York is roughly 800 MW for 6–10 months.
• The New York policy is framed as delay, not cancellation, because cancellations tend to involve highly speculative projects.
• Pennsylvania’s order is a conditional permitting regime, not a moratorium or ban.
• Pennsylvania DEP is told not to process permit applications until requirements are met and local approval is secured.
• Pennsylvania also removes data-center proposals from fast-track permitting.
• Pennsylvania prohibits NDAs for data-center projects, increasing disclosure pressure.
• The Pennsylvania regime mostly lengthens pre-permit diligence and hits speculative projects hardest.
• Oregon paused data-center projects on state-owned land for one year.
• The Oregon order is said to have no impact on the forecast.
• NDAs with local governments are common in hyperscaler projects and often keep communities ignorant until late in the process.
• The speaker says city councils should not be put under NDA because they owe transparency to constituents.
• AWS is cited as having used NDAs multiple times, including an Ireland project that later triggered backlash.
• The hosts argue for more transparency rather than hiding projects behind NDAs.
• The speakers say planning documents and meeting materials are often unpublished, so local social media can be a source of project intelligence.
• Local meetings are often overwhelmingly hostile to data centers.
• Opposition is described as BANANA rather than NIMBY: build absolutely nothing anywhere near anyone.
• Opponents often focus on power and water rather than AI ideology.
• Public opinion can be net positive on AI while net negative on data centers.
• People often see data centers as boring light-industrial buildings rather than a major public hazard.