I am experiencing incessant dropouts due to this code 1016. Have verified my ISP is not to blame.
As of now, 11:10PM SAST I am unable to join the chat or even log in.
This is so frustrating
Hey ilSalvatore,
Most likely the disconnections are occurring somewhere between your ISP and the Diablo 3 servers. If they are still going on can you run a WinMTR and post the results?
- Download WinMTR
- Right-click on the downloaded .zip folder and select “Extract All”, to extract the files to a new folder.
- Open the new folder that was created, then open the WinMTR_x32 folder.
- Right-click on the WinMTR application and select “Run as administrator”.
- Type the IP address for the Europe game server 185.60.112.157 in the “Host” field.
- Click on “Start” and then launch the game. Allow the test to run for at least 10 minutes. Click on “Stop” when you’re done playing after you have experienced the latency or connection issue.
- Click on “Export TEXT” to save the results as a text document, then post the results.
I will do that too because yesterday i played few nephalem rifts and no problem. Entered GR - 1016, entered again GR - 1016. Then i did some changes suggested in the internet. And after you had restart of the server - 1016 again in GR. Will test tonight.
It’s really odd… this afternoon around 12 - 1 PM SAST I was online w/o dropouts or being 1016’d.
From around 5 PM in this part of the world, I get dropped, at first once in a while then it ramps up the later the night progresses.
This is me when i got disconnected after playing couple of hours.
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| my. totolink .net - 0 | 5404 | 5404 | 0 | 0 | 9 | 0 |
| 109.160.41.1 - 1 | 5396 | 5393 | 0 | 1 | 14 | 1 |
| core1 .burgasnet .com - 1 | 5387 | 5382 | 1 | 1 | 15 | 1 |
| mail .bt-varna .com - 31 | 2430 | 1683 | 8 | 15 | 292 | 180 |
| ae52-202.bar1.Sofia1.Level3 .net - 1 | 5313 | 5289 | 8 | 10 | 81 | 8 |
| ae-1-3104.edge7.Amsterdam1.Level3 .net - 1 | 5252 | 5212 | 56 | 71 | 401 | 71 |
| BLIZZARD-EN.edge7.Amsterdam1.Level3 .net - 1 | 5275 | 5241 | 57 | 72 | 773 | 68 |
| ae1-br02-eqam1.as57976 .net - 4 | 4675 | 4512 | 56 | 162 | 4792 | 66 |
| 137.221.78.83 - 1 | 5341 | 5324 | 46 | 49 | 159 | 47 |
| 137.221.66.41 - 1 | 5306 | 5280 | 47 | 48 | 104 | 48 |
| 185.60.112.158 - 1 | 5271 | 5236 | 47 | 47 | 62 | 48 |
|____________|||||||
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider
Hey there Donatello, thanks for posting your WinMTR test data. The data here shows 1% packet loss beginning on the second “hop” and persisting through all subsequent hops:
| 109.160.41.1 -
1 | 5396 | 5393 | 0 | 1 | 14 | 1 |
With that in mind, this would be an issue to bring up to your ISP. They may adjust specific security/firewall settings on your modem or temporarily replace the device to narrow it down further. Keep in mind that you can request to speak with a “level 2 or level 3 technician” when contacting the ISP, as the front-line representatives typically only have access to basic diagnostics and troubleshooting tools.
I hope this helps get things fixed up so you can get back to playing uninterrupted!
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
Local IP
| 192.168.1.100 - 0 | 2272 | 2272 | 0 | 0 | 0 | 0 |
ISP
| 10.22.1.56 - 0 | 2272 | 2272 | 1 | 2 | 116 | 2 |
| 41.76.34.25 - 1 | 2207 | 2190 | 1 | 3 | 80 | 1 |
| 41.77.200.105 - 2 | 2179 | 2155 | 1 | 3 | 82 | 3 |
Toplevel ISP
| 41.66.132.237 - 1 | 2206 | 2189 | 1 | 6 | 134 | 5 |
Toplevel ISP - note increased ping lag
| 41.84.13.14 - 3 | 2047 | 1990 | 170 | 174 | 265 | 175 |
| 80.249.208.83 - 2 | 2119 | 2080 | 172 | 179 | 875 | 174 |
|note 4000+ ms ping lag: 137.221.78.33 - 5 | 1942 | 1862 | 171 | 195 | 4027 | 173 |
| 137.221.78.75 - 3 | 2071 | 2020 | 171 | 176 | 295 | 172 |
B-net server
| 185.60.112.157 - 4 | 2031 | 1970 | 171 | 174 | 279 | 175 |
|____________|||||||
Hey ilSalvatore! Thanks for posting that WinMTR data. The problem shown here is similar to Donatello’s issue, except the packet loss begins on the third hop in your test:
| 41.76.34.25 -
With that in mind, the situation is similar, and the same applies – you will need to reach out to your ISP to determine what’s causing the packet loss on that third hop. You can request to speak with a “level 2 or level 3 technician” when contacting the ISP, as the front-line representatives typically only have access to basic diagnostics and troubleshooting tools. I also encourage forwarding your WinMTR test data to whomever you speak with, because if they’re able to interpret the data, it may help them resolve the issue more quickly.
I sincerely hope this information helps get things fixed up for you!
How do you explain that a huge number of players (at least European players) experience that problem since s20? I have never had that issue before but after new patch I am constantly getting error 1016 on European server but on American everything is just fine. Why are you trying to tell us it’s a mistake on our side? Every Blizzard member just copy/paste “solutions” that don’t help at all.
Y’all got d Dosd and now I can’t connect to my friends and my nat is open just like this guys.
It’s not our isp blizzard, the server for diablo is messed up and it needs to be looked at.
That’s what they do.
They never actually answer directly.
That’s what is do frustrating, might as well be talking to a robot.
I think it is mostly because many people are at home and the internet provider is overwhelmed.
I played little at the midnight hours and it was just fine.
That 1% package lost is something normal. Usually i lose that 1% at the start and it is not like you can make it back.
When you see how many are sent and received - 5396 | 5393 - only 3 packs and that was at beginning of connecting.
So that is not a valuebale reason for 1016.
The thing is that you can continue play when you get the 1016 error. So can you just not show the message? It is not like we are disconnected. We are still connected and playing and that message is at the middle of the screen.