On September 16, the House passed the Ratepayer Protection Act by a vote of 417 to 3. Four hundred seventeen to three. In a Congress that can’t agree on what day it is, that’s not a bipartisan vote — that’s a near-unanimous one, the kind you get maybe once a year on anything with “AI” attached to it. The bill would push state regulators to make data centers pulling 100+ megawatts off the grid pay for the power plants and transmission lines their own demand requires, instead of spreading that cost across everyone else’s electric bill.

Then, on September 17, the whole thing ran straight into the Senate and died. Not the bill itself — a Republican senator’s attempt to fast-track it, followed immediately by a Democratic senator’s attempt to fast-track something tougher. Both got blocked, on the floor, within minutes of each other. Congress managed to agree almost unanimously that AI data centers shouldn’t get a free ride on your power bill, and then, the very next day, proved it still can’t get out of its own way to actually do anything about it.

Quick Summary: What Happened

Detail	Info
House vote	417-3, September 16, 2026
What it does	Pushes state regulators to make 100+ MW data centers cover their own grid-upgrade costs
Who voted no	Reps. Summer Lee, Delia Ramirez, and Rashida Tlaib — all Democrats
Senate fast-track attempt	Blocked September 17 by Sen. Martin Heinrich (D-NM)
Heinrich’s alternative	The GRID Savings Act, blocked in turn by Sen. Bernie Moreno (R-OH)
Official source	H.R. 9340, Ratepayer Protection Act

Bottom line: Congress found near-total agreement that AI shouldn’t be allowed to quietly raise your electric bill, and then, one day later, proved that agreement doesn’t survive contact with the Senate.

What Actually Happened

Start with what the bill actually does, because “make AI pay for its own power” is the pitch, not the mechanism. H.R. 9340, sponsored by Rep. Gabe Evans (R-CO) and Rep. Kathy Castor (D-FL), amends the 1978 Public Utility Regulatory Policies Act to push state utility commissions toward requiring “large load” customers — facilities drawing 100 megawatts or more, which is squarely where a modern AI data center campus lives — to cover the full incremental cost of the generation, transmission, and distribution upgrades built to serve them. States get a year to start the process and two years to finish it. Large loads have to post financial assurances before utilities break ground, and if a data center bails on its power contract early, the bill guarantees the utility still gets made whole. Rep. Evans put it plainly: “Hardworking families should not have to subsidize the energy demands of data centers.” Castor’s version of the same point: “If Big Tech builds a massive AI data center, Big Tech — not hardworking families, farmers or small businesses — should pay for the power and grid upgrades it requires.”

That message cleared the House Energy and Commerce Committee 52-0 back in July, then cleared the full floor 417-3 in September. The three no votes — Reps. Summer Lee, Delia Ramirez, and Rashida Tlaib — weren’t objecting to the idea. Tlaib’s complaint was that the bill doesn’t go far enough: it only requires state regulators to consider adopting cost-recovery rules, not actually adopt them, which she argued would “fail to meaningfully protect our communities.” That’s a real distinction, and it’s the exact distinction that ended up sinking the bill’s fast-track shot in the Senate a day later.

The backdrop here isn’t abstract. Nationally, electricity prices have climbed roughly 27% since 2019 — well ahead of general inflation — and in the states where data centers have clustered hardest, bills are rising faster still: Virginia up 13% in a single year, Illinois up 16%, Ohio up 12%. Data center construction rose 57% between July 2025 and July 2026. None of that is a coincidence a state regulator has to squint to see.

Why Did the Senate Fast-Track Attempt Collapse a Day Later?

1. Sen. Jon Husted (R-OH) tried to pass H.R. 9340 as-is through unanimous consent on September 17 — a procedural shortcut that only works if literally zero senators object, which is a low bar Congress clears constantly for uncontroversial bills.
2. Sen. Martin Heinrich (D-NM), the top Democrat on Senate Energy and Natural Resources, objected, arguing the bill’s core mechanism is too weak. “It’s not enough for us to tell states to consider making data centers pay for grid updates,” he said from the floor — the same “consider, don’t require” gap Tlaib flagged in the House.
3. Heinrich immediately countered with his own unanimous consent request for the GRID Savings Act, which he’d introduced back in August. It hands the Federal Energy Regulatory Commission direct rulemaking authority over any facility drawing 150+ megawatts, requiring those operators to absorb infrastructure costs under one binding national standard instead of a patchwork of state “considerations.”
4. Sen. Bernie Moreno (R-OH) objected to that one in turn, and didn’t pretend it was about the merits. “The term ‘do-nothing Congress’ exists for a reason,” he said on the floor. “We absolutely accomplished that right now.”
5. Husted, whose Ohio reelection race has made data center costs a live campaign issue, didn’t take the loss quietly — he posted on X that “Senate Democrats want Big Tech to get a free pass while your electric bill goes up,” and on the floor said, “It is a shame that this opportunity has been missed today, but I will be back to push this issue forward.”

Why This Matters

Line up the two bills and the disagreement isn’t really about whether AI data centers should pay for their own grid upgrades — everyone involved, House and Senate, both parties, agrees on that part. It’s about how hard the requirement bites. The House bill nudges states to act over a one-to-two-year runway and stops short of forcing their hand. Heinrich’s GRID Savings Act skips the state layer entirely and puts FERC in charge of one binding national rule. “If a company is driving the need for expensive new facilities, that company should pay for it — not families and small businesses,” Heinrich said when he introduced it. That’s not a different goal than the House bill. It’s a different amount of trust in whether state regulators will actually use the discretion Congress hands them, and Tlaib’s three-vote objection in the House was the same bet made from the other chamber.

Husted’s political situation adds a layer worth being honest about. He’s in a competitive Ohio reelection fight where data center costs are already an attack line, which is exactly why he wanted a clean, fast, bipartisan-looking win before it became a floor fight. Heinrich answering with “only if it’s my stronger bill,” followed by Moreno tanking that bill on the very next request, turned a policy disagreement into something closer to the Senate’s ordinary reflex against letting the other side claim credit.

This also lands inside a broader story this site has tracked about who gets to set AI’s pace. Anthropic’s Dario Amodei has pushed labs to voluntarily slow down; Sam Altman told OpenAI staff he’s open to the same idea, then had to ask Congress if coordinating on it with rivals is even legal; Trump has dismissed the entire pacing conversation as a “sick conspiracy.” Those stories are all about whether labs should slow model releases. This one’s different — it’s about who eats the electric bill while AI keeps moving — and it’s the first version of that question to get an answer nearly the whole House agreed on, only for the Senate to prove even the least controversial AI-adjacent idea in Washington isn’t immune to normal gridlock.

What Are Your Options Now

If you’re a residential ratepayer in a state with heavy data center buildout (Virginia, Illinois, Ohio, and similar high-concentration states are the ones to watch), nothing changes on your bill yet. Both the House bill and Heinrich’s alternative are stalled, and states aren’t required to act on either. Your state utility commission’s public comment process — not Congress — is currently where this actually gets decided, and most of those proceedings are open to public input.

If you’re evaluating where to site or build an AI data center, treat “large load cost recovery” as a when, not an if, regardless of what happens in Washington. Roughly 18 states already have purpose-built data center tariffs in place or approved, with a median threshold around 50 megawatts — well below either federal proposal’s floor. Federal inaction doesn’t mean state-level cost exposure isn’t already here.

If you’re tracking AI policy for enterprise compliance or government-affairs reasons, watch the state commissions and FERC dockets more closely than the Senate floor for now. With the Senate leaving Washington in roughly two weeks and midterms looming in November, neither bill is likely to move again this session — the House’s near-unanimous vote was the easy part.

The Bigger Picture

The uncomfortable read here isn’t that Washington disagrees about AI and electricity costs. It’s that it doesn’t, really — and gridlocked anyway. A 417-3 House vote is about as close to consensus as modern Congress produces on anything, let alone something touching both Big Tech and utility regulation. The Senate had two separate chances, roughly ten minutes apart, to advance some version of the same basic idea, and both attempts died to single-senator objections that were more about process, timing, and an Ohio Senate race than about the substance either side claims to care about.

That’s a pattern this site has now documented across a few different flavors of AI governance this year: strong agreement on the problem, followed by breakdown over whose version of the fix gets to pass. It happened with lab pacing. It’s happening again here, just with electric bills instead of model releases. The mechanism for making AI data centers pay their own way clearly exists — multiple versions of it, in fact, sitting in the same building on the same day. What’s missing isn’t consensus. It’s a Senate willing to let either version through without extracting something else first.

Our Take

We think the 417-3 vote is the real story and the Senate collapse is the predictable coda, not the other way around. It’s genuinely rare for Congress to agree this cleanly that AI infrastructure shouldn’t get subsidized by people who’ll never use it — that’s worth taking seriously as a signal, even with the underlying bill’s soft “consider” language doing a lot of the compromise that made 417 votes possible in the first place.

