Cloudflare

$696.1 million in Q2 revenue, up 36% year over year, coincided with Cloudflare’s shift from web infrastructure toward tools and access controls for AI agents and bots.

Who they are

Cloudflare appears in coverage as an internet-infrastructure company led by CEO Matthew Prince, associated with DDoS protection, DNS, web delivery and its Workers serverless platform. Its stories span the operational consequences of being infrastructure for major online services, security and moderation decisions over whom to protect, and an expanding role in AI-facing developer tools.

The recent arc

Coverage reached its recent high in 2026Q2, driven by an unusually mixed set of operating, financial and strategic stories. A June Google Cloud outage disrupted Cloudflare and other customers including Spotify, Discord and Snapchat; in May, Cloudflare reported Q1 revenue growth while saying it would cut more than 1,100 jobs to architect the company for the “agentic AI era”; and August reporting put Q2 revenue at $696.1 million, 36% above the prior year, alongside a larger net loss and an above-estimate Q3 outlook.

The subsequent phase has centered on turning Cloudflare’s network and Workers footprint into AI-agent infrastructure. It launched Kitesurf, a cloud-hosted browser for agents, joined Vercel in adding Jev for AI tool selection, and introduced open-weight multimodal decision models Clef and Clef-flash. Prince’s September interviews also put bot traffic, a revival of HTTP 402 as a way to charge bots for web access, and blocking Google at the center of the company’s public agenda.

The tension

The coverage increasingly circles a conflict between the open web’s dependence on automated discovery and Cloudflare’s effort to give site operators more leverage over automated traffic. Google is the clearest counterparty in the recent reporting, while HTTP 402 and agent products such as Kitesurf frame Cloudflare not just as a traffic intermediary but as a prospective gatekeeper and service provider for AI bots; that sits alongside its longstanding DDoS-protection role and the reputational scrutiny that comes with deciding which sites receive protection.

Why it matters

If this trajectory holds, Cloudflare could become a consequential control point in how AI agents access, pay for and act on the web, linking bot governance to developer infrastructure and its core network business. The opportunity is balanced by execution and reliability risk: the same coverage records service disruptions affecting Cloudflare and customers, job cuts during the AI transition, and a widening quarterly loss even as revenue grew. Whether publishers, platforms and developers adopt its proposed access mechanisms remains unresolved.

Related: Matthew Prince · Google · DDoS · AI · Cloudflare says “a fix has been implemented and we believe the inciden