07/26/2012 12:01 pm ET Updated Jul 26, 2012

Twitter Down After Gchat Blackout On July 26 (UPDATE: It's Back)

This post has been updated.

First Gchat, now Twitter... What's happening with the Internet today?!

This morning we reported that Google Talk, better known as Gchat, was experiencing a global outage. By 11:40 a.m., Twitter users were noticing service issues.

When we tried accessing on Google Chrome, we received an error message telling us that "The connection to was interrupted." According to the website, many users are unable to reach the site.

UPDATE 1: "Users may be experiencing issues accessing Twitter," Twitter has written on its service status webpage. "Our engineers are currently working to resolve the issue."

UPDATE 2: Though the mobile version of Twitter isn't working for us (on the iPhone), The Verge notes that it has successfully tweeted though Twitter's mobile site. So anxious Twitterers, try and ply your blitherings there.

UPDATE 3: We should note that today makes for the second major Twitter blackout this past year. In June, the site was downed by a "a cascaded bug in one of our infrastructure components," according to a tweet from the company.

UPDATE 4: Twitter appears to be back up, for us at least. (As well as TechCrunch.) Both mobile and the normal web version are loading for us, and we were successfully able to tweet. According to the AP, the Twitter outage seemed to be worldwide, though it's difficult to say to what level different users were affected. Twitter being Twitter, already jokes are filtering in. "First, they came for Gchat, and I said nothing, because I couldn't. Then they came for Twitter...." The Atlantic's Matt O'Brien tweets.

UPDATE 5: At about 2 p.m. ET, Twitter issued an apology for the morning outage. The company explains:

The cause of today’s outage came from within our data centers. Data centers are designed to be redundant: when one system fails (as everything does at one time or another), a parallel system takes over. What was noteworthy about today’s outage was the coincidental failure of two parallel systems at nearly the same time.

So it wasn't because of high tweet volume from the Olympics. Phew. Because the problem would have only gotten worse with the opening ceremonies on Friday.