Error 1016 - Ongoing for Months Now

  • Been experience disconeects/error 1016 on and off in frequency for months now. I've tried damn near everything that is suggested to no avail. I am frankly at my wits end with this game as it is the only place I have issues. Worse my brother in the same house as me does not have the same issues.

    Here is my pathping
    Tracing route to 24.105.30.129 over a maximum of 30 hops

    0 Nessus-PC [192.168.254.5]
    1 192.168.254.254
    2 drr01.rdmd.wa.frontiernet.net [184.19.243.239]
    3 50.125.68.197
    4 ae1---0.car01.tamp.fl.frontiernet.net [74.40.1.153]
    5 ae0---0.cbr01.sttl.wa.frontiernet.net [74.40.5.122]
    6 eqix-se2.blizzardentertainment.com [198.32.134.68]
    7 ae1-br01-eqse2.blizzardonline.net [137.221.73.33]
    8 * * *
    Computing statistics for 175 seconds...
    Source to Here This Node/Link
    Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
    0 Nessus-PC [192.168.254.5]
    0/ 100 = 0% |
    1 0ms 0/ 100 = 0% 0/ 100 = 0% 192.168.254.254
    0/ 100 = 0% |
    2 12ms 0/ 100 = 0% 0/ 100 = 0% drr01.rdmd.wa.frontiernet.net [184.19.243.239]
    0/ 100 = 0% |
    3 11ms 0/ 100 = 0% 0/ 100 = 0% 50.125.68.197
    0/ 100 = 0% |
    4 --- 100/ 100 =100% 100/ 100 =100% ae1---0.car01.tamp.fl.frontiernet.net [74.40.1.153]
    0/ 100 = 0% |
    5 13ms 0/ 100 = 0% 0/ 100 = 0% ae0---0.cbr01.sttl.wa.frontiernet.net [74.40.5.122]
    0/ 100 = 0% |
    6 --- 100/ 100 =100% 100/ 100 =100% eqix-se2.blizzardentertainment.com [198.32.134.68]
    0/ 100 = 0% |
    7 13ms 0/ 100 = 0% 0/ 100 = 0% ae1-br01-eqse2.blizzardonline.net [137.221.73.33]

    Trace complete.

    Here is my trace route
    Tracing route to 24.105.30.129 over a maximum of 30 hops

    1 <1 ms <1 ms <1 ms 192.168.254.254
    2 11 ms 15 ms 10 ms drr01.rdmd.wa.frontiernet.net [184.19.243.239]
    3 11 ms 9 ms 9 ms 50.125.68.197
    4 11 ms 14 ms 14 ms ae1---0.car01.tamp.fl.frontiernet.net [74.40.1.153]
    5 11 ms 10 ms 14 ms ae0---0.cbr01.sttl.wa.frontiernet.net [74.40.5.122]
    6 11 ms 14 ms 14 ms eqix-se2.blizzardentertainment.com [198.32.134.68]
    7 10 ms 14 ms 14 ms ae1-br01-eqse2.blizzardonline.net [137.221.73.33]
    8 * * * Request timed out.
    9 58 ms 38 ms 39 ms 137.221.65.6
    10 37 ms 39 ms 39 ms be2-pe02-eqla1.blizzardonline.net [137.221.68.73]
    11 36 ms 39 ms 39 ms 24.105.30.129

    Trace complete.

    As a side note, if I persist and try to continue playing after getting the 1016 error by logging back in and then have the error occur again, upon logging back in the second time I'm greeted with the, I guess, "new player/what's new page" and my characters in my character select list get jumbled up and disorganized.
  • Hey Asponti,

    Have you gone through all of the Disconnect and Latency troubleshooting steps for Diablo 3 yet? If not, I recommend starting with those. If you're still having trouble after that, post your system's DxDiag in a code block and we'll go from there. <code>To put the Diag results in a code block, copy/paste the entire file into your next post, highlight all of it within the post box, then click the </> button. When you add the reply the system diagnostic should appear in a box like this one.</code>
  • Hey Asponti,

    I looked at the connection diagnostics you posted again and the concern I have is that you mentioned you are using a wired connection, but the latency on hop two is more consistent with a wireless connection. Seeing how out of date everything was, I'd also recommend making sure the network card drivers are up to date as well.

    With regard to the step 5 on that Diablo III Disconnection Problems support article, it specifically mentions "closing background applications", however this means doing a selective startup on your system, not just exiting applications. I suggest doing the selective startup as well as going through the advanced steps listed on that page.

    If you're still having trouble after that, post a new Trace Route and a new DxDiag as well as let us know the make and model of your modem.
  • Hey, Asponti!

    I noticed you have Frontier and live on the west coast. Has this gotten worse in the past week? If so, it may be related to the routing issues that have been ongoing.

    People have reported VPN's working to resolve the issue for you. If you would like to test a VPN, that may help rule out the issue.

    We also have recent reports that the issue has been resolved for Frontier customers in Overwatch. Is it any better for you now?
  • Okay, if it is working better now, it was likely related to all the other Frontier customers that were experiencing the same thing. All are reporting that it is back to normal. We are still keeping an eye on it, though. :)