Cloud spend hit $143B in Q2. GenAI services grew 165%.

Global cloud spending just posted its fastest growth in eight years, and the reason is a line item that barely existed on your bill two years ago. Synergy Research Group put Q2 2026 enterprise spend on cloud infrastructure services at $143.4 billion, up 43% year over year. Inside that number, GenAI cloud services grew 165%. If your cloud bill feels like it's moving faster than your headcount, that's why.

What actually happened

Synergy's Q2 numbers, published July 30, put the trailing-twelve-month cloud infrastructure services market at roughly $500 billion. Amazon holds 28% worldwide share, Microsoft 20%, Google 15% — but Microsoft and Google are growing meaningfully faster than Amazon, so the ordering at the top is more stable than the momentum underneath it. Chief Analyst John Dinsdale's framing was that "AI technology has lit a fire under the cloud market."

The Register's read is that this is now the eleventh straight quarter in which the growth rate itself increased — not just the revenue. That's the part worth sitting with. A market growing 43% on a $500B base, accelerating, is not a market where anyone is competing on price.

Why cloud costs matter for your business

Here's the operator translation: the discount pressure you were waiting for isn't coming. Providers selling into 43% demand growth do not cut list prices. They add SKUs.

And that's the real risk for a small business. The 165% GenAI number isn't a headline about hyperscalers — it's a description of what happens to a bill when a new class of metered service lands inside a platform you already use. Token charges, agent gateway charges, evaluation charges, memory and session charges. Each one is small. None of them show up as "AI" on the invoice. They show up as a bigger cloud bill and a shrug.

Three things we do about it on every build. Tag AI spend at the resource level so the model layer is a separate line you can actually read, not a rounding error buried under compute. Price the work, not the tokens — know what one processed order, one drafted reply, one enriched record costs you, because that's the number that tells you whether the automation pays. Don't sign multi-year commits against a line growing triple digits; your usage profile in 18 months will not look like today's, and neither will the cheapest way to serve it.

The single best hedge is portability. If your automations call a model through an interface you control, repricing is a config change. If they call one vendor's proprietary agent runtime, repricing is a rebuild.

Sources: Synergy Research Group, The Register.