13

    Blizzard’s Battle.net log in servers have been unavailable for most of the day, despite numerous Blue Posts updating the issue and working towards a fix. Battle.net Log In Failure: Now Resolved.

    The connection issues reported earlier appear to have been resolved. Thanks to everyone for being patient with us while we looked into and addressed your reports. As ever, we will continue to monitor the status of our games and incoming reports from our players.

    If you ever have difficulty accessing our sites during a service outage, please don’t hesitate to reach out to our Customer Support team via Twitter or by submitting a Customer Support ticket:

  • @BlizzardCS (Twitter)
  • Customer Support Page
  • There was a lot of speculation that the downtime was due to a DDoS attack, but a Blue Post stated that was *not* the case. Ironically, I’d just read an article on Kotaku about how DDoS attacks have evolved in recent years and why they are so difficult to deal with these days. It’s an informative and depressing read.

    Last week, eager Christmas celebrators across the world hooked up their brand new Xboxes and PlayStations only to find that both online networks were down, leaving countless new games totally unplayable.

    It was a particularly large piece of coal in gamers’ stockings, and while Microsoft’s service recovered after 24 hours, the PlayStation Network suffered a prolonged outage that lasted two full days. Even today we’re still feeling the effects; almost a week later, PSN’s service remains intermittent thanks to what Sony said this weekend was a Distributed Denial of Service (DDoS) attack—an intentional flood of traffic designed to cripple a network’s servers.

    …these attacks have grown increasingly sophisticated over the past few months, to the point where security methods installed as recently as 2012 or 2013 might no longer be effective.

    “One of the historical ways that people have handled these attacks is they notice that the spike is occurring against them and they’re seeing an outage, and then they work with their providers to do something called ‘blackholing,'” Larson said. “Meaning as they’re sending [fake traffic] you just wanna throw it into the ground, you wanna throw it away.

    “A year and a half ago, DDoS attacks were the kind of things that happened against you—you noticed there was a DDoS attack, and then you blackholed and moved on. The tools are much more dynamic now. Humans and human processes are not fast enough to keep up with the change — you need a machine system that’s basically looking for and identifying the attacks in real time, then taking action against them immediately.”

    It’s a sad state when some geek group with a grievance, or just some bored script kiddies, can ruin everyone else’s gaming fun for hours or days. But that seems to be the world we live in, as cyber security and maintenance is forever trying to keep up with the people figuring out ways to break the system. Throw that on top of just general technical issues and human stupidity, and it’s a wonder we can even check our email with any reliability.

    Click through for some more Blue posts about today’s log in downtime.

    Good morning, everyone!

    We’re aware that many players are experiencing issues both logging into and staying connected to several of our games, including Diablo III.

    While we don’t have an ETA to share at this time for when login and connectivity will be restored, we’re working to address the issues presently and will provide further updates as more information becomes available. You can follow this thread for those updates or check out our @BlizzardCS Twitter feed.

    We sincerely apologize for any inconvenience this service interruption has caused, and would like to thank you so much for your patience (and your reports). We hope to have our Battle.net service restored and running smoothly just as quickly as possible.

    ———————————————————————————–

    [UPDATE] 11:55 a.m. PST: At this time we are currently hoping to have login and connectivity restored for both Battle.net and Diablo III in approximately 90 minutes. Please note that this just an estimate, however, and that these issues may take longer to resolve.

    As always, should this estimate change, and should these issues persist after that time frame has expired, we will post an update to this thread. We will also be sure to provide an update once all issues are resolved.

    ———————————

    [UPDATE] 1:49 p.m. PST: We’re continuing to work to address issues affecting login, connectivity, and long game queues. We don’t have a new ETA to share at this time regarding when these issues will be resolved, but we’ll continue to provide updates in this thread as new information become available.

    Thank you to everyone for being so patient. We hope to have you all back into Battle.net and playing your game of choice as soon as possible!

    ———————————–

    [UPDATE] 4:10 p.m. PST: The connection issues reported earlier appear to have been resolved. Thanks to everyone for being patient with us while we looked into and addressed your reports. As ever, we will continue to monitor the status of our games and incoming reports from our players.

    And more info….

    Velnrak: 10:06 am

    Our current Estimate for a resolution is 90 minutes. Thanks again for your patience.

    Hello Everyone, we’re looking into the Error 3006 issues. I’ll post updates as I get them. Thanks for your patience!

    12 Noon

    We’ve identified the issue, and it should be resolved in an hour.

    We can say that this was not a DDoS attack, and it was an issue on our side.

    1 pm

    We’re continuing to work on this issue, and we’ll provide updates as we get them.

    Update 3:28 pm

    Battle.net has been restored, and you should be able to login once again. Thanks very much for your patience today.

    Annoying for people who missed a day or an afternoon of play time, but it goes to show why Bliz didn’t want to go live with the patch now on the PTR back before Xmas. It was content complete, but with the holiday coming up and heavier player use expected, they didn’t want to risk it without all their tech guys present in case of emergency. Like the one they had today.

    You may also like

    More in Battle.net