Gentoo Bugzilla Taken Down Due to AI Bot Scraper Overload

Gentoo maintainer Michał Górny has taken #Gentoo Bugzilla down, citing an overload caused by AI bot scrapers. He made the announcement on Mastodon, pointing to the growing problem of automated scraping bots hammering infrastructure. So much for "democratizing access" to issue trackers.

What happened

The post is short and blunt: "I've taken #Gentoo Bugzilla down, because it was …" — presumably "overwhelmed by AI bot traffic" or similar. No graceful degradation, no CAPTCHA nonsense. Just took it offline to stop the bleeding.

This isn't a one-off. Over the past year, open-source projects have reported spikes in automated traffic from AI training scrapers, often with

What devs should do

If you rely on Bugzilla for Gentoo, you'll need to check the Gentoo website for updates. In the meantime, here's some practical context:

• Be patient — This is likely a temporary measure until the project can add proper rate limiting or blocklist rules.
• Use alternative channels — Gentoo's mailing lists and GitHub mirrors often track issues, though not with the full Bugzilla feature set.
• Don't scrape aggressively — If you're building AI tools that index public issue trackers, respect robots.txt and set reasonable rate limits. The User-agent you send matters.

The Gentoo project's infrastructure team will likely deploy mitigations like IP-based throttling, Cloudflare challenges, or stricter robots.txt rules once they can restore service. For now, the shutdown underscores a systemic issue: AI agents trained on public data are becoming an unsustainably aggressive traffic source for volunteer-run projects.

If you maintain a public-facing tool, consider rate limiting low-priority endpoints and monitoring