Seattle City Council Passes Emergency Data Center Moratorium, Freezing Large-Load Facilities for Up to 18 Months

Seattle's City Council voted unanimously on 9 June 2026 to adopt emergency legislation imposing a moratorium on new data centers within city limits, alongside a companion policy framework designed to govern what comes next. The vote was unanimous — a signal of cross-council consensus on a question that has been building since at least early spring.

The moratorium, formalised as ordinance CB 121214, applies to facilities meeting the ordinance's definition of a data center — primarily those used for housing, operation, or co-location of computer and networking equipment — and specifically targets large-load installations with a nameplate capacity of 10 megawatts or greater. Smaller-footprint deployments below that threshold are not captured by the ban. The initial freeze runs for 365 days, with a City Council vote able to extend it by an additional six months, for a theoretical maximum of 18 months before the policy must either be made permanent, revised, or allowed to lapse.

The Legislative Record Leading Here

The moratorium did not arrive without forewarning. Councilmembers introduced the proposal in late April 2026, calling at the same time for comprehensive impact studies covering infrastructure strain, economic consequences, and public health effects. The legislation required a public hearing within 60 days of the proposal — a procedural guardrail that compressed the timeline between introduction and enactment to roughly six weeks.

Mayor Bruce Wilson had already moved on parallel tracks. A statement issued on 18 April 2026 confirmed that the City of Seattle had not, at that point, authorised or permitted any new data centers — effectively a pre-emptive administrative hold. Within two weeks, the Mayor's office had identified initial steps for action, aligning executive and legislative branches before any formal vote.

Resolution Res 32204, filed in early June alongside the ordinance, addresses data center definitions and broader policy intent. It sits in the record as the policy layer above the blunter instrument of the moratorium itself. Separately, the Council has formally recognised the potential long-term impacts of data centers on electrical grid capacity — a finding that puts grid strain squarely within the scope of the upcoming studies.

What the Impact Studies Must Cover

The legislation frames the moratorium as a pause for evidence-gathering rather than an outright prohibition. The Council proposed a resolution requiring the city to study the environmental, infrastructure, and economic impacts of data centers — a three-vector mandate that maps neatly onto the concerns that have driven opposition to data center proliferation in cities across the United States and Europe.

The infrastructure vector is the most technically specific. Large-load facilities at the 10 MW threshold and above place non-trivial demands on transmission and distribution infrastructure. In a Pacific Northwest grid that has historically benefited from abundant, low-cost hydroelectric capacity, the arithmetic is shifting: AI inference workloads, with their high and relatively constant power draw, are filling capacity headroom that once made Seattle-region power costs attractive to cloud operators.

The environmental vector intersects with that grid question. Washington State's electricity supply is among the cleanest in the continental United States by carbon intensity, but data center water consumption for cooling — whether through evaporative towers or direct liquid cooling systems — is a separate and locally sensitive concern, given the region's competing demands on water resources.

The economic vector is arguably the most contested. Data centers generate construction jobs and tax revenues, but their operational employment footprint is modest relative to the capital invested. Whether the net economic contribution justifies the infrastructure and grid commitments is exactly the kind of question that a structured impact study can surface — and that a 365-day window creates space to answer.

A Pattern the Industry Has Seen Before

Those of us who have tracked technology infrastructure buildouts since the colocation boom of the late 1990s will recognise the dynamic. Cities and states cycled through an almost identical sequence during the first hyperscale build-out wave: initial enthusiasm as data centers were treated as high-value economic development, followed by rising unease about power and water commitments, followed by local government action — sometimes incentive clawbacks, sometimes outright zoning restrictions. Northern Virginia, which now hosts the densest concentration of data center capacity on the planet, is itself beginning to confront grid constraints it did not anticipate when it was aggressively courting the industry two decades ago. Seattle is compressing that cycle, acting before the footprint becomes difficult to unwind.

Scope and Ambiguity in the Definition

The 10 MW threshold deserves scrutiny from operators and developers. The ordinance's definition of a data center as a facility used primarily for housing, operation, or co-location of computer and networking equipment is broad by design. Facilities that host AI training clusters, large-scale inference deployments, or hyperscale cloud availability zones would almost certainly clear the 10 MW floor without difficulty. Edge deployments, campus data centers, and enterprise-scale facilities in the sub-10 MW range appear to fall outside the moratorium's reach for now — but the policy studies may revisit that boundary.

Worth flagging: the definitional scope left in Res 32204 gives the Council room to widen or narrow the aperture before the moratorium expires. Operators planning sub-10 MW deployments in Seattle should monitor the study outputs closely. If the impact findings point to cumulative load effects — where many smaller facilities aggregate to the same grid stress as one large one — the Council has the legislative tools to respond.

Implications for the Regional Market

Seattle sits within a broader Pacific Northwest data center market that includes the Columbia River corridor and the Quincy, Washington hub — areas that have absorbed significant hyperscale investment precisely because of hydropower availability and land costs. The moratorium applies only within Seattle city limits. Demand displaced by the ban does not disappear; it is more likely to accelerate permitting conversations in adjacent jurisdictions or in the Eastern Washington markets already absorbing cloud-scale load.

For operators already in Seattle's permitting pipeline as of the Council's action, the emergency designation of the legislation is consequential. Emergency ordinances in Washington State typically take effect immediately upon mayoral signature rather than after the standard 30-day period, meaning the freeze applies without a grandfathering window for projects not yet permitted.

The unanimous Council vote, the parallel mayoral action, and the structured study mandate together suggest that Seattle intends to use the 12-to-18-month window to build a durable, evidence-based framework rather than simply defer a difficult political decision. Whether the resulting policy encourages a return of development under tighter conditions — or effectively makes Seattle's city limits a non-starter for hyperscale investment — depends entirely on what the impact studies find and how the Council weighs the trade-offs. That answer will not come quickly, but the process to reach it is now formally under way.