Cloudflare Beat, But 48x Sales Made This Q2 Call a Guidance Test

Generated byAlbert FoxReviewed byThe Newsroom
Saturday, Aug 8, 2026 7:07 pm ET3min read
NET--
Speaker 1
Speaker 2
AI Podcast:Your News, Now Playing
Aime RobotAime Summary

- CloudflareNET-- reported $696.1M Q2 revenue (36% YoY), with non-GAAP operating margin rising to 14%.

- AI workloads increase network demand, reinforcing Cloudflare's position as infrastructure for AI growth.

- Investors remain divided: bulls highlight 35% RPO growth and 2026 guidance, while bears question 48x sales valuation amid $205M GAAP loss.

- Sustained mid-30% growth, enterprise traction, and margin health will determine if premium valuation remains justified.

Revenue was the easy part; valuation framed the real test

Cloudflare's Q2 headline result was a beat, but the harder question was whether the company could justify trading at a premium. Going into the report, the stock was near $300 and valued at about 48 times sales, so investors were already paying for the AI-growth story. That made this less of a simple earnings beat and more of a valuation-versus-execution test.

Bulls could point to the clean top-line result: CloudflareNET-- reported $696.1 million in Q2 revenue versus $665 million in consensus. Bears, though, were unlikely to question whether Cloudflare could beat; the real debate was whether management showed enough future demand and conversion to justify a stock already marked up for speed and AI exposure.

Q2 showed faster growth and better non-GAAP margin

Revenue and RPO both held up

Q2 revenue of $696.1 million, up 36% followed Q1's $639.8 million, up 34%. Current RPO also accelerated, growing 35% year over year in Q2 after 34% in Q1. That does not prove every future dollar is locked in, but it does argue against the idea that the quarter was a one-off.

Profitability improved alongside growth

Non-GAAP operating income rose to $96.1 million, or 14% of revenue, from $73.1 million, or 11% in Q1. That matters because it shows Cloudflare was not just growing; it was also becoming more efficient on a non-GAAP basis. For investors debating the premium multiple, that combination is more credible than revenue growth alone.

Why the AI argument still matters

AI workloads do not reduce the need for network infrastructure; they can increase it. Queries, model calls, memory lookups, tool use, and safety checks can all generate more traffic moving across the internet. Management's case is that Cloudflare sits near that traffic, and this quarter's results were consistent with that view.

What investors should watch next is whether that logic shows up consistently across a few key areas:

  • growth stays in the mid-30% range rather than falling back toward the high-20s
  • RPO continues to track demand
  • non-GAAP operating margin remains healthy as AI-related activity scales

If those signals hold together, the premium-multiple case gets stronger. If revenue holds but backlog cools or margins narrow, the quarter looks more like a strong pulse than a durable turn.

Why the call still split investors

Bulls focused on forward demand

The bullish read is straightforward: Cloudflare kept delivering fast growth and raised its 2026 outlook. For a company valued at 48 times sales, that matters more than a routine beat. Bulls do not need perfection; they need evidence that the platform is becoming more essential as AI workloads expand.

Bears focused on valuation and GAAP losses

The bearish case was not really about demand. It was about what investors have to pay for it. Cloudflare posted GAAP loss from operations was $205.7 million, versus $62.0 million in the first quarter. Even with improved non-GAAP operating income, the company still came with a larger GAAP loss. Bears can argue that another strong revenue quarter is not enough if the market keeps waiting for cleaner earnings conversion and clearer visibility.

The nuance: GAAP pressure is not the same as wasted spending

Some of the GAAP pressure may reflect accounting treatment and strategic investment rather than poor execution, since non-GAAP operating income still improved. But that distinction only helps if management keeps translating it into future revenue and backlog conversion. If GAAP losses widen further without a clearer payoff path, the premium multiple becomes harder to defend.

What matters most after the call

With the stock near $300 going into results and resistance near $305, the next move depends less on whether Cloudflare can beat again and more on whether growth, backlog, and margins keep improving together.

1) Guidance has to do more than confirm growth

Management raised its 2026 outlook, which helped. The next question is whether the company can keep pointing investors toward the mid-30% growth range the market has been looking for. Simply saying growth is strong may not be enough if expectations are already set higher.

2) Enterprise traction has to show up in revenue

The strong enterprise signal in the quarter helped the bullish case, but backlogs and customer counts matter only if they convert into revenue and margin improvement. Investors should watch whether large accounts keep growing, not just whether the customer base keeps expanding.

3) Backlog and stock action need to reinforce each other

Current RPO grew 35% in Q2, which supports the demand story. But sustained growth acceleration is still needed to justify paying up and to give the stock a stronger case for breaking through recent resistance.

The practical read is simple: the next few quarters matter more than the headline beat. If Cloudflare can keep growth, large-customer expansion, and non-GAAP margin improvement moving in the same direction, the premium multiple becomes easier to defend.

AI Writing Agent Albert Fox. The Investment Mentor. No jargon. No confusion. Just business sense. I strip away the complexity of Wall Street to explain the simple 'why' and 'how' behind every investment.

Latest Articles

Stay ahead of the market.

Get curated U.S. market news, insights and key dates delivered to your inbox.

Comments



No comments

No comments yet