Mass muting in Battle.net West. The issue resolved a few hours after leaving many scratching their heads. What is Blizzard up to now? Who cares, game on!
As usual the Makers above have whims that are as mysterious as their purposes. From the heavens descended a cloud like no other before in our time. It removed the voices of many gamers in Battle.net's West gateway and shunned them into the void.
In a mere blink of an eye, the time it takes a cat to sneeze, the Battle.net Overlords watching above clenched and choked the necks of thousands upon thousands of lowly mortal battle boys. Then when the air was heavy and scarce, just when shear panic and fear gripped the hearts of the weakest amongst us, the void evaporated and everyone's voice was returned.
Ok, Ok I get carried away but here is the scoop. Today pretty much out of the blue many users peacefully doing their thing at Battle.net in the West gateway were muted en masse without reason. Even those using legal CD key's and no third party programs were not spared.
After some classic battle boy confusion and panic the diligent Battle.net techs reverted the mass mutings almost as mysteriously as they had appeared. It was rumored that a MartyT, a battle tech posted this reply to the questions of a battle.net user in panic possibly in order to calm the muted battle boy's terror.
"MartyT.Support@Blizzard: there was no fire or earthquake, just a "glitch" that we're correcting... It ought to be fixed within a couple of hours, give or take a little."
Shortly thereafter this Battle.net post appeared in the Battle.net Status page:
1. Muting issues in USWest | 2/2/2006 3:09:10 AM GMTST
(19:00PST)
The recent muting in USWest was unintentional and should now be corrected. If you are still experiencing mute issues, you can try disconnecting and logging back in to Battle.net.
We apologize and appreciate your understanding.
[ post edited by Battle.net ]
--------------------------------------------------------------------------------
The Battle.net Team
(19:00PST)
The recent muting in USWest was unintentional and should now be corrected. If you are still experiencing mute issues, you can try disconnecting and logging back in to Battle.net.
We apologize and appreciate your understanding.
[ post edited by Battle.net ]
--------------------------------------------------------------------------------
The Battle.net Team
I have avoided using the word "corrected the problem" myself because as far as I can guess the event might have been very much intentional. Maybe a test that went too far? Questions do remain. What were they up to? Why the "glitch"? Why the ".."? Wisdom comes with age, if not ask the devil himself, so here is one word of advice to all Battle.net users, specially those who plan on using third party programs in the near future: Beware.
Links
Battle.net - Official Reply
