Bitcoin hashrate slumps as US miners curtail during winter storm

Earlier this week, a sweeping US winter storm pushed Bitcoin miners to curtail, pulling a noticeable chunk of computing power off the network in a short window.

Data shows a 40% dip in hashrate between Jan. 23 and Jan. 25, with around 455 EH/s going offline, and block production slowing to around 12 minutes for a stretch.

bitcoin hashrate
Graph showing Bitcoin’s hashrate from Jan. 20 to Jan. 30, 2026 (Source: CoinWarz)

The fact that the sharpest drop came from Foundry USA, the largest mining pool with the largest presence in the US, tells you that the drop was caused by curtailments.

bitcoin mining pools hashrate minersbitcoin mining pools hashrate miners
Graph showing the 30-day distribution of Bitcoin’s hashrate by mining pools on Jan. 30, 2026 (Source: Hashrate Index)

Why can so many miners now shut off quickly? Why would they ever choose to do it, and what do those choices mean for Bitcoin’s security budget, transaction flow, and the politics of plugging a large industrial load into a grid that can get stressed in extreme cold?

Curtailment 101: miners as flexible load, not fragile infrastructure

While curtailment is simple in definition, it’s kind of messy in practice. At the simplest level, it’s miners reducing electricity consumption, either partially or fully, because power is scarce, expensive, or contractually more valuable to sell back to the grid than to burn through ASICs.

In the US, and especially in Texas, that choice has matured into a full-blown business model. ERCOT has explicitly created mechanisms meant for “large flexible customers” that can reduce load during peak demand, and it named Bitcoin mining facilities as a core example.

The idea is straightforward: if a load can drop quickly, reliably, and repeatedly, a grid operator can treat it as a pressure-release valve during tight conditions.

In real mining fleets, curtailment tends to fall into three buckets.

The first is purely economic. Miners watch a simple spread: revenue per unit of hash versus the all-in cost of producing that hash. When real-time power prices spike, the cheapest decision can be to just stop hashing.

This is no charity, and it’s certainly not some kind of corporate moral stance. It’s just your basic unit economics measured minute by minute, especially for miners exposed to wholesale pricing.

The second is contracted. Some miners sign demand-response arrangements where the “off switch” is effectively part of the product they sell.

Texas has offered multiple ways for flexible load to participate in reliability programs, and the last few years have produced plenty of cases of miners profiting during stress events by curtailing or selling contracted power back into the market.

Company disclosures show miners can earn money for not consuming power when the grid is tight. In Riot’s August 2023 update, the company split the haul into two buckets: $24.2 million of “power Credits,” which it describes as power curtailment credits earned by selling contracted power back into ERCOT at market spot prices, plus $7.4 million of something called “demand response credits,” tied to participation in ERCOT demand response programs.

The smaller, routine versions of this show up in almost all of Riot’s monthly reporting. In its November 2025 update, Riot listed $1 million in estimated power curtailment credits and $1.3 million in estimated demand response credits, noting that those demand response credits came from participation in ERCOT and MISO programs and that the combined credits are netted against its all-in power cost.

Iris Energy’s investor update from August 2023 said its Texas site generated about $2.3 million in “power sales,” described as power credits primarily driven by voluntary curtailment under hedge contracts tied to ERCOT real-time prices.

In that setup, a mining site is closer to a hybrid of data center and power trader than the old mental model of a warehouse that just runs ASICs until they break.

The third is emergency or rule-driven. Texas now expects the biggest new loads to be curtailment-ready as a condition of interconnection in grid-emergency scenarios, explicitly naming crypto miners and data centers among the targets.

That matters because it turns curtailment from something nice to have into something that’s now built into the operating plan.

What makes this week’s storm useful as a teaching moment is that the incentives line up.

Cold snaps lift heating demand, which tightens reserve margins and often triggers conservation alerts. The storm was seriously disruptive for the US energy system, with price spikes and operational strain reported across regions.

So, if you’re a miner sitting on a flexible load arrangement, curtailment is often the cleanest, most rational response to a grid that is suddenly valuing a megawatt more than a terahash.

This is also why the pool-level picture can move fast. When US-heavy operators curtail, their pools register it almost immediately. The week’s curtailment effect was most easily seen through the visible drop in Foundry’s hashrate and the knock-on slowdown in blocks.

While the network is global, the marginal hashrate swing can still be regional when enough capacity clusters behind a handful of operators and grid regimes.

Bitcoin’s difficulty timer: why slow blocks are usually a temporary tax

A hashrate shock scares people because they map it directly to security. That’s true, but in a very narrow sense, because fewer hashes per second means the brute-force cost of attacking the chain is lower than it would be at peak hashrate.

But the more important operational question is what Bitcoin does when hashes disappear quickly. The answer is that Bitcoin has a built-in recalibration mechanism with a built-in delay.

Bitcoin targets one block roughly every 10 minutes, but it doesn’t adjust difficulty continuously. It adjusts difficulty every 2,016 blocks based on how long the last 2,016 blocks took to mine.

That structure creates the short-term “storm tax.” If a lot of miners shut off today, blocks will be slow today. However, the difficulty doesn’t instantly drop to compensate; the network just produces blocks more slowly until enough of them pass for the next adjustment to reprice the work.

You could see that taking place in real time this week. CoinWarz’s difficulty dashboard showed the network running slower than the 10-minute target, with average block time above target during the window it tracked.

When block production stretched to roughly 12 minutes, it was the lived experience of that lag: fewer blocks per hour, slower confirmations on average, and a mempool that can thicken if transaction demand holds steady.

CryptoSlate Daily Brief

Daily signals, zero noise.

Market-moving headlines and context delivered every morning in one tight read.