Twitter is notorious for its intermittent crashes. Most of those crashes lasts for a few seconds for some users, but every once and while, the website crashes for a great length for most, or all of its users.
The worst crash thus far took place on June 21, 2012. Here's a quick rundown on the crash:
At approximately 11:50 AM EDT, Twitter went down for most of its users. The crash was so severe, Twitter's "Fail Whale" failed to show up.
At approximately 1:00 PM EDT, some users reported that Twitter is functioning for them.
At 1:42 PM EDT, Twitter declared that "the issue has been resolved and all services are currently operational" on their Status page.
At 2:46 PM EDT, Twitter crashed again for some of its users. Twitter announced that "the issue is on-going and engineers are working to resolve it."
Shortly after 3:00 PM EDT, the issues was finally resolved, and Twitter announced that the crash was caused by "a cascaded bug in one of our infrastructure components."
This crash was so "severe," thousands (if not millions) of Twitter users freaked out and constantly complained about the crash on Facebook and Tumbler...
Image Credit: Twitter