An update on Wayback Machine access: Internet Archive tightens bot protections

The Internet Archive says its Wayback Machine has been hit by waves of high-volume automated traffic, and that it has put protections in place to keep the service running. In a short update published on September 15, the organization acknowledges that those protections sometimes catch real people by mistake, and apologizes to anyone affected.

What changed

The post, written by Mark Graham, says one recent change was a rewrite of the message users see when a request is blocked with a 429 error, the HTTP status code that means too many requests. It opens by acknowledging the message the organization keeps hearing from users: Fix the Wayback Machine.

The archive says it is getting better at telling abusive bots apart from the people who depend on the Wayback Machine every day, and that it is working to reduce the errors that hit legitimate visitors. No timeline is given for that work.

If you believe you were blocked by mistake

Users who think they were blocked in error are asked to email [email protected] with their operating system, browser and IP address, so staff can look into the case.

Why the traffic matters

The update does not say who is behind the automated traffic. Readers filled the comment thread, 27 comments at the time of writing, with their own theories: several suggested that large-scale scraping for AI training data is the likely cause, while others asked whether the load amounts to an attempted denial-of-service attack. VPN users reported being blocked frequently, and one commenter suggested the archive adopt Cloudflare-style protections.

The Wayback Machine is used by journalists, historians, lawyers and researchers to retrieve pages that have changed or disappeared, so access failures draw outsized complaints. The Internet Archive says it appreciates users' patience while it reduces the false positives.