Seattle Freezes New Data Centers: A Closer Look at Why and What Comes Next

On June 9, 2026, Seattle's City Council voted unanimously to stop approving new large data centers within the city for up to 18 months. The vote was unanimous — a sign that council members across the political spectrum agreed this pause was necessary.

The freeze, officially called ordinance CB 121214, targets data centers — the massive warehouse-like buildings that house computer servers and networking gear for cloud services, artificial intelligence, and the internet. Specifically, it applies to facilities that need 10 megawatts of electricity or more (think: enough power to supply roughly 8,000 homes). Smaller operations stay unaffected. The ban lasts one year automatically, and the council can vote to extend it by another six months if needed.

How We Got Here

The move did not come out of nowhere. Council members introduced the moratorium proposal in late April 2026, asking for detailed studies on how data centers would affect the city's power grid, the local economy, and public health. The law required a public hearing within 60 days — which meant the whole process, from introduction to vote, took roughly six weeks.

Seattle's Mayor, Bruce Wilson, was moving in parallel. On April 18, 2026, he announced that the city had already stopped approving new data center projects. Two weeks later, his office outlined initial steps to address the issue, coordinating with the Council before any official vote.

A companion resolution, Res 32204, filed alongside the moratorium, lays out the city's thinking on data center definitions and broader policy goals. The Council also formally acknowledged that data centers could strain the city's electrical grid — a finding that ensures grid capacity becomes a central focus of the upcoming studies.

What the Studies Will Examine

The Council is treating the moratorium not as a permanent ban, but as a pause to gather evidence. The city will conduct studies on three fronts: environmental impact, infrastructure demands, and economic effects.

The infrastructure question is the most concrete. Data centers running at 10 megawatts or higher draw enormous amounts of electricity, and Seattle's power grid was designed with the assumption that the region had cheap, abundant hydroelectric power. That assumption is changing. The newest workloads — AI systems that need to run continuously at high intensity — consume electricity far faster than the grid's headroom can accommodate.

Environmental concerns are intertwined with the power question. While Washington State generates some of the cleanest electricity in the country (thanks to dams), data centers need massive amounts of water for cooling. They either use cooling towers that evaporate water into the air, or they pump cool water directly through servers. In a region where water is already stretched between cities, farms, and ecosystems, this matters.

The economic question is more complicated to answer. Data centers do create construction jobs and bring tax revenue. But once built, they do not need many workers to operate — a handful of technicians per facility rather than hundreds of employees. Whether the money and jobs they generate justify the commitment of power and water resources is precisely the kind of question a careful study can help answer.

This Pattern Has Appeared Before

Anyone who has watched technology infrastructure over the past 25 years will recognize what is happening. The same sequence played out during the first big wave of data center building in the late 1990s and 2000s. Cities and states initially welcomed data centers as economic development, then grew concerned about power and water demands, and finally took action — either clawing back tax incentives or restricting where facilities could be built. Northern Virginia, which now has more data center capacity than anywhere else on Earth, is now struggling with grid constraints it did not plan for when it was actively recruiting the industry two decades ago. Seattle is moving faster, acting before the problem becomes entrenched.

Questions About the Boundary

The 10-megawatt threshold is worth understanding. The ordinance defines a data center as a facility primarily used to house, operate, or rent out servers and networking equipment — a definition broad enough to capture AI training facilities, large cloud computing clusters, and standard hyperscale data centers. Edge deployments and smaller enterprise data centers that use less than 10 megawatts would not be frozen.

The definitional language in Res 32204 gives the Council flexibility to widen or narrow the rules before the moratorium expires. If the impact studies find that many smaller facilities, added together, create the same grid strain as one massive one, the Council can adjust the threshold downward. Operators planning smaller-scale projects in Seattle should watch the study findings closely.

What Happens to Demand Elsewhere

The moratorium applies only to Seattle itself, not the broader region. The Pacific Northwest has other data center hubs — the Columbia River corridor and Quincy, Washington — that have attracted significant investment because of cheap hydropower and available land. Demand that Seattle turns away will likely shift to these other areas or to Eastern Washington, where some companies are already building large facilities.

For any companies that were already working through Seattle's permit process when the council voted, the timing matters. Washington State's emergency ordinances typically go into effect immediately when the mayor signs them, rather than waiting 30 days as normal laws do. That means the freeze applies right away, with no grandfathering period for projects still in the pipeline.

The unanimous Council vote, the Mayor's coordinated action, and the formal study mandate all point to Seattle intending to use these 12 to 18 months to build a thoughtful, evidence-based policy rather than simply kicking the decision down the road. Whether that policy eventually welcomes data centers back under new conditions — or effectively closes the city's doors to the industry — will depend on what the studies reveal and how seriously the Council weighs the trade-offs between economic gain and infrastructure burden. That answer will take time, but the process to find it has now officially begun.