error 3003Forget the Prime Evil that is Diablo, even he is no match for Error 3003. With a sea of gamers trying to log on into Diablo 3 after it was released, there were plenty of gamers experiencing time outs as well as different error messages. Two of the more popular ones we saw were Error 3006, Error 12 and Error 37 – I guess with the turn of the tide, the most popular error now would be Error 3003 as you can see above. Not only that, there are other gamers who have also reported on an Error 75, but so far that error has remained rather reclusive, so it might be some time before she ends up as the flavor of the day. According to Blizzard, they are truly sorry, and have been trying real hard to get things up and running before midnight yesterday, saying, “We’re continuing to work on the issues currently affecting the Americas region, which are resulting in failed login attempts and service issues. While we’ve identified the causes and are working to resolve them, we expect our efforts to require an approximate two hours to complete. We expect game services to fully return by approximately 11:45 p.m. PDT. We apologize for the downtime, and appreciate your continued patience.” Are you still experiencing those errors?

Filed in Gaming . Tags: diablo and Diablo 3.
User Comments