Archive.today Current Status
*Current Status is based on reports from UpdownRadar users and social media activity data
Website: archive.todayHow do you rate your experience with Archive.today?
Server status
upStatus code
200Response time
1.761 sec
Server status information has just been updated.
Check again
What to do if the site is unavailable?
Is Archive.today down today May, 2025?
Find out if Archive.today is working normally or is there a problem today
Archive.today problems for the last 24 hours
Archive.today not working?
Website is down, not accessible or buggy?
Most reported problems
Not determined.
Forum & Comments
Tips? Frustrations? Share them with other site visitors:
Admin
•
comment pinned
#
Possibly, redirect from different versions is configured incorrectly on archive.today. In this case, use the links below:
http://archive.today
https://archive.today
http://www.archive.today
https://www.archive.today
tell us about today's failures without registering
no identification required
comments with obscene language and insults will be deleted
Guest
•
531 days ago
#
30 November 2023
+
1
-
Cloudflare
Guest
•
534 days ago
#
27 November 2023
+
2
-
★
☆
☆
☆
☆
Guest
•
573 days ago
#
19 October 2023
+
3
-
★
☆
☆
☆
☆
Guest
•
574 days ago
#
18 October 2023
+
0
-
★
☆
☆
☆
☆
www.archive.today unexpectedly closed the connection.
Guest
•
617 days ago
#
4 September 2023
+
0
-
Guest
•
619 days ago
#
+
2
-
★
☆
☆
☆
☆
Guest
•
635 days ago
#
+
0
-
getting Archive.today
I use Firefox. No Archive for some time now.
However: when I switch to Safari I get archive, stick in the URL and it works. I try to grab content from there and it works but is textually butchered. Not sure if that is via Archive or moving back to get it into Firefox.
tip: if you can not get archive try a different browser. that will tell you something but what I am not sure and how to fix I am also unsure.
Guest
•
639 days ago
#
+
0
-
Archive.today/archive.ph hasn't connected for a week.
Guest
•
642 days ago
#
+
0
-
★
☆
☆
☆
☆
Guest
•
690 days ago
#
+
0
-
★
★
☆
☆
☆
Guest
•
691 days ago
#
+
2
-
Can't archive anything anymore.
It's such a good webpage capturing tool since they know that some websites require registration whereas the more famous Internet Archive doesn't use an account for certain websites which would ignore important member-only content that needs to be saved.
Guest
•
762 days ago
#
+
0
-
★
☆
☆
☆
☆
Guest
•
1119 days ago
#
+
0
-
★
☆
☆
☆
☆
"Welcome to nginx!
If you see this page, the nginx web server is successfully installed and working. Further configuration is required.
For online documentation and support please refer to nginx.org.
Commercial support is available at nginx.com.
Thank you for using nginx."
This has neem the case for over a month, now. I reported the problem to Archive.Today on March 21, it is now April 21, and I had been seeing that placeholder page for a while, at the time.
For a while, I found that I could bypass the problem by using an ip anonymizing proxy, which was semi-convenient, but also a little bit damning. The guy running the archive had a working site. He was just playing games with some of the would-be users. A few hours after I carelessly shared the workaround in public with somebody else who had run into the same problem, I started getting error messages when I used it. All of a sudden, the proxy couldn't connect to the archive.
Gosh, almost as if somebody had read the comment, which was in a discussion started by the owner of the archive, and had decided to have his site being invisible to proxies just to sabotage the workaround. At this point, over a month has passed, the clown running the archive has still not bothered to reply to my problem report, and this doesn't look like mere breakdown. I've long since come to the conclusion that some of us, as users, are being messed with by the owner of Archive.Today, who seems to be getting some sort of twisted amusement out of this.
Even before I started seeing that placeholder page, I had been getting error messages when trying to connect, so this has been going on for a long time.
He might try to defend his failure to respond to the problem report by saying something about DDOS attacks, but that's not going to cut it. The conversation in which I reported the problem (and then made the mistake of sharing that workaround) took place on a social media site that has been working just fine, and loading with no particular delays, ruling out the possibility that its servers have been under any particularly heavy load. The owner saw that report. He just chose to ignore it, apparently because he's having fun by messing with his users.
April 1 was almost three weeks ago, at this point. If this ever had been amusing, it would have ceased to be so, a long time ago. At least two of us have tried to reason with the owner, and were nice and supportive in the beginning, but in the end, there was no way to get around the conclusion that we had been dealing with a jerk, the whole time, and that reason wasn't going to work on him.
My advice to anybody reading this is to not bother with Archive.Today or any future project started by its owner. He has shown what kind of person he is - a man without honor, one in whom one shouldn't put any faith, now or ever. The Internet needs a few good archives, but Archive.Today (also known as Archive.is) isn't one of them, any more.
Other websites recently down: