Follow me.......





Friday, May 13, 2011

Blogger Debotchery......

Wondering where your favorite blog posts are?
Well, wonder no more......

A Note from our friends at Blogger....

What a frustrating day. We’re very sorry that you’ve been unable to publish to Blogger for the past 20.5 hours. We’re nearly back to normal — you can publish again, and in the coming hours posts and comments that were temporarily removed should be restored. Thank you for your patience while we fix this situation. We use Blogger for our own blogs, so we’ve also felt your pain.

Here’s what happened: during scheduled maintenance work Wednesday night, we experienced some data corruption that impacted Blogger’s behavior. Since then, bloggers and readers may have experienced a variety of anomalies including intermittent outages, disappearing posts, and arriving at unintended blogs or error pages. A small subset of Blogger users (we estimate 0.16%) may have encountered additional problems specific to their accounts. Yesterday we returned Blogger to a pre-maintenance state and placed the service in read-only mode while we worked on restoring all content: that’s why you haven’t been able to publish. We rolled back to a version of Blogger as of Wednesday May 11th, so your posts since then were temporarily removed. Those are the posts that we’re in the progress of restoring.

Again, we are very sorry for the impact to our authors and readers. We try hard to ensure Blogger is always available for you to share your thoughts and opinions with the world, and we’ll do our best to prevent this from happening again.

Posted by Eddie Kessler, Tech Lead/Manager, Blogger

3 comments:

Sonya said...

Thanks for the information! I was looking from blog to blog to see if anyone knew anything...was about to check out the blogger website. lol

Sam said...

i was wondering why it was down :o) The only info I could find is that it was down for about an hour on Wednesday!!

Barbara said...

Interesting.. But if they followed sound IT practices they would have tested the patch or code they intended to roll out as part of their maintenance program .. perhaps a newbie at the wheel. If that happened in a banking environment all sh*t would hit the fan. just saying