An Update on Wayback Machine Access
The Internet Archive has implemented new protections for the Wayback Machine to manage high-volume automated traffic. These measures occasionally result in legitimate users being blocked with 429 errors, for which the organization has apologized. Users who believe they were blocked in error are encouraged to contact the archive with specific technical details for review.
- ▪The Wayback Machine is experiencing waves of high-volume automated traffic that require protective measures.
- ▪A recent update changed the message displayed when a request is blocked with a 429 error code.
- ▪The current protections sometimes mistakenly block real users who depend on the service.
- ▪Users who were blocked in error can email [email protected] with their operating system, browser, and IP address.
- ▪Mark Graham, the Director of the Wayback Machine, posted this update on September 15, 2026.
Hacker News (Front Page) files mainly under programming. We currently carry 1,689 of its stories. Top-voted stories on Hacker News.
Story provenance
Source · retrieval · rights · ranking — open for full record
inspect →
Story provenance
Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.
Record
| Original publisher | Archive |
| Canonical URL | https://blog.archive.org/2026/09/15/an-update-on-wayback-machine-access/ |
| Publication time | Tue, 15 Sep 2026 17:52:18 +0000 |
| Retrieval time | 2026-09-15T18:26:52.506Z |
| Last seen | 2026-09-15T18:26:52.506Z |
| Headline source | Publisher (no WeSearch rewrite) |
| Excerpt source | publisher body |
| Excerpt method | First ~120 words (~800 chars) of extracted publisher body, fair-use limited. |
| Summary | WeSearch · cerebras-chat (WeSearch summarizer) |
| Summary source text | contentText |
| Citation coverage | Summary is a WeSearch-generated derivative; primary citation is the original publisher URL. |
| Cluster | BNIFoN9_JrG9 · 1 stories |
| Cluster logic | Grouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison. |
| Ranking reason | Story pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking. |
| Publisher visit | Yes — open original |
| Substitutes article? | No — link-out required for full text |
Rights status (four layers)
WeSearch handling by dimension
| Indexing | May the item be indexed (stored, ranked, made findable)? | Allowed |
| Snippet | May a short excerpt of the publisher's text be shown? | Allowed |
| AI summary | May WeSearch generate its own short summary of the article? | Limited |
| Retrieval / RAG | May the content be exposed for third-party retrieval-augmented generation? | Not asserted |
| Model training | May the content be used to train AI models? | Not asserted |
| Commercial reuse | May the content be reused commercially? | Not permitted |
Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.
Opening excerpt (first ~120 words) tap to expand
An Update on Wayback Machine Access Posted on September 15, 2026 by Mark Graham We’ve heard you: “Fix the Wayback Machine!” Here’s what’s going on. The Internet Archive’s Wayback Machine has been hit by waves of high-volume automated traffic, and we’ve put protections in place to keep the service running. One recent change: we rewrote the message you see when a request is blocked with a 429 error — the HTTP code that means “too many requests.” Those protections sometimes catch real people by mistake. If that’s happened to you, we’re sorry, and we appreciate your patience while we work to reduce the errors. We’re getting better at telling abusive bots apart from the people who depend on the Wayback Machine every day.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at Archive.