A woman at a small Tokyo web agency looks at a wide monitor showing a rising traffic graph while a colleague points at it, with server racks behind glass and the city in the window (AI-generated image)

Cloudflare CEO: AI Agent Traffic Could Make Websites 1,000× More Expensive to Host

Key takeaways

Matthew Prince says bot traffic will reach 1,000× human traffic and a $3.17 site could cost over $3,000 to host. What he said, Cloudflare's data, and what to do.

Cloudflare's chief executive, Matthew Prince, says automated traffic from AI agents and crawlers will reach about 1,000 times human traffic within five years, and that the economics of running a website will not survive that unchanged. His example, repeated on the Big Technology Podcast in September and on Cloudflare's Q3 2026 earnings call on Nov 5, is a WordPress host whose site costs $3.17 to run and sells for $12.99. Scale the traffic 1,000 times and, in his words, it would cost "over $3,000" to host. Here is what Prince actually said, what Cloudflare has built in response, what Cloudflare's own data shows, and what a small company in Japan can do about it this month.

Key facts
  • The claim: automated traffic online will be about 1,000 times human traffic (Prince, Big Technology Podcast, Sep 2, 2026). He says the crossover, when bots overtook humans, came in May 2026.
  • The example: one large WordPress host pays about $3.17 to host a site and charges about $12.99. At 1,000 times the traffic, Prince says, hosting it would cost over $3,000. The host is not named, and the figures are his illustration, not a forecast of any bill.
  • The restaurant problem: an agent may read 1,000 restaurant menus to recommend one; the other 999 paid for the server time and got nothing (Cloudflare's 2026 Founders' Letter and the Q3 call).
  • What Cloudflare sells against it: AI crawlers blocked by default and a Pay Per Crawl gateway (July 2025), a research pilot with OpenAI on page-change signals (July 2026), and a push toward serverless, cached architectures.
A woman at a small Tokyo web agency looks at a wide monitor showing a rising traffic graph while a colleague points at it, with server racks glowing behind glass and the city skyline in the window
Traffic going up with no customers behind it. AI-generated image (ChatGPT), not a photo of a real company.

What Prince said, and where

The numbers come from Prince's own mouth on a podcast, not from a Cloudflare press release. On the Big Technology Podcast on Sep 2, 2026, he said automated traffic online "will be a thousand times what human traffic is", that one of the largest WordPress hosts "costs us about $3.17 to host a website" and "we charge like $12.99", and that at 1,000 times the traffic "it would cost us over $3,000 to host that website". He also said WordPress runs on PHP, "not the most efficient programming language", and that some fundamental web technologies have to change. He made the same argument on The Verge's Decoder podcast on Sep 26 and in Cloudflare's 2026 Founders' Letter on Sep 27, which is where the restaurant example appears: an agent "may survey 1,000 restaurant menus in the area only to suggest one". On the Q3 2026 earnings call on Nov 5, he put it as 999 of those restaurants now having a cost, as The Register reported.

Graphic showing a site that costs $3.17 to host and sells for $12.99 today, an arrow marked 1,000 times automated traffic in five years, and a red panel reading over $3,000 with Prince's quote
The unit economics Prince quoted, as he described them. The hosting provider is not named; the $3,000 figure is his illustration.

A caution on the arithmetic. The $3.17 figure is one provider's cost today; $3,000 is what Prince says it would become if cost scaled linearly with traffic. Real bills depend on caching, bandwidth pricing and how much of the extra traffic ever reaches the application server. Prince himself said the outcome would be "hundreds to thousands of dollars" depending on optimisation. Treat the 1,000 times figure as Cloudflare's projection and the $3,000 as a worked example, not a measurement.

Grid of 200 blocks, one green and the rest red, with panels reading 999 pay server and bandwidth and get no customer, and 1 gets the customer
Prince's example: an agent reads 1,000 menus and books one table. Each block is five restaurants.

