Blizzard Blue Tracker:
We're aware of the issue and are currently looking into it. We appreciate your patience while this is being investigated.
Update 5:20 p.m. PDT: We're aware that many players are receiving "Error 37" when logging into the game. Please note that this error indicates that all servers are full, and that we're currently receiving a high volume of login traffic. We're working to reduce the frequency at which players are prompted with this error message and ensure that everyone can successfully log in to the game and play.
Update 5:00 p.m. PDT: Maintenance has concluded and Diablo III is now available for play. Auction house maintenance has concluded, as well, but commodities are still disabled at this time.
We're continuing to investigate latency affecting successful sales and purchases on the gold auction house. Please note that while these issues may cause a temporary delay in having purchased items appear in your Completed tab, your items have not been lost. If you do not see your purchased items immediately, please check back later.
-----
We're aware of issues affecting our authentication servers which may cause players to experience failed or slowed logins (e.g. getting stuck at "Retrieving Character List"). We're currently investigating the cause of these issues and have brought all Diablo III game servers offline for maintenance. We will provide updates as they become available.
Thank you so much for your reports!
Update 3:10pm PDT - I see a few asking about Error 37. That error occurs when the realms are unavailable. As we're working on this issue still, you may see Error 37. As before, we do not need further reports of this. We will do what we can to get the authentication server back up and working properly as soon as possible.
Update 3:54pm PDT - We're still investigating the cause of these issues and have brought all Diablo III game servers offline for maintenance. We will provide updates as they become available.
0 comments:
Post a Comment