Twitter back online (mostly) after unexplained outage

[zigzag3143]

The problems started around 9am Pacific Time (5pm UT) and, after service resumption, it failed again around 90 minutes later. As we post this piece just before 2pm Pacific Time, the problems are still unresolved, according to the Twitter Status page. "The issue is on-going and engineers are working to resolve it," it says.

http://www.theregister.co.uk/2012/06/21/twitter_outage_fail_whale/

 

[zigzag3143]

Another Source

http://www.infoworld.com/d/applications/twitter-struggles-hours-long-outage-196144

 

[zigzag3143]

Another Source

http://www.bbc.com/news/technology-18541129#sa-ns_mchannel=rss&ns_source=PublicRSS20-sa

 

[JMH]

Twitter explains service meltdown

Twitter's service went down and up multiple times in a three-hour period this morning and it was all because of a bug, the company explains to users. The company said it was a "cascading bug," that spread into other parts of its system, causing the outage.

Twitter's VP of engineering Mazen Rawashdeh wrote in a blog post today that the bug isn't confined to a particular software element and instead "cascades" into other elements, affecting users worldwide. He said the company took "corrective actions," after it discovered the bug.

"Not how we wanted today to go. At approximately 9 a.m. PDT, we discovered that Twitter was inaccessible for all Web users, and mobile clients were not showing new tweets. We immediately began to investigate the issue and found that there was a cascading bug in one of our infrastructure components. This wasn't due to a hack or our new office or Euro 2012 or GIF avatars, as some have speculated today," he wrote.

http://news.cnet.com/8301-1023_3-57458477-93/twitter-explains-service-meltdown/

 

[JMH]

[h=1]Twitter Was Taken Down Yesterday By a “Cascading Bug”[/h]

Following yesterday's failure, Twitter has gotten to the bottom of what went wrong: it was a software issue known as a "cascading bug".
If that doesn't mean an awful lot to you, you're not alone, so Twitter has tried its best to explain the issue on its blog:

A "cascading bug" is a bug with an effect that isn't confined to a particular software element, but rather its effect "cascades" into other elements as well. One of the characteristics of such a bug is that it can have a significant impact on all users, worldwide, which was the case today.
​

http://gizmodo.com/5920455/twitter-was-taken-down-yesterday-by-a-cascading-bug

 

[zigzag3143]

Twitter Downplays Downtime

Twitter executive offered an explanation for the cause of an outage that twice knocked Twitter offline around the world on Thursday. Twitter first crashed around 12:30 p.m. EDT on Thursday. The outage affected all platforms and took down both third-party and Twitter apps on the Android and iOS platforms.

http://www.pcworld.com/article/258181/twitter_downplays_downtime.html#tk.rss_news