What Cloudflare's own data shows

Cloudflare publishes crawler statistics on its Radar site. In July 2025 it reported "crawl-to-refer" ratios, the number of pages a platform crawls for every human visit it sends back, of about 5.4 for Google, 1,091 for OpenAI, 38,066 for Anthropic and 195 for Perplexity (Cloudflare blog). The ratio is the heart of Prince's argument: a search engine that crawls five pages and sends one visitor is a trade; a crawler that reads tens of thousands of pages per visitor is a cost. Current figures move week to week and are on Radar's AI Insights page.

Table of crawl-to-refer ratios published by Cloudflare for July 2025: Google 5.4 to 1, OpenAI 1,091 to 1, Anthropic 38,066 to 1 and Perplexity 195 to 1
Crawls per human visit sent back, July 2025, as published by Cloudflare. Current figures are on Cloudflare Radar.

We looked at Radar on Nov 18, 2026. For the seven days to Nov 17, the five most active AI bots on Cloudflare's network were Googlebot (25.3% of the top-five's requests), ClaudeBot (12.1%), Applebot (8.6%), GPTBot (8.1%) and Bingbot (8.1%). That is Cloudflare's view of its own network, which carries a large share of the web but not all of it.

Screenshot of Cloudflare Radar's AI Insights page showing a line chart of HTTP traffic by bot for Nov 11 to 17, 2026, with Googlebot at 25.3%, ClaudeBot 12.1%, Applebot 8.6%, GPTBot 8.1% and Bingbot 8.1%
Our screenshot of Cloudflare Radar, AI Insights, taken Nov 18, 2026 (last 7 days). Chart © Cloudflare, Inc., reproduced for reporting purposes.

The same page gives the current crawl-to-refer ratios, which have shifted a long way since July 2025. For the seven days to Nov 17, 2026, Radar showed Perplexity at about 3,300 crawls per referral, OpenAI 1,800, Anthropic 450, Mistral 192, Baidu 37.6, Microsoft 34.8, Yandex 20.4, ByteDance 11.2, Google 3.3 and DuckDuckGo 1.6. Anthropic's ratio has fallen sharply from the 38,066 Cloudflare reported in 2025, while Perplexity's and OpenAI's have risen. Cloudflare notes that Radar counts HTML page requests only and that a referral is a visit that arrives with the platform as the referrer, so ratios for assistants that open links without a referrer are inflated.

Screenshot of Cloudflare Radar's crawl-to-refer ratio panel for the week to Nov 17, 2026: Perplexity 3.3K to 1, OpenAI 1.8K to 1, Anthropic 450.4 to 1, Mistral 192 to 1, Baidu 37.6 to 1, Microsoft 34.8 to 1, Yandex 20.4 to 1, ByteDance 11.2 to 1, Google 3.3 to 1, DuckDuckGo 1.6 to 1
Our screenshot of Cloudflare Radar's crawl-to-refer panel, taken Nov 18, 2026 (last 7 days). © Cloudflare, Inc., reproduced for reporting purposes.

What Cloudflare has built in response

Timeline of five Cloudflare moves: Pay Per Crawl and default blocking on Jul 1, 2025; the OpenAI research pilot on Jul 8, 2026; the Big Technology Podcast on Sep 2, 2026; agent bots blocked on ad pages from Sep 15, 2026; and the Q3 earnings call on Nov 5, 2026
Eighteen months of Cloudflare moves on AI crawlers, from its blog, press releases and earnings materials.
  • Default blocking of AI crawlers (Jul 1, 2025). New Cloudflare domains block AI training crawlers unless the owner opts in (announcement). From Sep 15, 2026, training and agent bots are also blocked by default on pages that carry ads for new domains (update).
  • Pay Per Crawl (Jul 1, 2025, private beta). A site can answer a crawler with an HTTP 402 "Payment Required" response that states a price; Cloudflare acts as merchant of record and settles the micropayments (announcement). The pasted summaries circulating online call this a "monetization gateway", which is a fair description.
  • Page-change signals with OpenAI (Jul 8, 2026). Cloudflare announced a research pilot with OpenAI on "content freshness, traffic quality, and actual page changes" (press release). In October it reported results: change signals tell a crawler when a page is worth another visit, tested on about 1% of Cloudflare's network (blog).
  • Serverless and caching. Prince argues that container-based servers cannot keep up cost-effectively and that lighter runtimes such as Cloudflare Workers, plus aggressive static caching, are the fix. Cloudflare sells those products, so weigh the argument accordingly.
