For more than an hour, any page on the Wayback Machine leads to [Archive] Internet Archive: Scheduled Maintenance:
Temporarily Offline
Internet Archive services are temporarily offline.
Please check our official accounts, including Twitter/X, Bluesky or Mastodon for the latest information.
We apologize for the inconvenience.
Edit 20251209 18:22Z:
Back then I didn’t have time to put all updates in the blog post, so I put them as a reply below the [Archive] Richard MacManus: “The Wayback Machine has been offline for the past hour or so…” – Mastodon.
Later I forgot to update this blog post, but I just bumped into the thread again, so here it is:
- [Wayback/Archive] Jeroen Wiert Pluimers: “RE: https://wiert.me/2025/11/2…” – Mastodon
This is very typical for almost all their maintenance and outages and really frustrating for their users (of which luckily more and more are donating to them).
Plus that the title suggests the whole Internet Archive is under maintenance whereas the rest really is working pretty OK.
A page like `status.web.archive.org` or `status.archive.org` would be a much welcomed.
Just blogged about it: https://wiert.wordpress.com/?p=187822
(Hopefully Mastodon gets backtick code formatting)
- [Wayback/Archive] Jeroen Wiert Pluimers: “@ricmac @internetarchive It …” – Mastodon
It didn’t, but now that I’m back behind a keyboard, I see some social media activity by Jason Scott:
https://mastodon.archive.org/@textfiles/115581682877344258
- [Wayback/Archive] Jeroen Wiert Pluimers: “@ricmac @internetarchive The…” – Mastodon
There is at least some progress:
– https://web.archive.org/save/ returns a 503
– https://web.archive.org/save/https://mastodon.social/@wiert/115582221809188503 returns a 404
– https://web.archive.org/https://mastodon.social returns a 503- [Wayback/Archive] Jeroen Wiert Pluimers: “@ricmac @internetarchive Som…” – Mastodon
Some progress:
– https://web.archive.org/save/ returns 200
– https://web.archive.org/save/https://mastodon.social/@wiert/115582221809188503 returns 200 with “system is overloaded” message and no imagery on the canvas
– https://web.archive.org/https://mastodon.social returns 503
– https://web.archive.org/https://mastodon.social/@wiert/115582221809188503 returns 503
– https://web.archive.org/web/*/https://mastodon.social returns 200
– https://web.archive.org/web/*/https://mastodon.social/@wiert/115582221809188503 returns 200
– https://web.archive.org/web/20251120215143/https://mastodon.social/@wiert/115582221809188503 returns 503- [Wayback/Archive] Jeroen Wiert Pluimers: “@ricmac @internetarchive Som…” – Mastodon
Some 32 hours after the outage started, the status is this:
– HTTP 200 for https://web.archive.org/save/
– SRY page for https://web.archive.org/save/https://mastodon.social/@wiert/115582221809188503
– HTTP 303, 302 and finally 200 for https://web.archive.org/https://mastodon.social
– HTTP 303, 302 and finally 200 for https://web.archive.org/https://mastodon.social/@wiert/115582221809188503
– HTTP 200 for https://web.archive.org/web/*/https://mastodon.social
– HTTP 200 for https://web.archive.org/web/*/https://mastodon.social/@wiert/115582221809188503It’s slowly but steadily returning to normal behaviour.
- [Wayback/Archive] Jeroen Wiert Pluimers: “@ricmac @internetarchive Als…” – Mastodon
Also some social media coverage yesterday:
– https://x.com/internetarchive/status/1991504182411685955
– https://x.com/internetarchive/status/1991600485489656023– https://bsky.app/profile/archive.org/post/3m62vw5dsr22r
– https://bsky.app/profile/archive.org/post/3m63lafzzhs2r– https://mastodon.archive.org/@internetarchive/115582351252189547
– https://mastodon.archive.org/@internetarchive/115583852434614027The first were at almost 8 hours after the incident started. That’s pretty late for status updates on a large outage.
Time to get to the next appointment. Back in some 8 hours or so.
- [Wayback/Archive] Jeroen Wiert Pluimers: “@ricmac @internetarchive – H…” – Mastodon
– HTTP 200 for https://web.archive.org/save/
– HTTP 200 for http://web.archive.org/save/https://mastodon.social/@wiert/115587592601512225 plus a succesful archive
– HTTP 307, 307, 302, 200, 307 and finally 200 for https://web.archive.org/web/20251122120322/https://mastodon.social/@wiert/115587592601512225
– HTTP 303, 302 and finally 200 for https://web.archive.org/https://mastodon.social
– HTTP 303, 302 and finally 200 for https://web.archive.org/https://mastodon.social/@wiert/115582221809188503
– HTTP 200 for https://web.archive.org/web/*/https://mastodon.social
– HTTP 200 for https://web.archive.org/web/*/https://mastodon.social/@wiert/115582221809188503Oh: interesting: https://stackoverflow.com/questions/20
- [Wayback/Archive] Jeroen Wiert Pluimers: “@ricmac @internetarchive The…” – Mastodon
The appointment took way longer: got back late, did the mandatory 12 hour recovery hence the follow up only now.
The good thing: the Wayback Machine seems to have fully recovered.
New social media coverage some 2 hours after my coverage yesterday confirms this:
– https://x.com/internetarchive/status/1991888073446318191
– https://bsky.app/profile/archive.org/post/3m65l4skb3c2c
– https://mastodon.archive.org/@internetarchive/115588341280707332
Glad things work again. Now going through my backlog of pages that need to be archived.
- [Wayback/Archive] Jeroen Wiert Pluimers: “@ricmac @internetarchive Slo…” – Mastodon
Slowly archival times go down. From about 20 hours 2 days ago to about 6 hours now.
Edit 20251120T1614Z:
For a short time, some of the links didn’t redirect to the above SRY page, but now they again do. This was just a short happy period:
[Archive] Jeroen Wiert Pluimers: “@ricmac @internetarchive …” – Mastodon
There is at least some progress:
- https://web.archive.org/save/ returns a 503
- https://web.archive.org/save/https://mastodon.social/@wiert/115582221809188503 returns a 404
- https://web.archive.org/https://mastodon.social returns a 503






