wow-server-stauts
Latest
Maintenance for Thursday August 6th
According to the in-game announcement, there will be two hours of maintenance tomorrow August 6th on all realms. The maintenance announcement has changed throughout the evening, but seems to have settled on this downtime.The downtime will happen from 5:00 a.m. PDT / 8:00 a.m. EDT and last until 7:00 a.m. PDT / 10:00 a.m. EDT. This of course assumes that there'll be no extended super-fracken-duper maintenance put on top of that. And we know just how much Blizzard loves to increase their maintenance periods. If there is you'll hear it here.While the maintenance is going on, you can check out WoW.com's Guide to Patch 3.2 and read up on all the things you missed, or think you missed. There is also the beginnings of a list of bug fixes; a list that's sure to grow over the coming days.
Boom goes the servers...
....the night before BlizzCon ticket sales.Yes folks. You should be completely confident in Blizzard. I mean, the night before how many tens of thousands of people from around the world try to order tickets, the authentication servers go down. Many users are experiencing it, however a few are not.What on Earth could go wrong tomorrow?Reythur, a Blizzard blue poster, has said that the issue is being investigated. We'll update this post with more information as we get it.Update #4: Things are working now it appears for all Battle.net accounts and all regular accounts.
Authentication issues tonight [Updated]
In the last fifteen minutes or so we've received numerous reports that authentication servers are down for North American realms. While the outage does not appear to be affecting anyone in game, those folks logging in will be stuck at "authenticating" for the time being.There has been no word from Blizzard about this, but if we've gotten a dozen tips about this in the past fifteen minutes, I'm sure they have too.We'll update this post when we have more information.Update #1: Speak of the devil, there's a blue post about this now.Update #2: It appears the issue is now resolved.