Cloudflare has an interest hereEvery solution on that list is a Cloudflare product or partnership, and the company reported Q3 2026 revenue of $782.5 million, up 39%, on the same call (results, SEC filing). That does not make the traffic numbers wrong; Cloudflare sees more of the web's bot traffic than almost anyone. It does mean the "1,000 times" framing is also a sales pitch.

What this means for a small company in Japan

Most Japanese small-business websites run on shared WordPress hosting or a page builder, often on a plan with a bandwidth cap. Those are the sites Prince's example describes. The practical questions are not about 2031; they are about whether your hosting bill or your page speed has already moved. A restaurant, clinic or shop whose menu, prices and opening hours are read by agents on behalf of customers is exactly the case he describes, and the honest answer is that you want agents to read those pages, cheaply, and you want the cost to be yours to control.

Checklist of five steps: measure bot traffic first, decide whether to block, allow or charge, cache aggressively, watch the hosting bill, and keep the pages agents need fast and accurate
Five things a site owner can do this month.
  1. Measure it first. Your analytics, server logs or CDN dashboard will show what share of requests and bandwidth is automated. Decide on numbers, not headlines.
  2. Decide: block, allow or charge. If you are on Cloudflare, the AI crawler controls and Pay Per Crawl are a few clicks. Everyone else has robots.txt, which well-behaved crawlers honour and bad ones ignore.
  3. Cache aggressively. A static page or image should be served from a cache, never by PHP, when a bot asks for it. This is the single biggest lever on the $3.17.
  4. Watch the hosting bill. Bandwidth overage is where extra automated traffic shows up first on shared plans.
  5. Keep the pages agents need. Menus, prices and hours should stay fast, static and accurate. Blocking agents from the page that wins you the booking is self-harm.

Want to know what AI crawlers are costing your site?

We measure bot traffic, set crawler rules and move heavy WordPress sites to cached, static builds for Tokyo businesses, in English and Japanese. Book a free consultation.

Book a free consultation

Sources

Big Technology Podcast, "Cloudflare CEO: We're ready to block millions of websites from AI", Sep 2, 2026 (transcript); The Verge, Decoder with Matthew Prince, Sep 26, 2026 (episode); Cloudflare, 2026 Annual Founders' Letter, Sep 27, 2026; Cloudflare Q3 2026 results, Nov 5, 2026 (SEC exhibit; call transcript); The Register, report on the call, Nov 6, 2026; Cloudflare blog posts on Pay Per Crawl and default blocking (Jul 1, 2025), ad-page blocking (Jul 1, 2026), crawl-to-refer ratios (2025) and the OpenAI pilot results (Oct 15, 2026); Cloudflare press release on the OpenAI pilot, Jul 8, 2026; Cloudflare Radar, AI Insights, viewed Nov 18, 2026. Graphics are our own. The Radar chart is our screenshot of Cloudflare's public page, © Cloudflare, Inc. The photo-style image was generated with ChatGPT and is not a photograph of a real company. IT Support in Tokyo is not affiliated with Cloudflare, OpenAI or WordPress.

Related: More tech news · Is WordPress safe after PHP2shell? · Migrating WordPress to Next.js

    Cloudflare CEO: AI Agent Traffic Could Make Websites 1,000× More Expensive to Host