The Internet has a second audience
- ID
- 30287
- Status
- summarized
- Published
- 30 Sep 2026, 8:58 PM
- Fetched
- 30 Sep 2026, 9:59 PM
- Provider
- Cloudflare Blog
- Category
- infrastructure
- Original URL
- https://blog.cloudflare.com/agentic-web/
- Source URL
- https://blog.cloudflare.com/rss/
Summary
- Score
- 7.5
- Created
- 30 Sep 2026, 10:00 PM
- Tags
- Audience
- developersvibe_coderssaas_founders
What happened
Cloudflare reports that for the first time more than half of the traffic on its network is not human: it handled ~63M HTTP requests/second at the end of 2024 and now averages ~115M with peaks above 150M, while daily requests from AI agents grew over 1,700% in a year. Heavily crawled categories (Retail, Computer Software, IT & Services, Financial Services) have seen human traffic drop by as much as 40% in under a year, and crawler requests stated as AI training rose from 22% in Spring 2025 to 52% by June 2026. The post argues that blocking everything is not nuanced enough and that sites need to serve and capture value from agent visitors.
Why it matters
If your site's economics depend on ad impressions, referrals, or subscriptions, the post's numbers say a large and growing share of your bandwidth and origin capacity is now consumed by requests that produce no referral and no payment, with human traffic in some categories down as much as 40%. The concrete decision it forces is how you treat crawlers and agents by class rather than as one blob: training crawlers (52% of stated crawler purpose by June 2026, up from 22%) versus agents acting for a real person, since the post itself says a blanket block is no longer sufficient. Note this is Cloudflare's own blog arguing for a problem its products address, so treat the framing as vendor positioning and the request-volume figures as their network's data, not the whole internet's.
Discussion angle
Split your own traffic logs into human, agent, and stated training-crawler buckets and see whether the human share matches Cloudflare's numbers — then argue over what you'd actually do differently for a request that has a person behind it versus one that doesn't.