Heinrich’s objection is the more interesting substantive argument of the two, separate from how the Senate floor fight actually played out. “States should consider adopting cost-recovery rules” and “FERC sets one binding national rule” produce meaningfully different outcomes for the same stated goal, and reasonable people can land on either side of state discretion versus federal mandate here. What’s harder to defend is Moreno tanking the stronger version in the same breath Husted was blocked on the weaker one — that’s not two competing visions of good policy losing to each other. That’s neither version getting a real vote.

For ratepayers, the practical signal is this: don’t wait on Congress. State utility commission dockets are where the actual cost allocation gets decided either way, federal bill or not, and that process is already underway in the states carrying the heaviest data center load.

Frequently Asked Questions

What does the Ratepayer Protection Act actually require?

H.R. 9340 pushes state utility regulators to require data centers and other “large load” customers drawing 100+ megawatts to cover the full incremental cost of generation, transmission, and distribution upgrades built to serve them, rather than spreading those costs to residential ratepayers. States have one year to begin the process and two years to finalize rules, and large loads must post financial assurances before utilities start construction.

Why did the House pass it 417-3?

The bill drew broad bipartisan support because it addresses a concrete, visible problem — rising electric bills in states with heavy data center buildout — without mandating a specific outcome; it only directs state regulators to consider adopting cost-recovery standards, which kept objections to a minimum. The three no votes, from Reps. Summer Lee, Delia Ramirez, and Rashida Tlaib, came from the opposite direction: they argued the bill’s “consider” language is too weak to guarantee results.

Why did the Senate version fail?

Sen. Jon Husted (R-OH) tried to pass the House bill through unanimous consent on September 17, but Sen. Martin Heinrich (D-NM) objected, arguing it lacked enforcement teeth. Heinrich then sought unanimous consent for his own, stronger bill, the GRID Savings Act, which Sen. Bernie Moreno (R-OH) blocked in turn. Both attempts died within the same floor session.

What is the GRID Savings Act?

Sen. Martin Heinrich’s GRID Savings Act, introduced in August 2026, would give the Federal Energy Regulatory Commission direct rulemaking authority over facilities drawing 150 megawatts or more, requiring them to absorb grid-upgrade costs under one binding national standard rather than leaving it to individual states.

Does this affect my electric bill right now?

Not directly, not yet. Both federal bills are stalled, and neither has changed a single utility’s rate structure. But roughly 18 states already have their own data center-specific electricity tariffs in place or pending, with thresholds well below either federal proposal, so cost allocation may already be moving in your state regardless of what Congress does.

Is this bill likely to pass before the midterms?

Unlikely. With the Senate scheduled to leave Washington within about two weeks of the September 17 floor fight and midterm elections in November, neither the House bill nor Heinrich’s alternative has an obvious path to a floor vote before the current session’s window closes.

Which AI data center operators does this apply to?

The House bill’s threshold is 100 megawatts of demand; Heinrich’s competing bill sets it at 150 megawatts. Both thresholds are designed to capture large hyperscale AI training and inference campuses — the kind Amazon, Microsoft, Google, Meta, and OpenAI-aligned partners have been building at record pace — while leaving smaller commercial and industrial facilities out of scope.

How does this connect to the broader AI infrastructure buildout?

Data center construction is accelerating fast enough to strain grid capacity in concentrated regions, which is the direct cause of the rate pressure this bill responds to. It’s the electricity-cost side of the same infrastructure boom covered in Amazon’s $200 billion AI infrastructure commitment and the chip supply deals, like Qualcomm’s $60 billion agreement with AWS, feeding it.

---

Last updated: September 19, 2026. Sources: H.R. 9340 — Ratepayer Protection Act · Rep. Gabe Evans — press release · Utility Dive — House passes ratepayer protection bill · Yahoo News — Senate Democrat blocks Ratepayer Protection Act · Sen. Heinrich — GRID Savings Act introduction · Latitude Media — One Senate Democrat’s answer to Trump’s ratepayer protection pledge · CNBC — What’s happening to electricity prices in data center states.

Related reading: Dario Amodei Told AI Labs to Slow Down. OpenAI Blinked. · Altman Wants to Slow AI Down. Antitrust Says Maybe Not · Trump Calls AI Slowdown Warnings a ‘Sick Conspiracy’ · Amazon Bets $200B on AI: What Changes for Users · Qualcomm’s $60B AWS Deal Cracks Nvidia’s AI Grip