IBM Just Had Its Worst Trading Day in 115 Years

A company that survived two world wars, the mainframe era, the dot-com bust, and the 2008 crash just had its single worst trading day ever — and the earnings miss that caused it was, by historical standards, small. That gap between cause and effect is the actual story.

What happened on July 14?

IBM stock fell 25.2%, closing around $217 a share and wiping out roughly $67 billion in market capitalization in a single session, dropping the company’s valuation to just under $205 billion. It is the largest one-day decline in IBM’s 115-year history, exceeding the 23.7% the stock lost on Black Monday, October 19, 1987, when the entire market crashed simultaneously.

This time was different in one crucial way: the market didn’t crash. IBM did. The trigger was a preliminary second-quarter update, released ahead of the company’s scheduled July 22 earnings call, showing adjusted earnings per share of $2.93 against a Wall Street consensus of $3.01, and revenue of $17.2 billion versus $17.86 billion expected — a shortfall of roughly $660 million.

Why did a ~3% miss cause a 25% crash?

Because the number that spooked investors wasn’t the miss itself — it was what CEO Arvind Krishna said caused it. In a letter to shareholders, Krishna wrote: “These conditions require our teams to execute perfectly, and this quarter we faltered. We did not adapt and move quickly enough, and numerous large deals failed to close on the timelines we expected, driving the majority of our shortfall.”

Krishna’s explanation: in the final weeks of June, IBM’s enterprise clients redirected quarterly capital spending away from software and infrastructure contracts and toward servers, storage, and memory chips — racing to lock in supply-constrained hardware ahead of anticipated price increases. IBM said it had planned for some supply-chain disruption, but not for the scale of the reprioritization.

Where did the money actually go?

Krishna’s explanation points directly at the AI chip and memory supply crunch that’s been reshaping enterprise budgets all year. Clients weighing a choice between signing a software contract or securing hardware capacity before prices rise chose the hardware — a rational move for any buyer who believes memory and server supply will only get tighter. The same dynamic that sent SK Hynix’s Nasdaq listing soaring on memory-chip demand is, on IBM’s telling, the reason its software pipeline stalled.

Q2 2026 (preliminary)	Wall Street expected	IBM reported
Revenue	$17.86B	$17.2B
Adjusted EPS	$3.01	$2.93
Stock reaction	—	-25.2%

Did the panic spread beyond IBM?

Partially. Software peers Microsoft, Salesforce, ServiceNow, and Intuit each fell roughly 2% to 5% the same day, as investors marked down other enterprise-software names exposed to the same capex-diversion risk. But the broader Nasdaq 100 index still closed higher, meaning this wasn’t a market-wide flight from tech — it was a targeted repricing of software companies whose growth stories assume steady enterprise IT budgets rather than budgets increasingly captured by AI hardware.

Wall Street’s sell-side response was swift and mixed. BofA cut its price target from $330 to $280 while keeping a Buy rating, arguing IBM remains “well positioned” once execution issues clear. HSBC downgraded the stock from Hold to Reduce, cutting its target from $231 to $191 on the view that IBM’s valuation was stretched relative to the sector. Goldman Sachs was blunter, warning the results would “fully validate the software bear case scenario” that bears had been making for months.

What does this mean for how AI-era earnings get read?

It means the market is now hunting for AI-bubble evidence in ordinary earnings misses — and finding it. Fortune’s coverage framed the IBM crash as a sign of a potential “earnings bubble,” distinct from a valuation bubble: the risk isn’t that AI stocks are simply priced too high, but that the profit and growth assumptions baked into those prices are themselves inflated by capex spending that could just as easily reverse or redirect, as it did here. A single quarter of clients preferring memory chips over software licenses was enough to erase $67 billion.

For developers and technical leaders watching enterprise IT budgets, the read-through is concrete: capex is being actively reallocated in real time between software and infrastructure line items, and vendors on the losing side of that reallocation can get repriced violently even on modest misses. If your product sells into enterprise IT budgets, “AI adjacent” is no longer automatically a tailwind — it can be a budget line someone else is now competing for.

The bottom line

IBM’s crash is a reminder that in an AI capex cycle, “beating expectations” and “keeping your customers’ budget” are no longer the same test. A company with 115 years of trading history just had its worst day not because a war broke out or a bank failed, but because enterprise buyers, given a choice between software and hardware in a supply-constrained quarter, chose hardware. Whether that’s a one-quarter blip or the first visible crack in the “AI earnings bubble” story is exactly what the market will spend the rest of 2026 trying to figure out — starting with IBM’s full Q2 report on July 22.