June 21, 2012 at 12:50 PM ET
Updated 5:31 p.m. ET to reflect the end of the outage
You've probably already noticed, but Twitter went down for a while today. In theory, this means that productivity should have skyrocketed around the world — as soon as we all stopped frantically trying to refresh our Twitter feeds.
We don't know much about the outage, but Twitter did add a message to its official status page, pointing out that "users may be experiencing issues accessing" the social networking service when things came crashing down. Some users were seemingly able to access Twitter through mobile.twitter.com throughout the outage, though.
By late Thursday afternoon, Twitter issued this update via its @twittercomms account: "Today's outage is due to a cascaded bug in one of our infrastructure components. We'll provide updated information soon." A cascaded bug has an effect that isn't confined to aparticular software element; its effect "cascades" into otherelements as well.
In the aftermath of this social media tragedy, I offer my sympathies to anyone who is suffered Twitter withdrawal symptoms like I am and invite him or her to seek comfort on my or on msnbc.com tech's Facebook pages.
Want more tech news, silly puns, or amusing links? You'll get plenty of all three if you keep up with Rosa Golijan, the writer of this post, by following her on Twitter, subscribing to her Facebook posts, or circling her on Google+.