The blog service returns more and more errors

Feb 2, 2007 10:17 GMT  ·  By

Blogger is currently the largest blog community on the internet with millions of users from all around the world and a huge number of readers. Currently, Blogger is a Google service after the company decided to acquire the solution to make it even better. And when I'm saying "even better" I'm thinking at Google's employees' statements that said Blogger is going to be soon the leader of the online blog services. Since the Google acquisition, Blogger was available in two flavors: the classic version and a new Google edition that was meant to test all the new functions implemented by the search giant.

Recently, Google released the final version of the Blogger, saying that it contains even more features than before bundled with improved appearance and loading time. Although the praises coming from Google's employees were many, more and more users are criticizing the blog service, saying that Blogger returns a lot of errors and the loading time is extremely slow. Today, a new error was reported from most of the Blogger users, the solution now returning the following error: "We're sorry, but we were unable to complete your request. When reporting this error to Blogger Support or on the Blogger Help Group, please: Describe what you were doing when you got this error; Provide the following error code and additional information: bX-vjhbsj."

The funniest thing regarding this error is the solution provided by the company that says: "Some users see the error code bX-vjhbsj when trying to view a blog. We have identified the source of this error and will push the fix to the site shortly. In the meantime, hitting Refresh in the browser may workaround the problem. We apologize for the inconvenience."

So, what should we do? Hit the refresh button until Blogger is again available? Or maybe we should start looking for another blog service? What do you think Google?

Although the service is now running after the company announced that "The issue has been fixed. Unfortunately pushing out the new build involved a few minutes outage. We apologize for trouble," I am really curios how long it will take for the next error to appear?