Saturday, May 14, 2011

Blogger Is Restored

As some of you may know Blogger (Google's blogging and online publishing service) which is the host website I use for the "Delmar Dustpan" blog has been down since Wednesday. Google put all blogs on read-only, meaning users can view blogs hosted with the service but owners of those respective blogs cannot login, update, or manipulate their sites in any way. Yesterday it stumbled back up and I am waiting to see if there are any aftershocks before I start posting again. So far the only thing I notice is a couple of comments received between Wednesday and yesterday are missing.

Blogger has published this notice
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

No comments: