Hack Hack Hack Hack It Apart
Amazon.com’s homepage appears to be temporarily down, showing a “service unavailable” message to users. Links within Amazon are still functional, but the homepage is inaccessible.
As TechCrunch notes, the site is serving a 503 error, indicating that “the server powering the site is down due to maintenance or overloading,” which can mean the server is being DDOS’d. Amazon Web Services’ dashboard says all hosting services appear to be operating normally.
This day, a day that will live in infamy, has levied blows at both productivity and procrastination. Earlier today Gmail went down for a solid hour, with Gchat inaccessible for even longer. And now, prior to 6 p.m., as everyone is figuring out how to spend the last few moments of the work day appearing to get something done while actually logging on to fruitless social media sites, Facebook has gone down for some.
Come back Twitter!
For the past 30 minutes or so, real-time updating on Twitter appears to have stalled. The most recent tweet appearing in the Twitter feed of a number of users is from over 30 minutes ago, and the site has stopped updating itself. A scant tweet from over a half hour ago will flow in at the rate of about one per minute–otherwise, it’s a vast nothingness.
Strangely, it appears that tweets may be working on third party apps like Tweetdeck, but not on Twitter’s dedicated site.
Good thing school’s out for summer. Wikipedia, the Internet’s favorite knowledge base, has been down for the last 45 minutes.
The Wikimedia foundation tweeted that its engineers are currently working on solving the problem. Betabeat can access individual articles, but gets the above error message when trying to navigate to the main page. Hopefully it should be back up soon.
In the meantime, if you’re jonesing for your Wiki fix, here’s a pro tip: just read the Google cache version of the article. Or just continue to freak out.
Twitter’s big Thursday afternoon crash (ongoing for us as of 1:20 p.m. EDT) produced a weird landing page that sent Tumblr users into a screencapping frenzy, in part because unless you’ve programmed in or studied Ruby on Rails, the programming language upon which Twitter was originally built, you probably won’t recognize blank Ruby variables like “<%= reason %>” or “<%= deadline %>.”
Reactions ranged from Debby in Germany, who took the opportunity to abuse Twitter with profanity:
It appears that the Internet is greatly enjoying fucking with us today. Earlier this morning, Gchat experienced an outage, and as of 20 minutes ago, Twitter went dead. Strangely, obsessively refreshing does not fix the problem, and yields only a sad “This webpage is not available” message from our browser of choice (Chrome, duh).
The Twitter Status blog updated 19 minutes ago with the following message:
Users may be experiencing issues accessing Twitter. Our engineers are currently working to resolve the issue.
Seven users have somehow managed to tweet this message, through a method we can only describe as black magic.
Here we were, prepping a Zynga post, when we popped over to check a detail on Facebook and discovered much to our horror a page that read “The webpage at https://www.facebook.com/ is currently unavailable.”
Nor is it our admittedly budget Internet, either: A quick check of Twitter reveals that this Betabeat reporter is not alone, with a flood of tweets confirming the social network is down for at least some users. DownRightNow confirms, as does downforeveryoneorjustme.com/facebook.com. We checked Facebook’s official Twitter account, but it hasn’t been updated since May 24th, of course.
We’ve reached out to Facebook for details and will update when we hear more. In the meantime, please remain calm, Twitter and Tumblr are still functioning.
Presumably Sheryl Sandberg, corporate ninja, is personally sorting this out as we speak.