Friday, June 22, 2012

'Cascading Bug' Took Twitter Down

Twitter has blamed a "cascading bug" for digest the amicable networking site unapproachable on Thursday.

Users from around the world reported difficulties logging on to the site after problems proposed at about 17:00 BST.

The service was affected for around two hours whilst engineers sought to compromise the issue.

In a blog post , Twitter discharged reports it had been hacked, and offering "sincere apologies" to its users.

"A cascading bug is a with an outcome that isn't cramped to a specific program element, but rsther than its outcome "cascades" in to other elements as well," explained Mazen Rawashdeh, the site's clamp boss of engineering.

"One of the characteristics of such a bug is that it can have a poignant impact on all users, worldwide, that was the box today.

"As shortly as you detected it, you took visual actions, that enclosed rolling back to a formerly sound chronicle of Twitter."

Mr Rawashdeh described the incident as "turbulence".

"We began liberation at around 10:10am PDT [18:10 BST], forsaken once again around 10:40am PDT [18:40 BST], and then began full liberation at 11:08am PDT [19:08 BST]."

The site's final leading downtime in the UK was on New Year's Day when the site crashed after apropos overloaded.

In its progressing days, Twitter was famous for its flaky reliability, with its "fail whale" comic strip - that was displayed when the site was overloaded - apropos a periodic steer for users.

However, updated investment in to the service has resulted in improved stability, Mr Rawashdeh wrote.

"For the past 6 months, we've enjoyed the top outlines for site trustworthiness and fortitude ever: at least 99.96% and frequently 99.99%.

"In easier terms, this means that in an median 24-hour period, twitter.com has been sound and existing to everybody for rounded off 23 hours, 59 mins and 40-ish seconds.

"Not currently though."

No comments:

Post a Comment