Wednesday, February 28, 2007

bX-sp4hmm

A quiet evening at home?



Not Tonight.


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-sp4hmm

Additional information
uri: /2006/12/connecting-two-dissimilar-networks.html
host: nitecruzr.blogspot.com

This information will help us to track down your specific problem and fix it! We apologize for the inconvenience.


So much for using PChuck's Network for giving advice tonight. And I'm apparently not alone, either. Looks like it started about 17:35 PST.

Doesn't affect all blogs, either - PChuck's Network (my exemplary victim, here) is down, but The Real Blogger Status is up. Both are New Blogger with Classic templates. The Real Blogger Status - Beta, New Blogger with Layout template is also up.


3 hours later, nothing in Blogger Status.


And I don't see clearing cookies, as with the Status 503, yesterday, as a way around this one. Nope, just piss and moan all evening.

I wonder if this one will be solved in silence, like so many others.

(Edit 22:15): Problem acknowledged by Pete, at 21:58.



Here's an improvement!


Look at that - actually telling us, in the error message, that they are working on the problem. Dare we to hope that this will become a routine?



5 hours after it started


Problem fixed somewhere around 22:30, and further acknowledged by Pete.

>> Top

2 comments:

jau said...

Not actually fixed, however. They SAY it's fixed but there are many of us for whom it's still a problem. I'm puzzled, too, as to why one or two of my blogs are snagged by this, but not all. GOLLY it's frustrating!

Chuck said...

The Blogger problem that caused last nights shenanigans, aka the "bX-sp4hmm", is not the same as your problem, which has 3 different codes.

The different codes distinguish between the different problems, even though they don't actually solve any. Only Blogger can solve the problems.

They do let us organise our efforts a bit. When we started seeing "bX-sp4hmm" all over the forums, it was pretty obvious that there was a major outage in progress.

My hope is that we can train Blogger Support to respond faster. From what I can tell, the first "bX-sp4hmm" report was posted sometime around 17:30 PST. The first Blogger Status entry was time stamped 21:58.

Read my "Silence" articles for my feelings on that. Taking 2 1/2 hours to SEE, or to ACKNOWLEDGE, a problem is ridiculous. 30 MINUTES would be minimal. They should have had something in Blogger Status by 18:00.