IBM Investors Watch Early Q3 Recovery After Infrastructure-Driven Q2 Shock

IBM Investors Watch Early Q3 Recovery After Infrastructure-Driven Q2 Shock

Sun, September 20, 2026

IBM shares plunged in mid-July after the company warned that preliminary second-quarter 2026 revenue fell short of expectations. The miss was largely attributed to a 7% decline in infrastructure-related sales, especially in its mainframe (Z) business, as customers redirected capital expenditures toward AI-related servers and storage. This marked one of the steepest single-day drops in IBM’s recent history.

On July 22, IBM released its full Q2 results and revised its 2026 constant-currency revenue growth guidance to a range of 4–5%. Management emphasized that the shortfall stemmed from timing shifts—not demand loss—with about a third of delayed large deals closing early in Q3. Meanwhile, distributed infrastructure grew 37%, and backlog reached a record high of $500 million, partly offsetting weakness in traditional mainframe segments.

This week, while no new earnings report has emerged, investors are closely watching whether Q3 deals continue to close and if infrastructure demand stabilizes—especially since management framed the Q2 miss as transient. Any early signs of deal execution improving in consulting and infrastructure could shape sentiment and valuation amid this recovery phase.

What To Watch Now

– The pace at which delayed Q2 deals finalize in Q3, particularly within consulting and infrastructure.

– Strength in distributed infrastructure, including Power and storage, which registered its strongest growth last quarter.

– Any updates on IBM’s software segments like Red Hat, watsonx and HashiCorp—recent results showed sustained growth in recurring revenue, contributing to more defensive earnings.

For investors, the central question is whether IBM’s recovery narrative can regain traction following the infrastructure-driven Q2 slowdown. With $500 million in backlog and management confident that demand remains intact, the coming weeks will be critical in testing whether the execution reset sticks—or whether client capex reprioritization continues to pressure IBM’s mix.