Latency problem S9

  • Latency problem Big one its going from(350 to 2000) i done all i cant still have problem.I just cant play d3 at all.Other games work fine.
  • Hey Woilflord,

    Let's see what we can do to get the latency back down. To find out what may be causing this latency please run and post the results from a WinMTR. Also please let us know what steps you have tried.

    WinMTR
      1) Download WinMTR - http://winmtr.net/download-winmtr/
      2) Unzip the WinMTR.zip file to the Desktop.
      3) Open the WinMTR folder and select the one corresponds to your version of Windows (32 or 64 bit version).
      4) Run the WinMTR.exe
      5) Type the IP address you would use to run a trace route in the "Host" - https://battle.net/support/article/496
      6) Click on "Start" while playing
      & Run for at least 10 minutes then click on "Stop" in WinMTR
      7) Click on "Export text" and save to a text file.
      8) Copy and paste the contents of whole file here.
      9) Click on "Start"
      10) Run for 10 minutes then click on "Stop" in WinMTR
      11) Click on "Export text" and save to a text file.
      12) Copy and paste the contents of whole file here.
  • DustinSouls- The test does show that there is really large latency spike after the connection leaves your home router. Spikes this high will cause issue for the game's connection. With where the latency spikes start you may need to contact you ISP to fix this. Before you do try the steps below. They could help out.

    | 192.168.1.1 - 0 | 1101 | 1101 | 0 | 0 | 33 | 0 |
    | Destination host unreachable. - 1 | 1070 | 1062 | 0 | 37 | 2564 | 13 |
    | 10.108.208.1 - 1 | 1066 | 1058 | 6 | 48 | 2575 | 8 |


    theG57 The tests are also showing latency spikes at the first connection with the ISP. There is a little bit of a spike at the home router. Not too bad but could indicate there is issues with the router. The steps below may also help out with these spikes.

    | home.Home - 0 | 289 | 289 | 1 | 2 | 86 | 2 |
    | LR-DYN-67-231-160-1.prtcnet.com - 1 | 285 | 284 | 9 | 18 | 379 | 12 |
    | dsl-61.d01.ilclch.infoave.net - 1 | 285 | 284 | 14 | 67 | 696 | 14 |


    reapeRmikU The test shows there is some really high packet loss starting at the home router. This may be do to a Quality of Service (QoS) setting in the router. Disabling it may help. Also you can try the steps below to help stop this packet loss.

    | 192.168.254.254 - 87 | 5950 | 784 | 0 | 0 | 5 | 0 |
    | 10.91.18.38 - 87 | 5949 | 784 | 0 | 19 | 102 | 17 |


    • In the router please disable any Quality of Service (QoS), UPnP, game mode or adware protection options. The manufacture of the router should have instructions on how to do this. Usually it would be on their website.

    • Wireless connections are not the most stable thing in the world. Anything from a cellphone to a microwave oven can disrupt the signal. See if using a wired connection to see if it will help with the connection.

    • If you have a separate modem and router you can try bypassing the router and connecting your computer to the modem. This may help with the connection and will let you know if it is specifically the router that is causing the trouble.

    • Old firmware on your modem and router can cause issues when your network needs to deal with complex game connections. The manufacturer's website for your hardware should have firmware, as well as instructions on how to apply firmware updates.
  • DustinSouls - By passing the router was not meant a permanent fix for this. Just a way to test if the router is causing troubles. With were the latency spikes are showing it is not likely your home router. The troubleshooting steps are more of a just to be on the safe side. The latency spikes are showing with the first connection of your ISP. You will likely need to contact them to get this fixed.

    PHXiblade The test does show some latency spikes at the beginning of the connection. This is a bit high. What is more concerning is when your ISP hands the connection off to other ISPs the overall latency increases and there is a large amount of packet loss. This may be hard to get around. You may need to contact your ISP to let them know there is issues with their peering partners. Before you do I recommend to be on the safe side power cycle the network equipment and flush the DNS.

    | 172.16.9.213 - 1 | 584 | 579 | 3 | 16 | 223 | 4 |
    | 10.254.254.21 - 1 | 591 | 588 | 6 | 19 | 212 | 13 |
    | 10.200.200.2 - 1 | 596 | 594 | 43 | 56 | 243 | 49 |
    | 61.8.59.53 - 11 | 424 | 379 | 0 | 58 | 265 | 63 |
    |gi1-0-0.gw5.hkg3.10026.telstraglobal.net - 6 | 488 | 459 | 42 | 56 | 252 | 54 |
    | ip-61-14-158-23.asianetcom.net - 7 | 472 | 439 | 191 | 204 | 396 | 208 |