Bot Traffic Overtakes Human Traffic in 2024 as AI Agents and Scrapers Surge
The theory of a so-called dead internet has circulated since at least 2014, but recent data shows automated traffic is indeed overtaking human activity. Anti-detect browser company Aurorium examined traffic composition from 2013 onward and concluded that bots now hold a majority share in many segments.
Modern internet traffic consists of human users who create content and drive searches, plus bots divided into good, bad, and gray categories. Good bots include search engine crawlers, uptime monitors, news aggregators, and social media bots. Bad bots range from simple scripts to advanced tools that rotate fingerprints, use proxies, and mimic human mouse movements. Gray bots encompass AI agents and neural crawlers whose long-term value to webmasters remains unclear.
Imperva statistics illustrate the shift. Human traffic stood at 57 percent in 2013, dipped in 2014 due to good-bot indexing, then recovered through 2019 as smartphone adoption and 4G networks brought hundreds of millions of new users from Asia. From 2020 onward, pandemic-driven automation reversed the trend. By 2023 human traffic had fallen to 50.4 percent while malicious bots climbed to 32 percent.
The acceleration continued after generative AI tools lowered the barrier to creating scrapers. In 2024 human traffic dropped below 50 percent for the first time, reaching 49 percent against 51 percent automated. Latest figures show humans at 47 percent and bots at 53 percent, with the majority of bot activity classified as harmful scraping rather than beneficial indexing.
Additional sources align with these findings. Cloudflare reports that automated requests account for 37.5 percent of HTTP traffic, 87 percent of which originates from desktop environments. Akamai analyzed 6.9 billion requests and found 49.3 percent human, 42.1 percent bot-driven, and 65.3 percent of bot traffic tied to malicious scraping.
Within the bad-bot category, gray AI agents represent a fast-growing subset. AI crawlers comprise 85 percent of neural traffic while interactive AI agents account for 15 percent and are expanding at roughly 7 percent per year. These agents already compare prices, read documentation, and complete bookings with minimal human input.
Businesses bear an infrastructure tax from this traffic. A site that once handled 200 daily visitors may now serve 5,000, forcing upgrades to costlier hosting plans even though a large share of requests come from non-converting bots. For a digital property with 100 million monthly views and 30 percent bot traffic, annual server costs attributable to automation can exceed $19,000, excluding expenses for CAPTCHA services.
Site owners face difficult choices about blocking AI crawlers. Aggressive filtering risks losing legitimate mobile users sharing the same carrier-grade NAT addresses. At the same time, media organizations such as BBC and CNN that strictly limit AI access still achieve high citation rates in neural search results, suggesting that voluntary openness may not be required for visibility.
The cumulative data lends increasing weight to the dead-internet hypothesis. Human users are becoming a minority in the network they created, and recommendation systems trained on bot-generated patterns risk producing an increasingly synthetic information environment with no clear reversal in sight.
Related articles
Yandex Black October: How Architectural Flaws and Capacity Mismanagement Turned Data Center Losses Into a 11-Day Fintech Coma
In October 2026 three Yandex data centers in Central Russia were physically destroyed within days, triggering the collapse of Yandex Cloud and multiple core services. Between the first and third site failures engineers had 74 hours to restore quorum and rebalance workloads yet failed to do so because Control Plane components remained tied to the lost zone and spare capacity had been eliminated to cut costs. Core banking and BNPL systems entered Read-Only mode after losing quorum, forcing a complete stop-the-world reconciliation that lasted until 22 October. Backups stored inside the same regional S3 buckets proved unusable, resulting in a seven-day RPO and primary-key collisions after restoration. The incident exposed that Metro-Cluster designs had been incorrectly treated as full Disaster Recovery and that aggressive AP microservice patterns created logical split-brain conditions outside the database layer.
Astra Group Releases Low-Code Astra AI Platform for Building Corporate AI Agents in Closed Environments
Astra Group has launched the Astra AI Platform, a low-code constructor designed for creating corporate AI applications that operate entirely within closed circuits without reliance on foreign clouds. The platform targets small and medium businesses as well as large corporations, enabling rapid deployment of AI secretaries, technical support assistants, and other agents in days rather than months. It forms part of the broader Astra AI ecosystem and includes two main constructors: one for machine learning model training and deployment, and another for LLM-based language assistants, document search, and process automation. Users can assemble scenarios from visual blocks, debug them in real time, or extend functionality with custom Python code when needed. The solution supports RAG-based knowledge bases, integration with external tools such as CRM and ERP systems, and the coordination of multiple agents for distributed task handling. One demonstrated use case involves processing ten pages of engineering drawings and specifications in five minutes to prepare data for downstream systems. The product is already listed in the Russian domestic software registry and available to customers.
Multi-Tenancy Isolation in VictoriaMetrics, VictoriaLogs and Grafana: Building Client Separation in a Shared Stack
Voltir runs a single shared monitoring stack consisting of VictoriaMetrics, VictoriaLogs, Grafana and vmalert for all customers instead of deploying separate instances per tenant. Isolation relies on numeric account IDs enforced at every layer: nginx validates tokens against the platform API before proxying writes, Grafana data sources hard-code tenant accounts, and vmalert rules receive automatic account filters. The team discovered that a single malformed rule or template could break alerting for every tenant because vmalert loads the entire rules directory at once. They also found that Grafana automatically created personal organizations granting Org Admin rights, accumulating hundreds of orphaned organizations and users that consumed disk space and resources. A dedicated cleanup module plus hourly reconciliation now removes rules, organizations, series and users when a tenant is deleted, while isolation tests verify both data and API objects across tenants.
The Real Costs of Using Claude and GPT for Russian Businesses Exposed
Accessing generative AI models like Claude and GPT has become straightforward for Russian companies, yet calculating their true expenses remains complex. Hidden factors such as intermediary commissions, currency conversion rates, taxes, and the often-overlooked costs of model reasoning tokens can double or triple initial estimates. Founder Vitaly Nagay of the Heli service analyzed these financial and organizational risks for Russian firms relying on foreign AI providers. In one example, a support department processing 20,000 monthly queries sees costs rise from $240 to $480 when reasoning tokens are included. Nagay recommends evaluating providers by dividing actual ruble charges by the model's official dollar pricing to reveal hidden markups. Additional concerns involve data control, document compliance, and access history when employees use personal subscriptions. Companies are advised to verify billing details, data storage policies, and issue dedicated API keys with spending limits before procurement.