Off air

Politics · Data-center power costs

Senate stalls data-center power bill, leaving the question of who pays unresolved

A 57–43 majority could not advance the Ratepayer Protection Act. The central dispute: it would require jurisdictions to consider making giant computing customers pay their grid costs, but not require adoption.

Story trackerDay 7

1 report144 outlets244 sources4 videos

Video in its original language

Transcript · LOADING

Four hundred seventeen House members voted for the data-center electricity bill. Three voted against it. Two weeks later, 57 senators supported taking it up—and that still was not enough. The Ratepayer Protection Act stalled on September 30, leaving its proposed federal safeguard for electricity customers unenacted. 100 5

The practical question is simple enough: when a giant computing campus needs new power plants, transmission lines or distribution equipment, does the company ordering that expansion pay for it, or can some of the cost land on families and businesses that never ordered it?

The Senate dispute was over whether this bill would reliably deliver the first outcome. Its proposed standard assigned full incremental upgrade costs to covered computing customers. But jurisdictions would have been required to consider the standard, not adopt it. That gap between a protective principle and a binding protection explains more than the competing claims of bipartisan progress and political obstruction. 99

The September 30 result was a failed procedural vote, not a rejection on final passage. At 12:51 p.m. Eastern, Senate roll call 254 recorded 57 votes for cloture on the motion to proceed to H.R. 9340 and 43 against; 60 were required. The motion to proceed was subsequently withdrawn. Four Democrats joined Republicans in voting yes: Maggie Hassan of New Hampshire, Amy Klobuchar of Minnesota, and Georgia’s Jon Ossoff and Raphael Warnock. 5 55

Most Senate Democrats opposed advancing the measure because they considered its consumer protections inadequate. The House support was nevertheless overwhelming—and it was for this same bill, not merely a similar proposal. The Clerk records passage as amended, under suspension of the rules, on September 16, by 417–3, with 12 members not voting. NBC News’s September 30 broadcast described House passage as occurring the previous week; the official record puts it two weeks before the Senate vote. 3 100 1

A standard without mandatory adoption

Colorado Republican Representative Gabe Evans introduced H.R. 9340 on June 18, with Florida Democrat Kathy Castor as an original cosponsor. Ohio Republican Senator Jon Husted championed the Senate effort. His companion bill, S. 5028, was introduced July 16, but the September 30 vote concerned the House-passed measure. 101 102 6

The proposal targets very large computing loads, not every building called a data center. Covered customers would be nonresidential consumers contracting on or after enactment for facilities principally operating information-technology infrastructure and related data-storage and computational systems. Their aggregate peak demand would have to reach at least 100 megawatts at a single site or campus. 99

Under the proposed standard, rates would recover from those customers the full incremental costs of generation, transmission or distribution upgrades necessary to serve them. Responsibility would extend to remaining costs after a customer terminated its contract or stopped buying electricity. Utilities would obtain financial assurances or contributions before undertaking the upgrades. 99

That last part matters as much as the initial bill. Infrastructure can outlast the customer for whom it was built. A campus that shrinks, leaves or consumes less power than expected can leave expensive capacity behind. Requiring financial backing before construction is a way to address that risk rather than argue over it after the investment has been made.

But H.R. 9340 would amend the Public Utility Regulatory Policies Act of 1978, or PURPA, through its consider-and-determine framework. State regulators and nonregulated utilities would begin considering the standard within one year of enactment, complete consideration and make a determination within two years. Comparable prior state action could satisfy the process. Adoption would remain optional. Because the bill did not become law, neither deadline has begun. 99

Senate Democratic leader Chuck Schumer called it a “toothless messaging bill.” His objection has a specific basis in the legislation: a jurisdiction could complete the required process and decline the proposed protection. That does not mean the text contains no meaningful cost-allocation standard. It means the federal requirement would stop short of making that standard universal. 12 99

Husted’s case was that Congress should take a bipartisan step toward keeping large-load costs off other customers’ bills. During an earlier, blocked attempt to secure passage by unanimous consent on September 17, he said: 7

The Ratepayer Protection Act represents the most meaningful bipartisan step Congress could take to protect the American people from higher prices for electricity.

Jon Husted 7

The House tally gives the bipartisan argument real weight. It does not answer the enforcement argument. Agreement that companies should pay their way is not the same thing as requiring every jurisdiction to make them do so.

The risk behind the forecasts

