CoreWeave’s demand story is easy to see in its latest filing. The harder number is sitting below operating income: $640 million of net interest expense in one quarter.
CoreWeave Q2 2026 revenue reached $2.575 billion, up from $1.212 billion a year earlier. That is roughly 112% growth by Musthave.ai’s calculation. The same quarter produced a $626 million net loss and $640 million of net interest expense.
Those numbers are not a verdict on whether AI infrastructure demand is real. They show that demand, financing, and construction have to be read together. A buyer choosing a cloud partner should care about all three.
The quarter in four numbers
| Q2 measure | 2026 | 2025 | What changed |
|---|---|---|---|
| Revenue | $2.575B | $1.212B | Up $1.363B; about 112% |
| Net loss | $626M | — | The business remained loss-making |
| Net interest expense | $640M | $267M | Up $373M, or 140% |
| Quarterly sensitivity to a 100bp rate move | About $30M | — | Based on June 30 floating-rate debt |
Net interest expense was slightly larger than the net loss. That does not mean interest alone “caused” the loss; the income statement includes other operating and non-operating items. It does show how strongly financing costs now shape the result.
The rate sensitivity is a useful stress test
CoreWeave says that, based on its floating-rate debt at June 30, a 100-basis-point increase or decrease in rates could change quarterly interest expense by about $30 million. Over six months, the disclosed sensitivity is about $61 million.
That is a scenario estimate, not a forecast. Debt balances, hedges, repayments, and new financing can change the result. It is still a cleaner way to think about the business than watching the stock after earnings: capacity is being funded before all of its revenue arrives, and the cost of that funding is material.
Liquidity is large and partly restricted
The filing reports $5.5 billion of cash, cash equivalents, and marketable securities at June 30, plus $1.4 billion of restricted cash and cash equivalents. Restricted cash is not the same as money freely available for any operating need. CoreWeave says it primarily consists of bank deposits tied to a collateralized loan facility.
For a customer, the practical question is not “does the company have billions?” It is how much committed capital, power, hardware, and working cash support the specific region and service you plan to use.
Customer concentration changed shape, not relevance
CoreWeave says its top three customers represented about 36%, 26%, and 10% of Q2 revenue. A year earlier, its top customer represented about 71%. The distribution is broader, but three customers still accounted for roughly 72% of the quarter.
Concentration can support rapid expansion because large commitments justify large builds. It also creates renewal and bargaining risk. Buyers should read supplier resilience and customer concentration as two sides of the same capacity plan.
What an AI infrastructure buyer should ask
- Which capacity is contracted for us? Get region, accelerator, network, delivery date, and remedy in writing.
- What survives a financing delay? Separate live capacity from planned construction.
- How portable is the workload? Test images, orchestration, checkpoints, data movement, and observability on a second provider.
- Where is the concentration? Your own dependency can be dangerous even if the supplier diversifies its customer base.
- What is the exit cost? Include egress, retraining, reserved commitments, and engineering time.
Our model-selection framework treats operational fit as part of quality. The same logic applies to infrastructure. And the proposed CME compute futures story is a useful companion: hedging a rental index does not remove provider or capacity risk.
My verdict: growth is proven; durability still needs work
CoreWeave more than doubled quarterly revenue on the exact filed numbers. That is strong evidence of demand. The filing also shows the price of building ahead of that demand: a large loss, a large interest bill, substantial restricted cash, and a still-concentrated customer base.
Builders do not need to avoid the platform on these figures alone. They do need to treat cloud selection as counterparty engineering. Benchmark the GPUs, then test portability, delivery commitments, and the failure path if a planned cluster arrives late.
Read the filing
- Review CoreWeave’s Q2 2026 Form 10-Q.
Checked August 12, 2026. Dollar figures and customer shares are from CoreWeave’s SEC filing. The 112% revenue-growth figure and 72% top-three sum are Musthave.ai calculations using the reported values.
