Hi Everyone, How do you deal with error 1016? Please let me know if anyone can. Thanks.
Hey Jamuus,
Error 1016 is a generic error for “you have been disconnected”. Disconnections can happen for a lot of different reasons, but we generally recommend trying our Diablo III Disconnection Troubleshooting first.
Since this error can also be caused by problems between your internet provider and the Diablo 3 servers, if the troubleshooting doesn’t help it would be a good idea to run a WinMTR to “capture” how the connection looks when a disconnect occurs.
the same problem and not the first time at this time.
pingtestlive"dot"com shows a problem on your server
Hey HrenovBot,
I just checked and didn’t have any problems logging into the EU region of D3. We also aren’t aware of any similar widespread reports on our side from other players. You can also check this by visiting the EU forums here.
However, we have seen similar situations in the past were a local or regional ISP in a specific EU country started blocking or having issues reaching our servers. In this case, we would need to gather some more details in order to pinpoint the problem. Please reply with that WinMTR test. If possible, I would also recommend testing another network like a mobile hotspot, which can help isolate the problem.
Check this address? 185.60.112.157
Yeah, I tested that IP and had no problems sending or receiving data.
the problem is short-term. Throws it out of the server and in a minute you can log in.
where to forward the test result?
ps
Since you are silent, I will post it here.
It’s just inconvenient, it sees hopes as links and doesn’t allow …
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|---|---|---|---|---|---|---|
| router.asus.*com - 0 | 554 | 554 | 0 | 0 | 3 | 0 |
| 10.0.255.255 - 0 | 554 | 554 | 0 | 4 | 75 | 31 |
| 194.33.189.21 - 0 | 554 | 554 | 0 | 2 | 66 | 1 |
| kiev-nt-b1-ae8-vlan3138.fiord.*net - 0 | 554 | 554 | 0 | 0 | 11 | 0 |
| amsterdam-nik-b1-xe0-0-2-vlan3831.fiord.*net - 0 | 554 | 554 | 38 | 38 | 71 | 39 |
| 80.249.208.83 - 0 | 554 | 554 | 36 | 40 | 384 | 36 |
| ae1-br02-eqam1.as57976.*net - 1 | 546 | 542 | 36 | 67 | 4853 | 36 |
| et-0-0-67-pe02-eqam1.as57976.*net - 0 | 554 | 554 | 37 | 40 | 115 | 37 |
| 185.60.112.157 - 0 | 554 | 554 | 37 | 37 | 42 | 38 |
| ________________________________________________ | ______ | ______ | ______ | ______ | ______ | ______ |
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider
HrenovBot,
This test doesn’t show any issues. I assume it was run while you were having the issue? If not, it’ll need to be re run. Either way, it’s possible there’s some kind of caching issue causing the problem. You can try power cycling your connection to see if it clears the cache and fixes the problem for you.