jain.com — data centers, connectivity and security, analyzed daily

Tag: utility rates

  • Up to $1.8B in Grid Upgrades: California’s AI Data Center Deal Is About Who Pays First

    Up to $1.8B in Grid Upgrades: California’s AI Data Center Deal Is About Who Pays First

    TL;DR · 30-second read

    The Short Version

    California lawmakers have agreed on new rules for data centers, the giant warehouses of computers that run artificial intelligence and everyday online services.

    The central idea: companies building them would pay upfront for the power lines and grid upgrades their electricity demands, instead of spreading that cost across everyone’s utility bills. State grid planners estimate those upgrades in one major utility’s territory could cost up to $1.8 billion.

    The deal comes as nearly three in four Californians say they oppose data centers in their own communities, and several cities have banned or paused them.

    California lawmakers reached a compromise on Friday, Aug. 28, on legislation regulating the electricity use of data centers, the Los Angeles Times reported. The package, from Sen. Steve Padilla (D-Chula Vista) and Assemblymember Rick Chavez Zbur (D-Los Angeles), directs the California Public Utilities Commission (CPUC) to create special rates and updated rules for data centers, including how the cost of new power and infrastructure upgrades is charged.

    The final package includes the approach from Padilla’s SB 886, sponsored by The Utility Reform Network (TURN), requiring data centers to pay up front for broader grid upgrades needed to serve their demand. TURN cited a California grid operator transmission plan projecting up to $1.8 billion in upgrade costs, including transmission lines, driven by data center demand in PG&E’s service territory, where most current and proposed California data centers are concentrated.

    Executive Summary

    California has chosen a cost-allocation answer to data center growth rather than a moratorium. The deal does not cap how many facilities can be built. It changes who pays for the grid capacity they need, and when. Under the upfront-payment approach carried over from SB 886, a data center’s share of transmission and distribution upgrades becomes part of the developer’s capital budget instead of a cost recovered later from the general customer base.

    That matters because the numbers are no longer small. The California Energy Commission expects data center electricity use, now about 2% of statewide demand, to double within ten years, and the grid operator’s plan puts potential data-center-driven upgrades in PG&E territory at up to $1.8 billion. Much of the practical detail, including rate design, thresholds and timing, is left to the CPUC. Meanwhile, a provision allowing utilities to strike their own agreements with data centers before the CPUC finishes its rules creates an interim window that developers and critics will both watch closely.

    For AI infrastructure planners, the signal is mixed. The state has set a clear principle that growth pays for itself, which may reduce political risk over time. It has also added cost in a market where high power prices, scarce land and limits on gas-fired generators already hold most projects below 100 megawatts.

    The Fight Was Never About Whether, But Who Pays First

    The core dispute in Sacramento was not whether California should host data centers. It was how much they should pay for power and grid infrastructure, and whether the Legislature or the CPUC should decide. The two options on the table amount to two different financing models. When a utility builds new substations and transmission lines to serve a large new customer, the cost can either be added to the utility’s rate base and recovered over years from all customers, or charged to the customer that triggered it before the work proceeds. SB 886’s approach, which made it into the final package, leans toward the second model.

    The scale comes from the grid operator’s transmission plan, which projects up to $1.8 billion in upgrade costs from data center demand in PG&E’s territory. Moving even a meaningful portion of that onto project budgets changes a developer’s math in three ways. More capital is needed before a building is energized. Grid upgrades shift from a utility’s problem to a line item that competes with land and equipment. And a site’s value depends more heavily on how much grid headroom already exists nearby. TURN’s Matthew Freedman framed the result as keeping data center costs from “being foisted on other customers.” PG&E, which favored a less stringent approach, warned that SB 886 would “risk higher costs for customers and delay critical infrastructure,” which is a reminder that upfront payment also affects how quickly utilities can build ahead of demand.

    The groups most directly affected are developers targeting PG&E territory, which covers most of the state’s data center pipeline including the San José market, and household ratepayers, whose exposure to data-center-driven upgrades is what the deal is designed to limit. How much protection they actually get depends on rate design the CPUC has not yet written.

    A Market Already Built Small

    California enters this regime with an unusual profile. Its data centers are typically under 100 megawatts, well short of the 500-megawatt-plus AI campuses rising in other states, because of high electricity costs and state limits on gas-powered generators. The 49.5-megawatt facility under construction in Vernon is representative. For operators already constrained this way, an upfront grid charge adds to a cost stack that the Data Center Coalition’s Khara Boender says is uncompetitive: she noted that dozens of states offer data center exemptions and California does not, and called added regulation “another signal that the state is a more challenging place for data center development.”

    That argument deserves a fair hearing, and so does the counterpoint. The Coalition opposed both bills for “singling out” one type of power user. Yet the premise of cost-causation pricing is that the customer creating a large, identifiable load pays for it, and data centers are unusually concentrated loads. The strongest case on the industry’s side is not that the principle is wrong. It is that the details, such as how “broader” upgrades are apportioned among several projects on a shared line, could make early movers pay for capacity later arrivals use. That question now sits with the CPUC.

    The Interim Window and the Self-Supply Gap

    Two late amendments drew criticism from Monica Embrey of the Affordable Energy Campaign. The first allows a utility to reach its own agreement with a data center in the period before the state finalizes its rules. In practice, that creates a window in which terms are negotiated bilaterally rather than set by tariff, and projects that sign during it may lock in arrangements that differ from what the CPUC ultimately adopts. The second is the absence of clean energy requirements for data centers that generate their own power.

    Together these point to where AI campus developers are likely to focus next. If grid-supplied power carries upfront upgrade costs while self-supplied power carries no clean energy obligation, on-site or behind-the-meter supply becomes relatively more attractive, within the limits California already places on gas generators. Whether that tilt is intended, and how regulators will treat it, is one of the more consequential open questions in the package.

    Local Opposition Sets the Ceiling

    State rate rules do not settle the land-use fight playing out city by city. A Public Policy Institute of California poll in July found 73% of residents oppose data centers in their own communities. Monterey Park voters banned them outright in June, at least four other San Gabriel Valley cities have adopted moratoriums, Coachella imposed a permanent ban, and Tulare County adopted a moratorium in August. In San José, the state’s main development hub, residents have pushed for a pause while the city updates its standards.

    Water sits on a parallel track. Newsom vetoed a water-disclosure bill from Assemblymember Diane Papan last year, citing “rigid” reporting requirements, but lawmakers have since approved separate bills requiring energy and water use disclosure. For developers, the combined effect is that a California site now has to clear a cost-allocation test at the utility, a disclosure regime at the state level, and a local political test that some communities have already answered with a no.

    Background

    California has not experienced the wave of very large AI data centers seen in states such as Texas. High power prices, limited land and restrictions on gas-fired backup and primary generation have kept most facilities comparatively small, with San José and the wider PG&E service territory hosting most activity. The CPUC, whose board is appointed by the governor, regulates investor-owned utilities such as PG&E and sets the rates they charge.

    Data center growth has nonetheless become a political issue in the state. Community opposition has produced a local ban in Monterey Park, moratoriums across the San Gabriel Valley, the Coachella Valley and Tulare County, and pushback against a proposed 75-acre project in Imperial Valley. In 2025, Gov. Gavin Newsom vetoed a water-disclosure bill, citing concern about rigid requirements on critical digital infrastructure, which left energy cost allocation as the main legislative battleground in the 2026 session.

    Sources

    Source: California lawmakers reach deal in high-stakes fight over regulating data centers (Los Angeles Times), on the legislative compromise directing the CPUC to set data center electricity rates and upfront grid-upgrade charges.

  • Oregon Approves PGE’s 29.7% Data Center Rate Hike Under Landmark POWER Act

    Oregon Approves PGE’s 29.7% Data Center Rate Hike Under Landmark POWER Act

    Oregon regulators have approved a 29.7% electricity rate increase for data centers served by Portland General Electric (PGE), the state’s largest utility, as reported by Oregon Public Broadcasting on July 6, 2026. The decision is the first major rate action taken under Oregon’s landmark POWER Act, a 2025 law that directed regulators to place large energy users such as data centers into their own rate class so that the costs of serving them are not spread across households and small businesses.

    Executive Summary

    The approval makes Oregon one of the first states to move from debating data-center cost allocation to actually pricing it. Under the POWER Act — passed in 2025 amid rapid data-center load growth and rising residential bills — utilities must charge very large customers rates that reflect the full cost of serving them, including the new generation and transmission their demand triggers. The 29.7% figure now approved for PGE’s data-center class is the concrete output of that mandate.

    Why it matters: electricity has become the gating resource for AI and cloud expansion, and the question of who funds grid upgrades — the data centers driving demand, or all ratepayers — is now the central fight in utility regulation. Oregon has produced a working template, with a specific number attached, that commissions and legislatures in Virginia, Georgia, Ohio, Texas and elsewhere are likely to study closely.

    Who Pays for the AI Buildout Just Got a Concrete Answer

    For most of the past century, utilities spread the cost of new infrastructure across all customers on the theory that everyone benefits from a stronger grid. Data centers broke that logic: a single hyperscale campus can demand as much power as a small city, arriving faster than utilities can build generation and wires. When those costs land in general rates, households effectively subsidize some of the world’s largest companies. Oregon’s POWER Act rejected that outcome by mandating a separate rate class — a distinct pricing category with its own cost-based rates — for large energy users.

    The 29.7% increase is the first hard number to emerge from that framework. It represents a regulator’s judgment, tested through a formal rate proceeding, of what cost-causation pricing for data centers actually looks like at PGE. Whether one views the number as fair depends on the underlying cost studies, which the reporting summarized here does not detail — but the structural shift is unambiguous: growth-driven costs are being assigned to the customers driving the growth.

    A Template Other States Will Study — and Contest

    Regulators across the country are wrestling with the same problem, mostly through case-by-case special contracts with individual data-center customers. Oregon instead wrote the principle into statute and applied it class-wide, which offers predictability but less flexibility. Expect both sides of the national debate to cite this decision: consumer advocates as proof that ratepayer protection is achievable, and data-center developers as evidence of rising regulatory risk in some markets.

    The competitive question is real. Oregon, particularly the Portland-Hillsboro area that PGE serves, built a significant data-center cluster on the strength of relatively inexpensive Northwest power and long-standing tax incentives. A nearly 30% jump in the power line-item — often the largest operating cost of a modern facility — changes site-selection math. States hungry for data-center investment may market themselves against Oregon’s approach; states worried about residential bills may copy it. Either way, the era of uniform, geography-blind data-center power pricing is ending.

    The Economics Cut Both Ways

    For utilities, a dedicated large-load class is double-edged. It insulates existing customers and reduces political backlash against growth, but it also raises the price of the very load that funds new investment. If data-center operators respond by self-supplying — building on-site generation, contracting directly with power producers, or siting behind other utilities — PGE could face slower load growth than planned, and the fixed costs of any already-committed infrastructure would need a home.

    For operators, the decision reinforces a trend already visible across the industry: power strategy is now a first-order business function, not a facilities detail. Companies that locked in long-term supply arrangements, invested in efficiency, or diversified their geographic footprint are better positioned than those that assumed grid power would stay cheap and socialized. The Oregon decision does not end data-center growth in the state — but it prices that growth honestly, and honest prices change behavior.

    Background

    Oregon became a data-center destination over the past two decades thanks to relatively inexpensive Pacific Northwest power, a mild climate, strong fiber routes, and generous local tax incentives — attracting major cloud and internet companies to clusters around Hillsboro in PGE territory and along the Columbia River. As AI workloads accelerated demand in the 2020s, utilities projected unprecedented load growth while residential electric bills climbed, fueling a political backlash over who should fund grid expansion.

    The POWER Act, passed in 2025, was Oregon’s answer: separate very large energy users into their own rate class and charge them the full cost of serving them. The rate decision reported here is the first major application of that law, moving the cost-allocation debate from principle to an approved price.

    Source: Oregon approves PGE’s 29.7% rate hike for data centers under landmark law — Oregon Public Broadcasting report on the first major rate decision under Oregon’s POWER Act, published July 6, 2026.

  • Ohio Would Halve a $1.6B Data Center Break. The Harder AI Fight Is Who Pays for the Grid

    Ohio Would Halve a $1.6B Data Center Break. The Harder AI Fight Is Who Pays for the Grid

    TL;DR · 30-second read

    The Short Version

    Ohio lawmakers want to shrink a tax break for data centers, the giant warehouses of computers that run artificial intelligence and online services. The break cost the state roughly $1.6 billion last year. The bill would cut it in half.

    The bigger fight is over electricity bills. These buildings use so much power that new power lines and power plants have to be built. Manufacturers and environmental groups warn that ordinary households could end up paying part of that cost.

    Senators aimed to pass the bill within a day.

    Ohio state Sen. Brian Chavez unveiled a sweeping data center bill on Tuesday, June 9, attaching a long list of policy changes to a measure originally written only to study the issue, the Ohio Capital Journal reported. The proposal would cut the state’s discretionary sales and use tax exemption for data centers from 100% to 50%, or 75% for projects that build on brownfields and bring their own power. The exemption has grown to roughly $1.6 billion in the last year. The bill would also cap local property tax abatements at 50%, end data center access to Ohio’s 30-year mega project job creation grant, require data centers to track and report water use, and direct the Public Utilities Commission of Ohio (PUCO) to create a separate electricity rate class for data centers.

    The Senate Energy Committee was scheduled to advance the bill Wednesday morning, June 10, with a full Senate vote planned for later the same day.

    Executive Summary

    Ohio’s bill is one of the broadest state-level rewrites of data center policy so far. It covers tax incentives, nondisclosure agreements, water monitoring, utility billing, and a new surety bond meant to protect local governments. The tax provisions are the most concrete part. A roughly $1.6 billion incentive would be cut in half, with a larger 75% break reserved for projects on brownfields (previously developed, often contaminated land) that supply their own electricity.

    The provision that drew the sharpest testimony was the proposed data center rate class. It is modeled on the tariff PUCO approved for AEP Ohio last year, which the Ohio Manufacturers’ Association is now challenging in the Ohio Supreme Court. The underlying question is the one now running through every state served by PJM Interconnection, the regional grid operator: when AI-era data centers drive new transmission, distribution and generation spending, who ends up paying for it? PJM plans a backstop auction in September to secure 15 gigawatts of new generation. It has warned that without state rules, those costs could fall on other consumers, including residential customers.

    With a committee vote and a floor vote planned within about a day of introduction, the chance to refine the rate-class language before the Senate acts was limited.

    Tax Policy That Doubles as Power Policy

    The headline change is a 50% cut to the sales and use tax exemption. The more revealing detail is the exception. Projects keep a 75% break only if they build on brownfields and bring their own power. That condition ties Ohio’s largest data center incentive to a developer’s grid footprint as well as its capital spending. In practice, the state would be paying a premium for sites that reuse industrial land and lean less on utility-supplied electricity.

    Other provisions point the same way. Capping local property tax abatements at 50% and removing access to the 30-year mega project job creation grant both reduce the long-term public subsidy a single campus can collect. Together, these changes suggest Ohio is trying to stay open to data center investment while no longer competing mainly on how much tax it will forgo. Developers already planning Ohio sites will need to revisit their project economics. Those able to secure their own generation gain a relative advantage. The bill does not define what counts as bringing their own power, and that definition will matter.

    The Harder Fight Is the Rate Class

    The tax changes drew relatively little objection in testimony. The utility billing provision did not. The bill directs PUCO to create a data center rate class that assigns generation, distribution and transmission costs to data centers, similar to AEP Ohio’s existing data center tariff. The Ohio Manufacturers’ Association, already challenging that tariff in court, opposed extending the model statewide. Its energy consultant, John Seryak, described one project in AES Ohio’s territory that would need roughly $230 million in supplemental grid equipment. He said that once the cost is financed over 40 years with return on equity and interest, it comes to about $850 million, and the tariff would recover only $300 million of it. These are the association’s estimates, not audited figures. But the mechanism is plain. If a rate class spreads a project’s costs over years and collects less than the full lifetime cost, the gap has to be paid by someone else on the system.

    Seryak raised a second concern about the minimum monthly demand payments these tariffs impose. Minimum payments are generally meant to ensure a large customer covers the capacity built for it. He argued they could also inflate utilities’ load forecasts, pushing them to plan for more capacity whose cost is then spread across all ratepayers. They could also weaken a data center’s incentive to use power efficiently. The Ohio Environmental Council Action Fund raised a related gap. Nolan Rutschilling asked lawmakers to add explicit language telling PUCO how to handle PJM’s September backstop auction for 15 gigawatts of new generation. He said the large-load tariff might cover it, but the bill should make sure it does. The affected parties are clear. Manufacturers and households pay if costs leak out of the rate class. Developers pay more if it is written tightly. Utilities have to forecast and build against whatever the final design encourages.

    Water, NDAs and Local Leverage

    On water, the bill directs the Ohio EPA to develop a water quality testing plan and report any anomalies. Data centers would have to track and report their water use and adopt conservation practices, including closed-loop cooling, which recirculates coolant rather than continually drawing fresh water. This gives regulators data they currently lack. It does not set usage caps.

    The nondisclosure agreement provision drew criticism from both parties. The bill states that an NDA cannot prohibit or limit the release of a public record. Sen. Bill DeMora, D-Columbus, said this “does nothing to stop NDAs,” because it does not ban them. Sen. Jerry Cirino, R-Kirtland, worried from the other direction that the bill could hurt data centers’ ability to negotiate with local governments. The proposed surety bond is the most unusual local protection. It would equal the average salary of all of a data center’s workers over ten years, which Chavez described as “financial insurance” for affected communities. Save Ohio Parks asked for some carbon-free energy requirements and pointed to diesel backup generators as a pollution concern. The bill as introduced does not include such a requirement.

    Speed Leaves the Details Unsettled

    Chavez’s timeline, with a floor vote potentially one day after introduction, means the most contested language faced little revision in the Senate. DeMora warned that “anything the legislature does in a swift amount of time ends up being bad for everybody.” The risk is concentrated in the rate-class provision. The tax percentages are simple numbers. The cost-allocation rules are not, and they would be left largely to PUCO to design while the AEP tariff remains in litigation.

    For the wider PJM region, Ohio’s bill is a sign of where state policy is heading. Incentives are being trimmed and made conditional, while the real policy work moves to utility commissions and tariff design. That is where the costs of AI-driven load growth will actually be divided.

    Background

    Ohio, particularly central Ohio, has become a major destination for large data center campuses. Its utilities, including AEP Ohio and AES Ohio, are part of the PJM Interconnection grid, which covers all or parts of 13 states and Washington, D.C. As AI-driven demand for computing power has grown, PJM and its member states have struggled with how to pay for the transmission lines, substations and power plants needed to serve that load without shifting costs onto existing customers.

    PUCO approved a data center tariff for AEP Ohio last year to assign more of those costs to data centers. The tariff is now under challenge by the Ohio Manufacturers’ Association in the Ohio Supreme Court. Chavez’s bill draws on testimony from the Ohio Senate’s Select Committee on Data Centers and would extend a similar rate-class approach across the state’s utilities.

    Sources

    Source: Ohio lawmakers introduce sweeping new data center legislation (Ohio Capital Journal), covering Sen. Brian Chavez’s bill on data center tax breaks, water use, NDAs and utility rate classes.

  • Seattle’s 369 MW Data Center Freeze Shows Why AI Load Needs Ratepayer Buy-In

    Seattle’s 369 MW Data Center Freeze Shows Why AI Load Needs Ratepayer Buy-In

    TL;DR · 30-second read

    The Short Version

    Seattle’s city council voted unanimously on June 9 to temporarily stop new giant data centers from being built in the city. Data centers are warehouse-sized buildings packed with computers, and the biggest new ones run artificial intelligence.

    Four companies had asked the city’s electric utility to power five of them. Together, those five could draw as much electricity as about 300,000 homes.

    Council members said their main worry is that everyone else’s power bills could rise to cover the cost. The pause gives the city time to study bills, water use and pollution before it makes any permanent decision.

    On June 9, 2026, the Seattle City Council unanimously adopted two measures aimed at large data centers, the council announced on its official blog. Amended Council Bill 121214, sponsored by Councilmember Eddie Lin and Council President Joy Hollingsworth, places an emergency, temporary freeze on siting new data centers while the city conducts impact studies. The freeze covers facilities used primarily for storing and processing digital data that have more than 20 megavolt-amperes (MVA) of power capacity and require uninterruptible power. It can be extended by six months if necessary.

    A companion measure, amended Resolution 32204 sponsored by Councilmember Debora Juarez, sets a policy framework and directs city departments and the Mayor’s Office to analyze how such facilities affect grid capacity, water use, utility rates, land use, local jobs and public health. The votes followed reports in April that four companies had approached Seattle City Light, the city’s electric utility, about five large data centers with a combined maximum demand of 369 megawatts. Mayor Katie B. Wilson said the mayor’s office looks forward to signing the ordinance, which takes effect immediately under its emergency designation. A public hearing is required within 60 days.

    Executive Summary

    Seattle has paused new large data centers after four companies sought 369 megawatts of capacity for five facilities. By the council’s own comparison, that is enough electricity to power about 300,000 homes. The ordinance uses a 20 MVA threshold, which targets large, always-on computing facilities rather than small server rooms. It takes effect immediately, and the council says it can be extended by six months.

    The notable part is the reason. Every official quoted — the two sponsors, the council president and the mayor — cited utility rates or ratepayers. Environmental and water concerns were also named, but the shared argument was cost. The question the council put to developers is not whether the grid can physically deliver the power. It is who pays to deliver it.

    For AI infrastructure developers, the lesson reaches beyond Seattle. Where the people who govern a utility answer to the people who pay its bills, a large new load has to make a persuasive case to those ratepayers. A service request alone may not be enough.

    The Argument That Carried the Vote Was the Power Bill

    The measures passed 9-0, and the officials behind them made a consistent case. Councilmember Lin said large AI data centers are “driving up utility costs for residents and small businesses” and that “Seattleites should not be subsidizing record profits of large corporations from the AI boom.” Council President Hollingsworth said growth must not come “at the expense of residents and ratepayers.” Mayor Wilson cited “the potential impacts of large-load data centers on utility rates.” Air, water and noise concerns appear alongside, but rates are the thread that runs through every statement.

    Here is the mechanism. When a utility has to add substations, transmission lines or new power supply to serve a single very large customer, its rate design decides who pays. If those costs are spread across the whole customer base, households and small businesses carry part of them. If the tariff assigns them to the new load, the developer carries them. Resolution 32204 directs the city to study exactly these questions, grid capacity and utility rates, before any permanent rules are set. In Seattle the utility is City Light. It sits under the same elected council that voted the pause, and Juarez chairs the committee that oversees it. The people deciding whether 369 megawatts gets connected are directly accountable to the people who would share the bill.

    That is why this matters for AI infrastructure. A developer can secure land, chips and a utility service request and still be stopped at the point where the grid-upgrade bill meets ratepayers. The council has not yet shown Seattle-specific evidence that these five projects would raise rates; producing that evidence is the stated purpose of the studies. The vote still establishes the test. A large AI load in this city will have to show residents it will not cost them money. Developers who can answer that question credibly, for example by paying their own grid costs, will be better placed than those who cannot.

    What 369 Megawatts Means for a City Grid

    The five proposed facilities had a combined maximum demand of 369 megawatts, about 74 megawatts each on average. The actual split among them has not been disclosed. Maximum demand is peak draw, not average use. However, large computing facilities tend to run close to their peak around the clock, which makes them attractive customers for utility revenue and demanding ones for utility planning. The council’s comparison to roughly 300,000 homes shows the scale: this is a city-sized block of new demand, requested by four companies in a single round.

    The 20 MVA threshold sets the boundary. Megavolt-amperes measure electrical capacity and, for data center equipment, are close to megawatts. The definition also requires uninterruptible power, meaning battery and backup systems that keep servers running through outages. Together these criteria capture purpose-built, high-density computing sites while leaving smaller office server rooms outside the definition.

    Colocation Stays, Mega-Sites Wait

    Lin drew an explicit line between “mega AI data centers” and the city’s smaller colocation facilities. Colocation facilities are shared buildings where many organizations rent space for their servers, and Lin said Seattle’s support 911 call centers, municipal operations, hospitals, universities and cancer research. The freeze applies to new siting, so existing facilities keep operating. The open question for colocation operators is how the 20 MVA line will apply to any expansion plans.

    Where the demand goes next is uncertain. Lin spoke of developing safeguards “locally and regionally,” which suggests the city expects the issue to extend beyond its borders. Developers could wait out the studies, redesign projects to meet whatever conditions emerge, or pursue sites elsewhere in the region. None has said publicly which it intends.

    What the Pause Does and Does Not Establish

    Juarez described the measure as a pause for accountability and said it “does not stop AI or data centers.” It is temporary, it requires a public hearing within 60 days, and permanent rules depend on studies that have not yet been done. The council cited “tens of thousands” of residents raising concerns and pointed to rate increases elsewhere in the country. Both are statements of position; the studies are what will test them locally. The developers’ side is equally unsubstantiated so far. The four companies have not publicly set out what they would pay for, what jobs or tax revenue they would bring, or how they would limit the impact on existing customers.

    This is one city’s decision, and it should not be read as a nationwide trend. It is notable because Seattle is a major West Coast technology center, and because the council framed the decision in cost terms rather than opposition to the technology itself. That framing can be answered with evidence, which gives both sides a clear question to argue over.

    Background

    Seattle City Light is the city’s electric utility, and the elected City Council oversees it through a committee currently chaired by Councilmember Debora Juarez. That structure puts decisions about serving very large new customers in the hands of officials who answer directly to local voters and ratepayers.

    Large data centers, especially those built for artificial intelligence, need continuous, high-capacity power, and they have become a growing source of new electricity demand for utilities across the United States. Seattle’s action came two months after reports that four companies had approached City Light about five facilities. Seattle’s decision is one of the more prominent local responses to that growth, because the city is a major West Coast technology center.

    Sources

    Source: City Council passes emergency data center moratorium and policy framework, Seattle City Council Blog, June 9, 2026: the council’s announcement of Council Bill 121214 and Resolution 32204.

  • TVA Moves Data Centers Into a Separate, Higher Power Rate Class

    TVA Moves Data Centers Into a Separate, Higher Power Rate Class

    The Tennessee Valley Authority (TVA) will charge data centers more for power under a separate rate, according to an April 28, 2026 report by the Chattanooga Times Free Press. The federally owned utility, which supplies electricity across Tennessee and parts of six neighboring states, is effectively carving hyperscale computing load out of its general commercial and industrial rate structure and pricing it as its own customer class.

    Executive Summary

    According to the report, TVA — the largest public power provider in the United States — is establishing a distinct rate under which data centers will pay more for electricity than they would under existing industrial tariffs. A “rate class” is the category a utility assigns to groups of customers with similar usage patterns; creating a new one for data centers means the utility believes this load is different enough in size, growth, and risk to deserve its own pricing.

    Why it matters: this is one of the clearest signals yet that utilities are no longer treating gigawatt-scale computing demand as ordinary industrial load. When a system as large as TVA’s formalizes a premium rate for data centers, it sets a reference point that other utilities, regulators, and public power boards across the country can cite. For operators planning campuses in the Tennessee Valley — a region that has actively courted data center investment — the cost of power, typically the largest ongoing operating expense of a data center, just became a moving target.

    Pricing Hyperscale Load as Its Own Risk Category

    Utilities have historically loved large industrial customers: steady, predictable consumption spreads fixed grid costs over more kilowatt-hours, which can lower rates for everyone. Data centers complicate that logic. They arrive in enormous increments, request interconnection faster than generation and transmission can be built, and — critically — a project can be cancelled or relocated after a utility has committed capital to serve it. A separate rate class is the standard regulatory tool for isolating that risk: it lets the utility recover the cost of serving data centers from data centers, rather than socializing it across households and smaller businesses.

    The reported move fits a broader pattern. Utilities and regulators in several U.S. markets have been developing large-load tariffs with features like minimum-demand charges, longer contract terms, and collateral requirements. TVA formalizing a higher rate suggests the debate has shifted from whether hyperscale load should be treated differently to how much more it should pay.

    What a Premium Rate Means for Data Center Economics

    Electricity is usually the single largest recurring cost of operating a data center, and for AI-oriented facilities running dense, power-hungry hardware, the sensitivity is even greater. A structurally higher rate changes site-selection math: the Tennessee Valley’s traditional pitch — abundant, relatively inexpensive, largely carbon-light power from a mix that includes nuclear and hydro — becomes less differentiated if data centers pay a premium over the headline industrial rate. The report does not disclose the size of the premium, so the practical impact could range from a rounding error to a genuine deterrent.

    Operators have levers in response: negotiating long-term supply agreements, bringing their own generation or storage to the table, or shifting flexible workloads to hours when the grid has spare capacity. But each of those adds complexity and capital cost, and none fully escapes a tariff that applies by customer class. The likely near-term effect is that hyperscalers press for contract structures — rather than published rates — where their scale gives them negotiating room.

    A Public Power Precedent With National Reach

    TVA occupies an unusual position: it is a federally owned corporation that sets its own rates through its board rather than through a state public utility commission. That autonomy means it can move faster than investor-owned utilities, whose large-load tariffs must survive contested rate cases. If TVA’s data center rate takes effect as reported, it becomes an operating precedent other utilities can point to when they argue that hyperscale customers should carry a larger share of grid-expansion costs.

    There is a fairness argument on both sides worth stating plainly. Ratepayer advocates contend that residential customers should not fund transmission and generation built for a handful of technology companies. Data center operators counter that they are long-tenured, high-load-factor customers whose demand justifies infrastructure the whole region eventually benefits from, and that punitive pricing simply pushes investment — and its tax base and jobs — to neighboring territories. The reported story does not resolve which framing TVA’s rate design reflects, and the details of the tariff will determine whether it reads as prudent risk allocation or as a growth deterrent.

    Background

    The Tennessee Valley Authority was created by Congress in 1933 and grew into the largest public power system in the country, serving roughly ten million people through a network of local power companies. Its generation mix — including nuclear, hydroelectric, gas, and coal — and its historically competitive industrial rates helped make the Tennessee Valley a magnet for energy-intensive industry, and more recently for data center development tied to cloud and AI growth.

    That growth collided with a nationwide reality: electricity demand, flat for two decades, began rising sharply as hyperscale computing facilities requested interconnections measured in hundreds of megawatts. Utilities across the U.S. responded by rethinking how such load is priced and contracted, seeking to protect other ratepayers from stranded-cost risk. TVA’s reported creation of a separate, higher data center rate places it among the most prominent utilities to formalize that shift.

    Source: TVA to charge data centers more for power under separate rate — Chattanooga Times Free Press report, April 28, 2026, on TVA’s creation of a separate, higher electricity rate class for data centers.

  • Wisconsin Regulators Say Data Centers Must Pay the Full Cost of Their Power

    Wisconsin Regulators Say Data Centers Must Pay the Full Cost of Their Power

    Wisconsin utility regulators have taken the position that data centers must cover the full cost of the energy infrastructure their facilities require, according to an April 23, 2026 report from Wisconsin Watch. The stance addresses the central fight of the data center boom: whether households and small businesses end up subsidizing the power plants, substations, and transmission lines built to serve a handful of very large computing campuses.

    The report’s headline frames the position as a directive — data centers, not the general body of ratepayers, bear the cost of their own demand. The underlying details of the proceeding, and how “full cost” will be defined and enforced, are not spelled out in the source material available to us.

    Executive Summary

    As reported by Wisconsin Watch on April 23, 2026, Wisconsin regulators have signaled that data centers seeking grid connections in the state must bear the full cost of their energy needs. In utility ratemaking terms, this is a cost-allocation principle: when a single customer’s demand forces the construction of new generation or grid capacity, that customer — rather than the shared pool of ratepayers — should pay for it.

    It matters because Wisconsin has become one of the Midwest’s most active data center markets, anchored by Microsoft’s multi-billion-dollar campus in Mount Pleasant and a pipeline of other announced projects. Each hyperscale campus can demand hundreds of megawatts — on the scale of a small city — and someone must pay for the infrastructure that serves it.

    The bigger significance is precedential. Regulators in many states are wrestling with the same question, and several utilities have proposed special tariffs for very large customers. A clear “you demand it, you pay for it” stance from a state actively courting data center investment offers a template others can copy — and a test of whether such terms slow investment or simply formalize what serious developers already expect to pay.

    The Cost-Allocation Fight Behind Every Data Center Boom

    Regulated utilities recover the cost of new infrastructure through rates approved by state commissions, and those costs are typically spread across all customer classes. That model works when growth is broad and gradual. It strains when one customer class — hyperscale data centers — arrives suddenly and demands capacity additions measured in gigawatts. If a utility builds a power plant or transmission line primarily for one campus and the project later shrinks or cancels, the leftover cost, known as a stranded asset, can land on everyone else’s bills.

    That risk is why “who pays” has become the defining regulatory question of the AI infrastructure cycle. Consumer advocates warn of cross-subsidization — ordinary ratepayers underwriting corporate compute. Utilities and developers counter that large loads can spread fixed grid costs over more sales and put downward pressure on rates if structured well. The Wisconsin position, as reported, comes down firmly on the side of insulating the general ratepayer.

    Why Wisconsin Is a Bellwether

    Wisconsin is not a legacy data center hub like Northern Virginia, which makes its posture instructive: it is a state actively attracting new hyperscale investment while setting terms at the front end rather than repairing cost shifts after the fact. Microsoft’s Mount Pleasant development, announced in 2024, put the state on the hyperscale map, and Wisconsin utilities have since proposed rate structures aimed at very large customers — typically featuring long-term contract commitments and minimum payments so that infrastructure built for a data center is paid for by that data center even if its plans change.

    A regulatory endorsement of full cost responsibility strengthens the utilities’ hand in structuring those deals and gives economic developers a cleaner pitch: growth without a ratepayer backlash. States competing for the same projects will watch whether Wisconsin’s pipeline holds up under these terms.

    What “Full Cost” Could Mean in Practice

    The phrase sounds simple; the implementation is not. Full cost responsibility can be enforced through several mechanisms: dedicated rate classes for very large loads, up-front contributions toward interconnection and grid upgrades, minimum demand charges that guarantee revenue regardless of actual usage, contract terms of a decade or more, and exit fees or collateral that protect against a project walking away mid-build. Each mechanism allocates a different slice of risk between the developer, the utility, and its shareholders.

    The definitional boundaries matter enormously. Does “full cost” cover only the local wires and substations, or a share of new generation? Does it apply to grandfathered projects or only new applicants? A principle announced by regulators becomes real only when it is written into approved tariffs and signed contracts, and the reported material does not yet show that level of detail.

    Winners, Losers, and the National Template

    Residential and small-business ratepayers are the clearest intended beneficiaries — the policy exists to keep their bills from absorbing data center-driven costs. Well-capitalized hyperscalers can generally live with full-cost terms; they already sign long-term commitments in other markets, and predictable rules can be preferable to political uncertainty. The squeeze falls on thinner-capitalized or speculative projects, which lose the ability to socialize their risk. Utilities get growth with less rate-case blowback, though they take on more counterparty risk concentrated in a few very large contracts.

    If Wisconsin’s stance holds and investment continues anyway, the template argument writes itself: states can welcome AI infrastructure without asking captive ratepayers to underwrite it. If projects visibly divert to states with softer terms, expect a counter-narrative that strict cost allocation costs jobs and tax base. Either outcome will be cited in commission dockets across the country.

    Background

    Wisconsin’s arrival as a data center state dates largely to 2024, when Microsoft announced a multi-billion-dollar campus in Mount Pleasant, southeast Wisconsin — on land once slated for the Foxconn manufacturing project — followed by further large-load proposals elsewhere in the state. That growth pushed Wisconsin utilities to propose rate structures for very large customers designed to ensure new infrastructure is paid for by the customers who require it.

    Nationally, the surge in AI-driven electricity demand has made cost allocation the central issue in utility regulation. State commissions, consumer advocates, utilities, and hyperscale developers are negotiating who bears the cost — and the risk — of the biggest grid build-out in decades, and headline positions like Wisconsin’s are being watched as potential templates.

    Source: Wisconsin regulators: Data centers must cover full cost of their energy needs — Wisconsin Watch report, April 23, 2026, on Wisconsin regulators’ position that data centers must bear the full cost of the energy infrastructure they require.