I keep getting disconnected with error code 1016 , tried to submit a ticket but there is error when I press ‘SUBMIT’ , the game errors don’t go away for a week since i returned to game, and the fact that I can’t reach support through ticket system to tell about my problem doesn’t make it funny, its infuriating HELP. Any other online game works fine and there are no issues on physical network layer.
no “solution” from articles and forum discussions work, here’s the MTR
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| 192.168.0.1 - 0 | 559 | 559 | 0 | 0 | 2 | 0 |
| 185.163.193.129 - 2 | 871 | 854 | 0 | 0 | 66 | 0 |
| 100.64.1.2 - 3 | 867 | 849 | 0 | 0 | 15 | 0 |
| 100.64.1.1 - 2 | 871 | 854 | 0 | 0 | 61 | 0 |
| 185.163.195.250 - 2 | 871 | 854 | 0 | 0 | 14 | 0 |
|host-static-212-0-217-253.moldtelecom.md - 3 | 867 | 849 | 1 | 3 | 19 | 2 |
|host-static-212-0-217-210.moldtelecom.md - 3 | 863 | 844 | 2 | 3 | 16 | 5 |
|host-static-212-0-217-210.moldtelecom.md - 3 | 851 | 829 | 2 | 3 | 21 | 4 |
| 212-0-199-110.agg4.C-IGW-2.telco.md - 4 | 815 | 784 | 2 | 4 | 21 | 4 |
| ae5.RT.HST.ODS.UA.retn. net - 3 | 855 | 834 | 8 | 10 | 41 | 9 |
| ae4-2.RT.EQX.FKT.DE.retn. net - 3 | 847 | 824 | 46 | 48 | 84 | 48 |
| pr01.eqfr5.blizzardonline. net - 5 | 795 | 759 | 42 | 46 | 117 | 42 |
| ae1-br01-eqfr5.as57976. net - 5 | 787 | 750 | 45 | 81 | 2758 | 81 |
| et-0-0-2-br01-eqam1.as57976. net - 8 | 640 | 590 | 49 | 889 | 4655 | 58 |
| 137.221.78.79 - 3 | 839 | 814 | 45 | 49 | 164 | 48 |
| 185.60.112.157 - 5 | 807 | 774 | 48 | 48 | 72 | 50 |
This is the first hop that has packet loss, which continues thoughout the rest of the trace. A WHOIS lookup of that IP address… https://whois.domaintools.com/185.163.193.129 …shows that to be a Moldovian ISP. Reset your local network equipment (hub / router) and PC and re-run the trace. If that doesn’t help, speak to your ISP and ask them to investigate, showing them this trace.
1 Like
so you are going to completely ignore this abysmal latency on blizzard side just because of 2-3% loss which is absolutely normal and all other games work perfectly fine ??
| ae1-br01-eqfr5.as57976. net - 5 | 787 | 750 | 45 | 81 | 2758 | 81 |
| et-0-0-2-br01-eqam1.as57976. net - 8 | 640 | 590 | 49 | 889 | 4655 | 58 |
Meteor’s analysis is correct.
The data loss at hop 2 (185.163.193.129) is NOT normal.
Imagine a request sent to server get lost on the way, the server will not get the request and won’t return a respond to the client. So, the game client won’t get a response and throw 1016 error on timeout.
The as57976.net nodes are configured to depriorize ICMP message (used by ping, WinMTR, etc). Their data are irrelevant. The proof is the following hops were normal.
Also, we are just normal players, not Blizzard support (they write in blue text). You can ignore us if you don’t believe.
1 Like
sorry , didn’t mean to be rude , gonna kick the ISP anyway just in case
I’m getting this constantly as well, i’ve noticed alot of people have this issue and yet we’re told it’s our computer. I don’t think so, my computer is just under 5 months old, it’s a gaming computer, and no other online game logs me out period unless of a internet connection. Seriously blizzard this error needs addressing and fixing, you can’t keep passing the buck to us every time this gets reported. Keep in mind diablo 3 is a very old game now and it still has this error code pop up.
I am suddenly getting this issue without any system changes, tried troubleshooting, reset modem, flushed dns, reset wifi adapter, checked to make sure d3 was in the clear in firewall, literally nothing has changed on my end except a battle.net update and now I cant stay connected for even 10 minutes without getting 1016 error and d3 taking me back to the login page. PLEASE fix this blizzard this is clearly your fault.
You’ve resurrected a thread from two months ago and, if you look at their WinMTR trace and our analysis of it, the problem was clearly the OP’s ISP which was showing 2-3% packet loss at the first non-local network hop, and all subsequent hops onwards.
Please follow the instructions in this article…
Running WinMTR
Paste the results of the trace into the thread so that we can take a look and see which network hop(s) might be causing your disconnection issues.
- Close Diablo 3
- Search for “Command Prompt” by typing it in the Start menu. Right-click the first entry which will pop up as a search result and select the “Run as administrator”.
- Type in: ipconfig/flushdns press enter
- Type in: ipconfig/release press enter
- Type in: ipconfig/release6 press enter
- Type in: ipconfig/renew press enter
- Open Diablo 3
Check if the Diablo 3 error code 1016 issue still occurs.
Disable IPV6
IPV6 is a new Internet Protocol that although is advantageous to use is incompatible with older games. If this is what’s causing the problem then you should try to disable it.
- Use the Windows + R key combination to bring up the Run dialog box.
- Type “ncpa.cpl” in the bar and tap OK in order to open the Internet Connection settings item in Control Panel.
- Double-click on your active Network Adapter.
- click Properties and locate the Internet Protocol Version 6 entry on the list. Disable the check box next to this entry and click OK.
- Restart your computer.