A California county extends its data centre moratorium to the maximum its own ordinance allows, then votes to oppose the facilities in writing
Siting is the last decision a local government still controls over a class of infrastructure that is otherwise assembled above its head, and a 45 day pause extended to nearly a year is a county buying time to write rules before the rules are written for it. The register has now recorded three of these in a month, in New Hampshire, in Mississauga and here, which is the point: the pattern is not a local planning dispute but a broad reassertion of municipal authority over where compute is allowed to consume water and electricity. The tension is honest and worth stating. This is decentralised power being used to block, not to build, and the water argument in Tulare County is doing more work than the grid argument.
The Tulare County Board of Supervisors has extended its moratorium on new data centre development in the unincorporated parts of the county by a further 10 months and 15 days, reported to be the longest extension available under the urgency ordinance without starting again. The vote was unanimous. In a separate item the same day the board adopted, three votes to two, a letter opposing data centre construction within the county's boundaries; supervisors Valero and Townsend dissented.
The pause being extended began on 18 August 2026, when the board adopted a 45 day moratorium described at the time as extendable up to one year. The county's case was not that data centres are objectionable in themselves but that its zoning could not assess them: the demands such a facility places on water, electricity and public infrastructure were not contemplated by the existing standards, and the ordinance recited a threat to public health, safety and welfare. Water did more of the argument than power. Tulare County sits under groundwater pumping restrictions, and a facility that consumes water continuously is a different proposition there than in a wet county. Noise, continuous operation and cumulative impact on communities that already carry infrastructure burdens were also cited. A memorandum of understanding between the Tulare County Fairgrounds and GlobalStack USA, covering shipping container sized computing units at fairgrounds, sits somewhere in the background of the dispute.
This is now the third moratorium of its kind in this register inside a month, after a statewide proposal in New Hampshire and an interim control by law in Mississauga. Three is a pattern rather than three planning stories, and the pattern is the reassertion of local siting authority over an infrastructure class that is otherwise assembled without reference to the places it lands in. Compute is being built at the scale of a national industrial policy and permitted at the scale of a county planning department, and the county planning department is the only body in that sentence a resident can address in person. In Tulare County residents used that access to ask for a permanent ban, which the board did not give them.
It is worth being straight about the shape of the story. A moratorium is decentralised power used to stop something, not to build anything, and a publication that argues for control at the edge inherits both halves of that. The defensible reading is narrower and more interesting than either a victory or a nimby complaint: the county is not claiming the right to decide whether AI gets built, only the right to write the standards under which it gets built here, and it has bought itself most of a year to do so.
What is not established needs saying, because the county's own record could not be read. The county website returned a 403 and two local outlets refused the request, so the date of the vote rests on a syndicated report that says Tuesday, September 23, when 22 September was the Tuesday; other summaries say the 22nd and give the count as five to nothing. No ordinance number was obtained for either the original or the extension, and the claim that 10 months and 15 days is the statutory maximum is reported rather than checked against the code. One summary said the opposition letter carries an exception for enterprise facilities; the report that was actually read does not mention any exception, so it is not asserted here.
Public comments
Loading…