Get the Desktop App for Battle.net Now
- All your games in 1 place
- Log in once
- Automatic game updates
Welcome to the Technical Support forum for Diablo III! This forum exists to provide Diablo III players with a place to discuss technical issues both with each other, and with Blizzarrd Support staff.
Players are encouraged to ask questions, share advice, and participate in on-going technical discussions here. Accordingly, it is of utmost importance that all players treat each other with respect and courtesy. For more information, please review the Forum Code of Conduct and the Forum Guidelines detailed in a post below.
Edited by Lurdlespor on 02/10/2013 14:50 BST
The Diablo III Technical Support Forum is not intended to replace tickets, telephone queues or live chat support. In some situations you may need to contact our customer service teams directly.
Blizzard Technical Support staff regularly monitors this forum and replies to threads and queries, however we are not able to reply to all threads. If you require assistance urgently, then in some cases contacting our support staff directly may be the optimal course.
Our working hours are:
Monday: 09:00 - 19:00
Customer Service Forum Representatives
Edited by Lurdlespor on 27/11/2013 09:38 GMT
In addition to the Forum Code of Conduct, here are some common courtesy guidelines to follow. While these do technically fall within the bounds of the Code of Conduct, there has been some confusion regarding what is and is not allowed. These guidelines should help clear up any misconceptions.
Do not post in all capital letters, use excessive punctuation, etc.
Using the words Blizzard, Blue, or any community team members name in a thread topic is frowned on.
Note that threads discussing e.g. the Blizzard authenticator or Blizzard’s latest press release are allowed to have Blizzard in the title as it’s then relevant to the discussion.
Posting IBL, IBTL, or its variants constitutes spamming.
Posting TLDR or L2P constitutes as trolling
Do not bump posts.
Petition posts are frowned on.
Multiple threads on the same topic will be deleted
Do not post about locked or deleted threads.
Suspensions add up
If you have a post to report, use the down thumb next to the post. Should you wish to report a post for a sticky, please use the "Vote Sticky" at the top right of the thread.
Don't necro posts
Do not 'Name and Shame'
Edited by Lurdlespor on 21/09/2014 16:53 BST
Writing an Effective Post
Before you make your post:
1) Read the Stickies: Many issues we see pop up on the forums are covered in our stickies and a quick glance in the relevant sticky can often resolve your problem without having to wait on a response to your forum thread which can often take hours.
2) Check the FAQ: We have a detailed Support site with support articles covering many common and not so common issues experienced by our players:
3) Search the Forum: There is a good chance, if your issue is not covered in a sticky or support article, that someone else has experienced the same problem in the past and made a post about it, searching the forum for an error number or some of your symptoms can often turn up some troubleshooting advice that may solve your problem.
Making your Post
If the existing advice in the stickies, support site and forum didn’t manage to resolve your problem, or you have trouble following that advice, it is time to create a new forum post, and the following steps can help ensure speedy identification and assistance for your issue from both players and our support staff:
1) Write a descriptive subject: Letting players and Support Staff know quickly and easily the sort of problem you have can greatly increase the likelihood and speed of an effective response. Use of categorisation and part of any error messages you receive can be very effective, for example:
Game is stuck at ‘Updating’ is much clearer than Game doesn’t work
2) Describe the steps you have already taken: Now that you have checked the stickies, FAQ and searched the forum, let us know in your post that you have done that and what steps exactly you have already tried so that other people reading your post do not present you with possible solutions that you know are not of use.
3) Provide relevant details: It can greatly speed up diagnosis of a problem if you already include relevant information about your computer and connection. We have a support article on finding important diagnostic information here:
Providing information such as Processor, RAM, Operating System, Graphics, Sound and Network Card models can help to narrow down possible causes of your issues.
For connection issues, please see our Connection Information post for the information we require to assist you with connection related queries.
4) Keep checking the forum: Keep looking at threads posted by other users to check if any others are experiencing similar problems. They may have tried some steps that may resolve your problem.
5) Be patient: Our Support staff will do their best to answer as wide a range of forum posts as possible, and will endeavour to reply to your post, but if you require a quick response or you’re out of the working hours as listed above, please contact our support staff directly.
Edited by Lurdlespor on 02/10/2013 15:14 BST
If you experience connection related issues when playing Diablo III, the first resource we would recommend is our Support Site:
However if you continue to experience connectivity issues after following the advice in our support articles, please don't hesitate to make a forum post. We would first recommend making sure you consult our advice in Writing an Effective Post here:
In addition to this information, we may require further details in order to accurately verify an issue or locate where the issue lies.
In particular, the information we normally require for troubleshooting connection issues is as follows:
Modem (and firmware version if known) -
Router (and firmware version if known) -
Network device (Driver version if available) -
Type of connection used (Wireless / USB / Ethernet) -
Operating System -
Security Software installed (Firewall, Anti-Virus) -
Traceroute to your region - battle.net/support/article/496
Pathping to your region - battle.net/support/article/718
PLEASE NOTE: The traceroute and pathping may take some time to complete correctly, please allow at least five minutes for these commands to finish. Please also run the pathping/traceroute when you're experiencing the issue, as this will give the most accurate results.
Edited by Lurdlespor on 02/10/2013 14:49 BST
You can follow all Blizzard Entertainment Customer Support Europe news and updates on Twitter! We provide updates on maintenance, service issues and outages and we also endeavour to bring you the latest news and relevant support information on current world (of Warcraft) events.
The feed is available in English, German, French, Spanish, Russian, Portuguese, Italian and Polish.
Please follow and if you have any feedback for us regarding our Twitter feeds then you can e-mail it to CSTwitterFeedbackEU@blizzard.com.
We like to use a lot of #tags on Twitter which help to spread our messages to as wide an audience as possible and also acts as a helpful consolidation tool for our community. Although the concept of #tags is a very natural one, and tags (and the way they are used) generally evolve over time, we do have a few set tags that we regularly use on our feeds.
To help newcomers and clear up any confusion, here is a list of the #tags we most commonly Tweet:
More to be added as required...
Edited by Lurdlespor on 02/10/2013 14:46 BST
Additional Social Media Resources
These are community-based social network resources for our 4 current games.
Additionally, we have a dedicated @BlizzardCareers Twitter page for those of you interested in available positions here at Blizzard Entertainment.
Threats of violence. We take these seriously and will alert the proper authorities.
Posts containing personal information about other players. This includes physical addresses, e-mail addresses, phone numbers, and inappropriate photos and/or videos.
Harassing or discriminatory language. This will not be tolerated.