The scale of possible electricity demand makes that distinction consequential. The Congressional Research Service cites a DOE/LBNL historical estimate of about 192 terawatt-hours consumed by U.S. data centers in 2024, roughly 4.7% of U.S. electricity. Its 2030 scenarios project 521–843 terawatt-hours, or 9.5–15.3%. Those are projections, not guaranteed demand. 80

A separate EPRI model puts the 2030 share at about 9–17%, with approximately 380–790 terawatt-hours in its own scenarios. The different assumptions mean these ranges should not be combined into one numerical series. Delayed or canceled campuses, overstated development pipelines and downward load revisions can make forecasts too high. That uncertainty strengthens the case for careful cost allocation: utilities can build for demand that never fully arrives. 80

Moody’s September financing scenario illustrates the potential investment. Using roughly 426 terawatt-hours of data-center consumption in 2030, it estimated about 45 gigawatts of new generation through that year, approximately $110 billion in capital costs, and $25 billion–$30 billion in additional annual electricity-system costs. The anticipated buildout was mostly gas, with some solar and storage and little nuclear restart. 79

Those figures are neither realized costs nor a prediction that households will pay everything left over. The analysis envisaged data centers directly covering up to about $15 billion through on-site or behind-the-meter projects representing roughly 30% of the generation buildout—not 30% of annual system costs. Who ultimately pays depends on tariffs, regulation and actual development. 79

Ohio brings the argument home

Before the vote, Reuters reported on September 28 that Republicans wanted to demonstrate action on electricity-rate concerns ahead of the midterms. That planned vote has now occurred and failed to advance the bill. Ohio is a concrete campaign test: Husted faces former Democratic Senator Sherrod Brown in the November 3 special election for the remainder of J.D. Vance’s Senate term. 4 142

Brown has criticized Husted’s earlier promotion of data centers and tax incentives. Both candidates oppose shifting major new loads’ infrastructure costs onto households, but their positions are not interchangeable. Husted advanced the federal consideration proposal. Brown favors local say over siting, union labor, an end to excessive tax breaks and protection against higher electricity bills. Those campaign positions do not themselves establish a separate enacted federal cost mandate. 200 198 203 99

The polling shows political discomfort, not an election forecast. The original NBC News survey found 64% less likely to support “A candidate who supports building a data center in your community”: 51% were much less likely and 13% somewhat less likely. Eleven percent were more likely and 22% said it would make no difference. NBC’s September 30 broadcast shorthand described 51% as less likely; that was the strongly negative subgroup, not the total. 213 16 1

The item was asked September 14–15 to 397 registered voters on Form A, with a margin of error of ±4.92 percentage points. The broader Hart Research/Public Opinion Strategies survey for NBC interviewed 1,000 registered voters September 11–15, but its smaller overall margin does not describe this question’s precision. Only 2% selected data centers as their leading issue among nine national issues. A low national priority can still become an unpopular local position. 213 134

President Donald Trump continues to argue for expansion on economic and China-competition grounds. On September 29, he said host areas “have become very rich” and “their taxes have gone down, not up.” Those are his assertions, not verified universal benefits. National competition and promised prosperity do not settle who pays for the grid. 74

Known

  • The bill did not advance or become law. Its proposed federal consideration requirement and adoption deadlines are not in effect. 55599

Unknown

  • No dated next congressional vote or replacement measure is established. The election impact of this dispute remains unknown.

Next

  • November 3 brings Ohio’s special election, but its result alone cannot establish that data centers determined voters’ choices.

The Senate result neither bans data centers nor creates a new nationwide obligation for covered customers to pay their incremental electricity and infrastructure costs. Existing state and utility rules remain separate. For consumers, that is the immediate consequence: Congress has not resolved the cost-allocation question, and the failed proposal would have required a decision about protection—not guaranteed the protection itself. 99 172

