Wayback Machine not working? The cause is usually one of five things: the archive itself is down or overloaded, your connection or browser is getting in the way, you have been rate-limited, the page was never captured (or was excluded), or the capture exists but replays badly. Each one has a different fix, and most take less than five minutes to identify. This guide walks through the checks in the order that saves the most time, explains the error messages you are likely to see, and shows what to do when you need the archived files themselves rather than just a page that loads.
Quick answer: what to check first
- Is archive.org down for everyone? Open
https://archive.organdhttps://web.archive.orgin a private window. If neither loads, check the Internet Archive’s official blog or social accounts for an outage notice and try again later. - Is it only one page? Load a well-known capture (for example any snapshot of
example.com). If that works, the problem is specific to the URL you want, not to the Wayback Machine. - Does an error code appear? Note it exactly; the table below maps the common ones to a cause.
- Does the calendar show no captures? The page may never have been archived, may be excluded, or may be stored under a slightly different URL (www vs non-www, http vs https, trailing slash).
- Does the page load but look broken? The capture is incomplete or depends on scripts that cannot run from the archive. Try another snapshot date.
Wayback Machine not working at all: outages and slowdowns
The Internet Archive is a non-profit that runs the Wayback Machine on its own infrastructure, and it occasionally goes offline. Past notices have included planned maintenance windows lasting days and unplanned outages caused by failed network equipment. During an outage you may see timeouts, a blank page, a generic “temporarily offline” message, or very slow loading that eventually fails.
What to do:
- Test from a different network (for example mobile data instead of office Wi-Fi). If the archive loads there, the block is on your side.
- Look for an official status message from the Internet Archive before assuming anything is broken on your machine. Third-party “is it down” checkers can help, but they only report what their own probes saw.
- Wait and retry. Slowdowns are common at busy times, and repeated rapid reloading can push you into a rate limit, which makes things worse.
- Do not start a large download during an outage or right after one. Requests that fail half-way leave you with a partial, inconsistent copy.
When the problem is your browser or connection
If archive.org works on another device or network, the issue is local. Work through these checks:
- Private window. A private or incognito window runs without most extensions and cached data. If the Wayback Machine works there, an extension or stale cache is the culprit.
- Ad blockers and privacy extensions. Archived pages contain old third-party scripts and tracking code. Some blockers react badly and stop the replay frame or the timeline bar from loading. Allow
web.archive.organd reload. - Clear the cache for archive.org. A cached error page can keep reappearing even after the archive is back.
- Corporate networks, VPNs and DNS filters. Some workplace filters, school networks and VPN exit nodes block or throttle archive.org. Try with the VPN switched off, or from a different exit location.
- Try another browser. Rarely, a browser update breaks replay of a specific old page type, such as pages that relied on Flash or obsolete plugins. That content cannot run in a modern browser at all.
Error messages and what they mean
| What you see | Likely cause | What to do |
|---|---|---|
| 429 Too Many Requests | Rate limit applied to your IP, browser or script | Stop, wait, then send far fewer requests per minute |
| Timeout, 502, 503 or 504 | Archive overloaded or partly offline | Wait and retry later; check official status updates |
| “Wayback Machine has not archived that URL” | No capture under that exact URL | Try other URL variants, the domain root, or a wildcard search |
| Message that the URL has been excluded | Site owner or rights holder requested exclusion, or robots rules blocked crawling | No workaround on archive.org; look for other public sources |
| Page loads but images, CSS or menus are missing | Those files were never captured, or were captured on a different date | Try nearby snapshots; check missing files separately |
| Redirect loop or redirect to a different page | The original site redirected when the crawler visited | Pick a snapshot from before the redirect was put in place |
“Not archived” or excluded: when there is nothing to load
A common reason people think the Wayback Machine is not working is that the page they want simply is not there. The Internet Archive‘s own help pages explain that a site’s robots.txt may have prevented crawling, that password-protected or otherwise inaccessible pages may not be archived, and that pages with no links pointing to them may never be found by a crawler. Site owners can also request exclusion.
Before concluding that nothing exists, try these variants of the address:
- With and without
www. http://andhttps://- With and without a trailing slash, and with
index.htmlorindex.phpadded - The domain root, then browse the captured site’s own navigation to reach the page
- A wildcard search such as
example.com/blog/*on the Wayback Machine to list every captured URL under a folder
If you need every URL that was ever captured for a domain, the CDX index is far more reliable than clicking through the calendar. Our guide to the Wayback Machine API and CDX server shows how to list captures and filter them by status code and date. For a full list of a site’s old addresses, see how to find historical URLs from the Wayback Machine.
New captures also take time to appear. The Internet Archive notes a lag of several hours between a crawl and the capture becoming visible, so a page you saved a few minutes ago may not show in the calendar yet.
The page loads but looks broken
A capture is a set of separate files saved at different moments: the HTML, stylesheets, scripts, images and fonts. If the crawler saved the HTML but not the stylesheet, you see unstyled text. If it saved the stylesheet a year later, after a redesign, the layout can look wrong. The Wayback Machine fills gaps with the nearest capture it has, which is useful but can mix versions.
Pages that depend heavily on JavaScript are the hardest. The archive’s help pages note that JavaScript elements are often hard to archive, and scripts that need the original server (search boxes, shopping carts, login areas, comment forms, infinite scroll) usually fail when replayed. That is not the Wayback Machine malfunctioning; the data those scripts fetched was never stored.
What helps:
- Open the calendar and try two or three captures around the date you want. One of them is often much more complete. Our guide on choosing the best Wayback snapshot explains what to compare.
- Check whether missing images exist under another date by opening the image URL directly in the Wayback Machine.
- Remember what the archive never holds: databases, server code, customer accounts, orders and private pages. No tool can bring those back from captures.
Save Page Now not working
Save Page Now is the form on web.archive.org that captures a single URL on demand. When it fails, the message usually explains why, and the reasons differ from replay problems:
- The target site blocks the archive’s crawler. Some sites refuse automated visitors, return a login wall, or serve a bot-check page. The archive then saves that block page, or nothing.
- The page needs a login. Save Page Now captures what an anonymous visitor sees. Members-only content cannot be saved this way.
- You saved the same URL very recently. Repeated saves of one page in a short window may be refused or return the earlier capture.
- The page is too heavy or too slow. Very large pages, long redirect chains or slow servers can time out before the capture finishes. Try again at a quieter time.
Keep in mind what Save Page Now does and does not do. According to the Internet Archive’s help pages, it saves one specific page and does not add the URL to future crawls, and it does not save multiple pages or a whole site. If a capture seems to have vanished, remember the lag before new captures appear in the calendar.
Wayback Machine not working on a phone or through an extension
On mobile, archived desktop pages are often wider than the screen and the replay toolbar takes space, so pages can look broken even when the capture is fine. Rotate to landscape or request the desktop site in your browser menu. In-app browsers inside social apps sometimes block the replay frame; open the link in your normal browser instead.
Browser extensions that open archived copies, and “view cached page” buttons in other tools, depend on the same Wayback Machine service. When they stop working, test the same address directly on web.archive.org. If the direct address works, the extension is out of date or its permissions were reset after a browser update.
When a downloader or script is the thing failing
If pages load in your browser but a command-line tool fails, the problem is almost always request volume or URL handling rather than an archive outage. Lower the number of parallel requests and add pauses. The 429 guide covers rate limits, and the Wayback Machine downloader troubleshooting guide covers tool-specific errors such as empty files and stalled runs.
When to stop troubleshooting and get the files another way
If your goal is a working copy of an old website rather than viewing one page, fighting the browser replay is often the slow route. Replay pages contain the archive’s toolbar, rewritten links and mixed capture dates, which all need cleaning before the files can be hosted again.
You have three realistic options:
- DIY with a downloader. Use a command-line tool, go slowly, then fix links and missing assets yourself. Our guide on fixing links in a downloaded Wayback website covers the clean-up.
- Check what is actually archived first. Our free archive check tells you how many pages and assets were captured before you spend time on a download.
- Have the download done for you. The Wayback website download service delivers the captured site as a clean HTML ZIP, with archive toolbar code removed and internal links pointed at the local files.
Whichever route you choose, nobody can promise a complete copy: the result depends on what the crawler saved. A quick check of the captures before you start is the best way to set realistic expectations.
Frequently asked questions
Why is the Wayback Machine not working today?
Either the Internet Archive is having an outage or slowdown, or something local (an extension, VPN, network filter or rate limit) is blocking you. Test in a private window on another network. If it fails everywhere, wait for the archive to recover; if it works elsewhere, the problem is on your side.
Why did Save Page Now not save my page?
The site may block crawlers, require a login, be too slow to load, or have been saved moments earlier. New captures can also take several hours to show in the calendar.
Why does the Wayback Machine say a page is not archived when I know it existed?
The crawler may never have found it, robots rules may have blocked it, the owner may have requested exclusion, or it may be stored under a slightly different URL. Try URL variants and a wildcard search before giving up.
Why are images missing from an archived page?
Images are separate files and were often captured on different dates or not at all. Try nearby snapshots, or open the image URL directly in the Wayback Machine to see which dates have it.
Is the Wayback Machine not working on mobile?
It works on phones, but wide desktop captures and in-app browsers often make pages look broken. Open the link in your main browser and request the desktop site.