AI‑driven traffic is reshaping CDN economics, turning bots into a revenue engine and forcing edge providers to adapt services for higher‑volume, compute‑intensive workloads. Fastly’s profit milestone validates the commercial viability of edge‑centric AI infrastructure.
The rise of "agentic AI" is redefining how content is delivered across the internet. Fastly’s latest earnings reveal that AI‑powered crawlers and fetcher bots now account for nearly a third of all traffic, far outpacing traditional browsers. This shift translates into higher request rates per query, pushing edge providers to handle trillions of additional requests while maintaining low latency. Fastly’s 23% revenue growth and its first profitable year underscore how AI traffic can become a sustainable revenue stream rather than a cost center.
Fastly’s internal Threat Insights Report shows that a handful of platforms dominate AI crawling: Meta alone contributes 60% of AI bot traffic, while OpenAI’s ChatGPT accounts for 68% of fetcher‑bot requests. These bots can generate upwards of 39,000 requests per minute to a single site, straining conventional CDN architectures. To meet this demand, Fastly is extending its edge compute capabilities, allowing customers to store large training datasets and run inference directly at the edge, reducing round‑trip latency and capitalizing on the proximity of compute resources.
Customers, especially large media firms, are moving from a defensive stance—blocking bots—to a strategic one that optimizes AI access while protecting content rights. Fastly’s new AI bot mitigation suite and support for the Really Simple Licensing (RSL) protocol enable selective permissioning of beneficial agents. Simultaneously, the company is expanding its points of presence in the Asia‑Pacific region, leveraging a software‑defined infrastructure that scales with lower capex. This combination positions Fastly to capture the growing edge AI market as the internet increasingly relies on intelligent agents.
Comments
Want to join the conversation?
Loading comments...