it really can’t be true. all servers down again. can’t play for days. i strongly assume that DDOS is used to duplicate runes via roleback. Please don’t buy any runes in shops, otherwise this will never stop.
would be great if blizzard can tell us something more spefic.
I think blizz is probably trying to put out multiple fires since launch and I imagine that’s not the time to explain what’s happening and what they did to fix it and what to expect going forward and all that, that is why we get those stock replys about “we know, we are working on it, blah blah”. We should expect better you’re right, but nothing we can do but wait.
all I know, is I found a shako about 30 minutes ago. And when server come back it Better still be there. I had made 2 games sense, but if they roll back my dang hat… I will be very disappointed.
been NM farming sense a few days after launch. Finally giving Hell act 1 a try with andy, raven, etc. Been getting a lot of bogus stuff. Finally before andy, champ back at base of lvl 4 stairs. Shako, I was like O_O eyes popping out of my head.
And finally I got an item i wanted that isnt Etherial… I got travs and a few chance gloves eth… But my skulders didnt go eth… this game I swear.
I suspect Blizzard shot themselves in the foot and pushed some flaky code out.
First, authentication is handled through battle.net and there is currently a beta version of the battle.net client which would seem to indicate changes being made to battle.net.
Second, the fact that the authentication servers go Tango Uniform in the early morning hours would point to attempts to band aid the problem - these are the hours during which many organizations push changes to theiur network applications.
Finally, emergency maintenance has been scheduled for tomorrow morning indication more than the configuration tweaks which is what has probably been happening and either rolling back code to a stable state, or actually pushing new code which will be more stable.
Am I off base? Probably. No one outside their team knows for sure, but is it a coincidence that this started soon after they pushed out their AVX (and who knows what else) fix.