The Washington data-center argument is no longer just about whether a new building should receive a permit. It is about who underwrites the infrastructure that makes AI possible when a proposed customer changes its plans. October 4 demonstrations gave that question a statewide political campaign, while Seattle’s existing restrictions supplied a narrower, already enacted example.
Washington AI Resistance organized at least 19 demonstrations across communities including Seattle, Spokane, Olympia, Tacoma, Moses Lake, Walla Walla, Cle Elum and Bainbridge Island. That count does not mean 19 large crowds: the protest report described roughly a dozen people near Seattle’s John Lewis Memorial Bridge. They wanted lawmakers to pause large data-center development when the legislature returned in January 2027. This was a demand, not a statewide ban already in force.
A local pause is not a statewide shutdown
The coalition brought together objections over electricity, water, pollution, privacy, surveillance, utility bills and concentrated technology-company power. Seattle protester Faith Mathison wanted regulation before large companies set the terms themselves. Spokane organizer Brittany Anderson questioned whether households would finance transmission upgrades serving future data centers. These are related concerns, but not a single technical objection that one efficiency pledge can settle.
Lawmakers had already attempted a broader response. House Bill 2515 passed the state House but stalled in the Senate in the 2026 session. Co-sponsor Gerry Pollet, a Seattle Democrat, supported a moratorium; Senate majority leader Jamie Pedersen stopped short of endorsing one, while expecting substantial requirements for new AI data centers. A pause, negotiated regulation and continuing local patchwork remained different political outcomes.
Seattle’s council unanimously adopted its one-year emergency moratorium on June 9. The city announcement describes stopping the filing, processing and approval of applications for covered new or expanded facilities. The relevant large-load threshold was at least 10 MW. This was not an order to switch off existing centers, prohibit AI services or stop projects outside city limits.
The city had about 30 smaller data centers, none near the scale of the proposals prompting the debate. Skagit and Snohomish counties also adopted temporary restrictions, alongside actions in Renton, Spokane, Burien, Federal Way and Marysville. Those separate measures do not establish identical rules across Washington.
What the 369 MW figure does—and does not—show
Four companies approached Seattle City Light about five large facilities whose combined maximum proposed demand reached 369 MW. Officials compared that scale with supplying approximately 300,000 homes. It was a planning comparison, not measured daily consumption or proof that all five projects would open and run at full load simultaneously.
Earlier reporting said two companies subsequently withdrew proposals. That means two companies, not necessarily exactly two facilities. Withdrawals reduced the immediate pipeline without removing the underlying risk: a utility must plan substations, transmission, generation procurement and upgrades before every prospective customer is operating. Auditors describe hyperscale facilities as commonly requiring 20–100 MW, a contextual range rather than the definition of Seattle’s 10 MW rule.
Industry supporters argue that large customers broaden utility revenue and can help fund shared infrastructure. That benefit depends on the terms. When demand is delayed, reduced or canceled, households and small businesses can inherit investment costs unless contracts specify otherwise. A sustainability statement does not say who pays for an unused substation.
Dedicated tariffs, minimum payments, exit charges, collateral and construction contributions are possible ways to assign that exposure. Seattle City Light was developing a large-load policy; the mayor’s plan sought to prevent infrastructure, power-purchase and electricity-use costs from shifting to existing customers. Developing a policy is not evidence that every proposed safeguard was already enforceable.
Water, workers and the relocation problem
The city’s planned permanent framework covered grid capacity, water, rates, land use, health, employment and emergency management. Direct cooling water and indirect water used in electricity generation are different impacts. Both vary with climate, cooling technology, workload and design. Backup generators add site-specific questions about fuel, testing schedules and local emissions.
Disclosure therefore needs a connection to permits, operating standards, tariffs and consequences for noncompliance. Building size alone cannot determine water use; publishing a number alone cannot allocate liability. Councilmember Debora Juarez presented the pause as compatible with continued AI and data-center activity, while council president Joy Hollingsworth emphasized understanding lasting consequences before approvals.
Three Amazon employees publicly urged regulation in council testimony, proposing additional renewable generation, storage, water and power transparency, and worker participation in safety oversight. Their proposals were not Amazon’s formal policy. Amazon said at that time it had no plans to build within Seattle, respected employees’ opinions and intended responsible community operations.
The regional question remains even if a company has no city project. Restricting one jurisdiction can move demand, pollution and infrastructure pressure into another rather than eliminate them. That supports the case for statewide minimum standards, without making local protections pointless. The October protest report said Amazon and Microsoft did not immediately comment; it did not establish their later positions.
The tax review challenges a simple jobs-for-subsidy bargain
Washington introduced its rural sales-and-use-tax preference in 2010, then a 2022 urban pilot for King, Pierce and Snohomish counties. A preliminary 2026 legislative review estimated urban beneficiaries saved $42.4 million in fiscal years 2023–2026. Owners claimed four exemption certificates and tenants six. Ten certificates are not ten newly built data centers.
Beneficiaries reported 53 permanent family-wage jobs and nearly 300 temporary construction jobs, with property-tax revenue and likely utility-tax revenue as additional contributions. Yet no new urban data center was built through the preference: owner exemptions supported refurbishing existing facilities. The nationwide AI investment surge had not translated into qualifying new urban construction under this program.
The auditor recommended allowing the urban preference to expire, considering it unlikely to meet its objectives under revised rules. That recommendation was not itself an enacted termination. From July 1, 2026, refurbishments and replacement server equipment stopped qualifying under both rural and urban provisions, leaving new construction as the remaining qualifying activity.
The HB 2515 Senate report records the wider bargaining: utility reporting and planning, labor requirements and a new exemption in a qualifying eastern Washington county. Supporters wanted large users to bear new-infrastructure costs; critics considered the framework overly prescriptive and potentially harmful to other large electricity customers. The amended bill stalled, rather than resolving those differences.
The next test is an enforceable allocation of risk
Rules also need usable boundaries. The urban tax preference used at least 20,000 square feet of server space and 1.5 MW of available power, not Seattle’s 10 MW threshold. Tax eligibility, zoning, environmental review and electricity rates serve different purposes. Mixed facilities run ordinary cloud applications, storage, databases and video alongside AI training or inference; an “AI” label is not a reliable load definition.
A statewide framework would need to address aggregated loads, related facilities and phased construction rather than invite project splitting. Demand response—reducing or shifting consumption during grid stress—can help, but reliability requirements and workload schedules limit interruptibility. Neither universal shutdown-on-command assumptions nor unsupported exemptions answer the engineering question.
A moratorium can create rulemaking time while also delaying projects capable of meeting strong standards and diverting investment. The federal proposal introduced by Bernie Sanders and Alexandria Ocasio-Cortez in March was a proposal, considered unlikely to advance, not a nationwide prohibition. State and local authorities already had powers over rates, land use, taxes, environmental review and planning.
Three subsequent tests matter: the substance of 2027 legislation, Seattle’s permanent framework before its pause expires, and binding customer contracts. Those contracts should make clean-energy additions, connection funding, water disclosure, unused reserved capacity and ultimate facility ownership intelligible and enforceable. For AI buyers, chips and capital alone cannot guarantee capacity: permits, grid commitments and public consent can constrain deployment just as materially.
The original reporting also circulated through an original news aggregation entry; that entry is an aggregation route, not a direct publisher page.