Web Scrapers Overwhelm Linux Kernel Git Infrastructure
The official Git repository for the Linux kernel is spending more CPU power rendering HTML pages for automated scrapers than serving legitimate developers, highlighting the growing toll of web crawlers.

The official Git repository for the Linux kernel, git.kernel.org, is currently dedicating more CPU cycles to rendering commits for automated scrapers than to all forms of legitimate developer access combined, including standard git clones. According to systems administrator Konstantin Ryabitsev, the background radiation of abusive web crawlers has reached a point where 14 CPU cores across 5 geo-distributed nodes are constantly occupied doing nothing but rendering Git commits as HTML for scrapers.
This infrastructure strain highlights a growing crisis for open-source projects and public web platforms. As artificial intelligence companies and data brokers aggressively harvest training data, the sheer volume of automated traffic threatens to crowd out human users. For systems administrators and developers, this shift means that traditional web-serving architectures must now account for massive, non-human workloads that offer zero return on investment.
The issue extends beyond kernel hosting to any platform that serves large volumes of structured, crawlable data. Software developer Simon Willison noted that this trend is a major concern for projects like Datasette, an open-source tool designed to help users explore and publish data. Because Datasette serves a vast number of crawlable web pages, it faces similar vulnerabilities to aggressive scraping bots that index public databases without regard for server resources.
To mitigate these issues, practitioners are increasingly forced to implement aggressive rate-limiting, robust robots.txt configurations, and specialized bot-detection mechanisms. However, as scrapers become more sophisticated and distributed, maintaining open access to public code and data while protecting server infrastructure remains an escalating challenge for the open-source community.
This is our own summary of reporting by Simon Willison