As aired 24 lines
  1. The Senate blocked a data-center cost bill that 417 House members supported. The vote leaves a proposed federal ratepayer standard unenacted, with families and businesses facing the question of who pays for power plants and grid upgrades built for giant computing campuses. Would this bill have guaranteed that data centers pay those costs—and what protections remain now?
  2. Fifty-seven senators supported advancing the measure—not rejecting it. But they fell three votes short of the sixty needed to overcome the procedural hurdle. On September thirtieth, the Senate rejected cloture on the motion to proceed to H.R. 9340, the Ratepayer Protection Act. That prevented senators from taking up the House-passed bill; it was not a final-passage vote. The motion to proceed was subsequently withdrawn. Four Democrats joined Republicans in voting yes: Maggie Hassan of New Hampshire, Amy Klobuchar of Minnesota, and Georgia's Jon Ossoff and Raphael Warnock. Most Senate Democrats opposed moving ahead because they considered the consumer protections inadequate.
  3. The House had passed this same measure two weeks earlier, on September sixteenth—not during the week immediately before the Senate vote. The tally was 417 to three, with twelve members not voting. Passage came under suspension of the rules, requiring a two-thirds majority. That establishes overwhelming bipartisan passage, despite older bill-status descriptions that still reflected an earlier legislative stage.
  4. Colorado Republican Representative Gabe Evans introduced H.R. 9340 on June eighteenth. Florida Democrat Kathy Castor was an original cosponsor, and the measure was ordered reported from committee on July twenty-first. Ohio Republican Senator Jon Husted championed the Senate effort. His companion, S. 5028, was introduced July sixteenth and referred to the Energy and Natural Resources Committee. But the September thirtieth vote concerned the House bill, not final passage of Husted's Senate companion.
  5. The bill draws its coverage line at one hundred megawatts of aggregate peak demand at a single site or campus. It targets nonresidential customers contracting on or after enactment for facilities principally operating information-technology infrastructure and related data-storage and computing systems. It would not cover every building called a data center.
  6. Its proposed standard would recover the full incremental costs of generation, transmission and distribution upgrades from the large-load customer needing them. That responsibility would continue for remaining costs after the customer terminated its contract or stopped buying electricity. Utilities would obtain financial assurances or contributions before undertaking the upgrades. The purpose is to protect other customers from infrastructure costs left behind when a campus shrinks, leaves, or uses less capacity than planned.
  7. States would have to consider the protection, but would not have to adopt it. That is the decisive distinction. The proposal would amend the Public Utility Regulatory Policies Act of 1978, known as PURPA. State regulators and nonregulated utilities would begin consideration within one year of enactment, then finish considering the standard and make a determination within two years. Comparable prior state action could satisfy that process. The binding federal obligation would be to consider and decide—not necessarily to implement the cost protection. Because the bill did not become law, neither deadline has begun.
  8. The bill contains detailed proposed cost protections, but no nationwide requirement to adopt them. Senate Democratic leader Chuck Schumer attacked that optional structure as insufficient to ensure data centers pay their costs. His criticism does not mean the text contains no protective standard. It means jurisdictions could complete the required process and decline to put that standard into effect.
  9. Husted's goal was to make large data centers bear their electricity and infrastructure costs rather than shift them to other ratepayers. An earlier attempt to obtain passage by unanimous consent was blocked on September seventeenth, separate from the later cloture vote.
  10. His argument rests on taking a bipartisan step toward protection. After the September thirtieth vote, he accused Senate Democrats of rejecting a policy conservative and liberal House members had supported. The House tally supports his claim of bipartisan agreement. It does not settle whether requiring state consideration would deliver the protection households need.
  11. Data centers used an estimated 192 terawatt-hours of electricity in 2024—about 4.7 percent of U.S. consumption. That is a historical estimate, not a measurement of their 2026 use. One set of scenarios projects 521 to 843 terawatt-hours in 2030, or 9.5 to 15.3 percent of U.S. electricity. A separate model projects roughly 380 to 790 terawatt-hours, representing about nine to seventeen percent. Those models use different assumptions and should not be combined into one forecast. Delayed or canceled campuses, overstated development pipelines and downward revisions by grid operators can all make demand forecasts too high.
  12. National electricity sales are projected to reach 4,135 billion kilowatt-hours in 2026 and 4,211 billion in 2027. The 2026 forecast represents about two percent growth. Commercial-sector sales are projected to grow 3.3 percent in 2026 and 2.7 percent in 2027, with data centers and manufacturing among the drivers. These are sales forecasts across the economy—not generation totals, not data-center-only consumption, and not a measurement of how much a family's bill has increased because of a nearby campus.
  13. A separate financing scenario puts the generation buildout at about forty-five gigawatts through 2030, costing roughly 110 billion dollars. It anticipates mostly gas, some solar and storage, and little nuclear restart. Its calculation uses approximately 426 terawatt-hours of data-center consumption in 2030—a different planning assumption from the other demand scenarios.
  14. That scenario estimates twenty-five billion to thirty billion dollars in additional electricity-system costs each year. Data centers might directly cover up to about fifteen billion dollars through on-site or behind-the-meter projects representing roughly thirty percent of the generation buildout. Thirty percent describes the buildout—not a share of annual system costs. These figures are not enacted spending or realized nationwide costs, and they do not establish that all remaining costs would fall on residential customers. The allocation depends on actual development, utility tariffs and regulation.
  15. Sixty-four percent of respondents said they would be less likely to support a candidate who backed building a data center in their community. Fifty-one percent were much less likely, and thirteen percent somewhat less likely. So fifty-one percent is the strongly negative subgroup—not the total negative response. Eleven percent were more likely to support that candidate, and twenty-two percent said it would make no difference. The remaining response category is not established and cannot be labeled. Respondents were asked how information about a candidate would affect their likelihood of voting for that person, then whether a positive or negative effect would be much or somewhat.
  16. The data-center item was asked only on Form A, September fourteenth and fifteenth, to 397 registered voters. Its margin of error is plus or minus 4.92 percentage points. The broader survey ran September eleventh through fifteenth with one thousand registered voters: 724 live telephone interviews and 276 text-to-web interviews. Its overall margin was 3.10 points; the Form A and B half-samples had a 4.38-point margin. Neither smaller margin describes the precision of this particular data-center question.
  17. A separate poll published September sixth found sixty-nine percent opposed building AI data centers in their areas, including forty-five percent strongly opposed. That measures construction opposition, not a candidate's electoral appeal. Its methodology is not established here, so it cannot be merged with the candidate-support results.
  18. Forty-four percent chose neither party on the question of trust over data centers. Thirty-two percent chose Democrats and twenty percent Republicans. The remaining response category and item-level methodology are not established. Those are issue-trust responses, not predicted votes. And only two percent selected data centers as their leading issue among nine national issues in the September survey. Low national priority can coexist with a negative reaction to a candidate backing a project close to home.
  19. Ohio voters will choose between Husted and former Democratic Senator Sherrod Brown on November third, in a special election for the remainder of J.D. Vance's Senate term. Brown has criticized Husted's earlier promotion of data centers and their tax incentives. Before the Senate vote, Republicans were seeking to demonstrate action on electricity-rate concerns ahead of the midterms. That planned vote has now happened, and the measure failed to advance.
  20. Both candidates say major new loads should not shift infrastructure costs onto households. But their records and proposals are not interchangeable. Husted advanced the federal consider-and-determine proposal. Brown calls for local say over siting, union labor, an end to excessive tax breaks and protection against higher electricity bills. He has not produced a separate enacted federal mandate resolving the cost-allocation dispute. Minimum-billing percentages and multi-year exit provisions in Ohio utility tariffs are utility rules—not Brown's personal legislative proposal, and not protections enacted by this failed federal bill.
  21. President Donald Trump continues to promote data-center expansion as economically beneficial and necessary for technological competition with China. His September twenty-ninth remarks asserted that companies would satisfy communities, that host areas had become wealthy, and that their taxes had fallen. Those are political claims—not verified findings that every host community benefits or pays lower taxes. His assertion that China would welcome projects rejected in the United States does not establish a Chinese commitment to accept any particular project.
  22. His comparisons with the Industrial Revolution also varied in certainty. In one September twenty-ninth statement, he pledged not to stifle a technology he described as larger than that transformation. In another, he attributed the comparison to others and explicitly acknowledged uncertainty. Those remarks belong to September twenty-ninth, not the previous day's coverage of his support. Neither formulation answers who pays for expanding the grid or proves household costs will fall.
  23. The answer to the central question is no: this bill would not have guaranteed nationwide that covered data centers pay their full incremental electricity and infrastructure costs. It would have required consideration of that protection, with adoption left optional. The failed vote neither bans new data centers nor sets a national electricity price or construction cap. Existing state and utility rules remain distinct, and actual household exposure depends on those rules and what gets built.
  24. No dated next congressional vote or replacement legislation is established. November third is the next concrete test in the Ohio campaign, but national hypothetical-candidate polling cannot determine how Ohio residents will vote or which issue will decide the race. The proposed federal consideration requirement is not law, and this vote secured no nationwide obligation for covered data centers to pay their incremental electricity and infrastructure costs.

Sources

244 sources144 outlets4 videos3 wire copies

Source map

Follow the evidence behind this report. The map shows its connections; the links below open the sources cited in this article.

Source map loads as you read.

Revision log

  1. r1First published.