Skip to content
The AI-First Web

Cloudflare Says Automated Traffic Passed Human Traffic in May 2026

Cloudflare's founders' letter puts the crossover more than a year ahead of its own second-half-2027 forecast.

W
WebPulse Newsroom
AI-assisted · 4 min read
Share on X LinkedIn
Cloudflare Says Automated Traffic Passed Human Traffic in May 2026

AI-generated image for WebPulse. About our images

In brief
  • Cloudflare's founders' letter of September 27 says automated traffic passed human traffic in May 2026, over a year before its own forecast of late 2027. The letter shows no data or method.
  • Cloudflare warns agents may re-fetch unchanged pages and favor long-established businesses, which could hurt newcomers. The letter calls these risks and cites no data showing either is already happening.
  • Cloudflare sells products for this problem, so weigh the claim accordingly. If bots are near half your traffic, check your bandwidth, CDN and analytics assumptions, and measure your automated share.

Cloudflare's forecast said 2027; it says May 2026

Cloudflare's 2026 Annual Founders' Letter, published September 27 to mark the company's 16th birthday, says automated traffic has already passed human traffic. Its earlier projection placed that milestone in the back half of 2027. Growth in agents and AI crawlers, the letter says, moved it to May 2026, more than a year ahead of schedule. It is a claim the letter makes without showing its data or method.

The repeat-visit problem

Cloudflare frames the cost of agent traffic as a tragedy-of-the-commons risk. An agent picking a lunch spot might read 1,000 local menus and recommend one; the other 999 restaurants serve those requests for nothing. The letter says agents inherit the search-engine habit of re-downloading pages on every pass, changed or not. Cloudflare says its own figures point to a majority of what well-behaved crawlers pull down being identical to what they saw on their previous visit. If that holds, much of that fetching is redundant. The letter does not say how much of total traffic those bots represent.

The risk: agents default to whoever they know best

The letter's second concern is discovery. Cloudflare argues that an agent has no loyalty to a neighborhood deli. Per the letter, it leans toward the businesses it knows most about, and those tend to be the longest-established. Cloudflare presents the consequence as a risk: as agents handle more commerce, new entrants may find it harder to break in, which the letter says is likely to lead to consolidation. That is a warning, not a measured effect, and the letter cites no data showing it is already happening.

A vendor's letter, a projection, and no stated method

Budget-holders should weigh the source. The same letter announces Cloudflare's own work on crawlers that fetch only what is new, and a way for content owners to get paid when agents use their material. Cloudflare also says the majority of "vibe coding" tools use its developer platform as their preferred deployment target, and that more than 7 million developers build on it. The company has a stake in the problem it describes. The letter also does not explain how "automated traffic" is defined or measured.

The forward-looking claim is a projection too. Cloudflare's five-year extrapolation puts automated traffic at 1,000 times human traffic, assuming present trends hold. It attributes that to agent growth, not to any fall in human traffic.

The letter describes the crossover as a shift in who uses the Internet; it does not say what any single site's traffic mix looks like. This is WebPulse's reading, not Cloudflare's argument. If automated traffic is even close to half of your inbound requests, budgets built on human-visitor assumptions deserve a second look. That covers bandwidth and CDN charges, origin capacity, and analytics that treat every visit as a person.

What to ask your team

Start with measurement. What share of inbound traffic to our properties is automated today, and how do we know? Are automated requests billed differently from human ones under our hosting and CDN contracts? How much of that load is repeat fetching of unchanged pages, and does our origin bear it or a cache? Which of our analytics and conversion metrics would shift if bot traffic were filtered out? Finally, separately from SEO, is our content structured so an agent comparing options can find and cite us, or does our position rest on the human familiarity the letter says agents do not weigh?

Produced by the WebPulse Newsroom with AI assistance from the original reporting credited below, and checked against that source by our editorial review. How we use AI.
Original reporting: Cloudflare.