Space for ads
Checked every 5 minutes · How we measure this
As of 18:40 EDT on 2 Oct 2026, web.archive.org responded to our check in 739 ms, with 95.71% availability over the last 24 hours.
Checked every 5 minutes · last checked 7 minutes ago
The line is response time measured from our probe to web.archive.org, which rises when the service slows down. Shaded red marks intervals where checks actually failed. It excludes your own connection and browser rendering.
0 problem reports
Web Archive outage
DownBits detected an outage on Web Archive between 2 Oct 2026, 07:50 – 08:45 IST, lasting ongoing. Detected across 11 consecutive automated checks of web.archive.org.
Detected by DownBits probe
Web Archive is responding normally. Our last automated check of web.archive.org completed 7 minutes ago and succeeded in 739 ms. Over the past 24 hours the service answered 95.71% of our checks.
Measured from our automated checks, Web Archive has been available 95.71% over 24 hours, 99.39% over 7 days, 99.40% over 30 days. We recorded 1 incident in the last 30 days.
Web Archive has averaged 804 ms across our successful checks in the past 24 hours, which is slower than ideal and may feel sluggish on a weak connection. Response time is measured from our probe to web.archive.org and does not include rendering time in your browser.
The most recent incident DownBits recorded for Web Archive began on 2 October 2026 at 07:50 IST and lasted 55 min. It was logged as outage. Detected by DownBits probe.
Our probe is reaching web.archive.org normally right now, so the problem is more likely to be local to you than a full outage. Use the report button on this page to add your own signal — when several people report the same problem within a short window, it appears on the chart above.
Mobile apps and the website often run on different infrastructure. If Web Archive fails in the app but works at web.archive.org in a browser, an app update or a cache clear inside the app usually resolves it.
Open any other site. If nothing loads, the issue is your network rather than Web Archive. On Windows run ping web.archive.org and nslookup web.archive.org in Command Prompt; on macOS or Linux use Terminal. A DNS failure and a server failure look identical in a browser but are very different problems.
Load web.archive.org in a private or incognito window. If it works there, clear cookies and site data for web.archive.org in your normal browser rather than clearing everything.
Switch from Wi-Fi to mobile data, or vice versa. Regional ISP routing problems are common and often affect one carrier while others are unaffected.
We link the vendor status page so you can check our reading against theirs.
No comments received
