Between 8:20 a.m. and 9 a.m., Twitter completely crashed, leaving many users devastated and distraught. We desperately cast about for answers in the bittersweet shelter of other social networks, begging our Facebook friends and our Tumblr followers for an answer to the long-lasting outage. An error page brought no relief: “Whole server runtime (in this case Ruby engine) is down and web server send raw code to client browsers,” a helpful commenter attempted to clarify, but we still had no idea what % = reason actually meant. It was a rough 40 minutes.
The service came back up a few hours ago, but Twitter hadn’t explained itself until now. So what happened? Was it a hacker attack? Olympic overload? Read More