State data-center bills have stopped sounding like welcome mats. MultiState says more than 300 data-center bills were filed across more than 30 states in the first six weeks of 2026, a shift from incentive policy toward oversight as the energy demands become visible. [1] The number matters because it shows this is no longer one county fighting one campus. It is a state-house pattern.

The paper's June 14 feature on data centers moving from tax breaks to ratepayer dockets argued that AI infrastructure costs reach households through tariffs, riders, and cost-shift rules. Monday's narrower record shows the mechanisms: moratoriums, tax-credit cuts, demand response, special rates, and protections against shifting grid costs to ordinary customers. The politics have moved from ribbon cuttings to rate design.

MultiState lists New York, South Dakota, and Oklahoma moratorium proposals. New York's bills would halt construction for up to three years while regulators adopt rules to minimize utility-rate impacts. South Dakota would pause hyperscale expansion for one year, and Oklahoma would pause data centers over 100 MW until November 2029 while studying water, utility-rate, and property-value effects. [1] Those proposals are blunt instruments, but blunt instruments appear when lawmakers think the market arrived faster than the rulebook.

The incentive era is under review too. MultiState points to Virginia proposals to narrow tax incentives, Georgia legislation that would eliminate tax credits including data-center credits, and Oklahoma legislation ending incentives for data centers not operating by January 1, 2027. [1] That is the second stage of the argument. States that once treated the data center as a trophy project now have to ask whether tax forgiveness still makes sense when the load is large, the water demand is visible, and the private customer can affect public bills.

The utility design is the heart of the matter. Arizona would require rules preventing new data-center grid-connection costs from shifting onto other retail customers. Maryland would encourage large-load demand response. At least 18 states have introduced more than 30 bills creating special rate classes for large energy users, and Alabama would condition permits on infrastructure-payment and statewide ratepayer-benefit findings. [1] That is not anti-technology language. It is utility language: who pays for the line, who pays for the backup, who pays when forecasts are wrong, and who gets protected when one giant customer changes the load curve.

FERC's large-load docket supplies the federal rhyme. The commission says it will act by June 2026 on reforms for large-load interconnection, naming data centers and other significant electrical loads as part of the proceeding. [2] The federal question is not identical to the state fight, but it points in the same direction. Large electrical loads need queue rules, cost allocation, and timelines that can survive the speed of AI buildout.

MSM often writes these fights locally because the bills are local. X writes ratepayer anger because the monthly bill is where abstractions become household math. The state bill map says the same thing in statutory prose: subsidy is giving way to pricing.

-- DARA OSEI, London