Wayback Machine outages and problems
In the past 24 hours, 16 user reports came in for Wayback Machine. Counting only the 15-minute windows with a spike big enough to count as an outage, that comes to 100.00% uptime for the day.
The busiest 15-minute window had 3 reports, about 4 hours ago. That stays below our outage threshold, so it doesn't count as downtime.
Wayback Machine in October 2026
- Problem reports in October (since 27 October)
- 20
Monthly report for October 2026
What people said was wrong in recent problem reports for Wayback Machine, as a share of those reports:
- 83% Website
- 17% App
Where Wayback Machine problem reports come from
Recent reports came from 5 areas. The most came from around Washington, DC, Los Angeles, CA and Boston, MA. Share of recent reports by area, named after its biggest town:
- 31% Washington, DC
- 15% Los Angeles, CA
- 8% Boston, MA
- 8% New York City, NY
- 8% Phoenix, AZ
From 13 recent problem reports. Big cities always send the most, so reports from many places point to a widespread problem, and one area far ahead of the rest can mean a regional one. Town names: GeoNames.
Wayback Machine problem spikes, last 30 days
Since 27 October, Wayback Machine had no outage spikes or periods of elevated reports.
A spike is a sharp rise in problem reports from users, kept exactly as this page showed it at the time. This history starts on 27 October 2026. Monthly reports for all services
How to fix Wayback Machine not working
Wayback Machine is up on our end, so if it won't work for you, the problem is most likely on your side. Work through these in order:
Your browser tries to reach web.archive.org over your own connection, right now. Nothing is sent to us or stored.
Retry the Capture Search
Load the archive tab again and search the exact page in the top search field. The calendar can look empty when that page has no captures for the chosen year, so switch to the year view and pick a nearby month before you call it a failure. If the tab stalls, stop the load, then start it once more.
Open the Archive in a Private Window
Open a private window and load the same archive page there: Chrome has three-dot menu > New Incognito window; Firefox has menu > New private window. If the archive loads there, an extension or saved cookie is breaking the normal tab.
Clear Site Data for the Archive
Delete the archive's cookies and site data in the browser's site settings, then reload the tab. In Chrome, click the lock icon left of the address bar, open Site settings, and click Delete data; in Firefox, click the padlock icon and choose Clear cookies and site data.
Test Another Network
Switch the device to a different connection: turn off Wi-Fi on your phone and load the archive over mobile data, or tether the laptop to the phone. If the page loads, your Wi-Fi router or provider is blocking the archive.
While Wayback Machine is down: what to use instead
- Archive.today Use it when you need a quick saved copy of a page and the URL is already known.
- Memento Time Travel Search several web archives at once with a URL when you need an older copy.
- Common Crawl This helps only if you can work with bulk crawl data and need to look beyond a single lookup.
- Browser cache Try it when you visited the page before; your browser may have a local copy, though images or scripts could be missing.
What happens when Wayback Machine goes down
The Wayback Machine is the Internet Archive's tool for viewing saved copies of web pages, and researchers, historians, journalists, and lawyers rely on it when a page changes or disappears. An outage interrupts archive lookups and saved page playback.
During an outage, a URL lookup can hang before any result appears, the calendar view may load with no usable dates, saved pages can fail to open, and Save Page Now may refuse a submission. Lookups tend to stall first; page playback and Save Page Now often fail after that. Problems are often partial, so one snapshot path can fail while another page opens, and a single network or browser can produce reports that look worse than the service as a whole. The status at the top of the page only compares user problem reports with their usual level; it does not ping or monitor the archive itself, and it never checks from multiple locations.
Wayback Machine IP address, servers and network
Checking web.archive.org from our server…
Wayback Machine FAQ
Is Wayback Machine down right now?
Why does the Wayback Machine say a URL has not been archived?
Why is an archived snapshot missing images, video, or CSS?
Why does the calendar show no captures for some dates?
Why does Save Page Now fail on a login page or paywall?
Service updates from @waybackmachine
No posts about problems from @waybackmachine in the last 14 days. The latest is from .
Put the Wayback Machine status badge on your site
Paste one of these into a web page, a blog post or a README. The badge shows the same status as this page, based on user problem reports. Browsers can keep a copy for up to 4 hours. It links back here.
<a href="https://isitdownrightnow.app/services/wayback-machine/"><img src="https://isitdownrightnow.app/badge/wayback-machine.svg" alt="Wayback Machine status" height="20"></a>[](https://isitdownrightnow.app/services/wayback-machine/)The badge is a plain image: no scripts, no cookies. People who see it on your page load it from our server.
How we track Wayback Machine
The status on this page comes from user-submitted problem reports for Wayback Machine, counted in 15-minute windows over the last 24 hours. Each window is compared with the normal level for Wayback Machine, so a few complaints on a quiet day don't trigger anything, but a sudden jump well above normal does.
When reports climb well above normal, the status here changes to partial outage or major outage and the chart moves with it. Wayback Machine doesn't publish a public status page that we know of, so user reports are often the quickest sign that something is wrong on their side.