Latency Issues

  • I am getting some crazy high latency issues that are making my game pretty much unplayable. I'm hitting north of 1600 mps at times, and staying pretty constant at around 750 mps. Can anyone offer some insight?

    I did a trace route and a pathping, and while there's some packet loss pretty early on, it looks like I hit some huge spikes further down the path. Is this an issue at Blizzard that I may just have to wait out?

    Trace route

    Tracing route to 24.105.30.129 over a maximum of 30 hops

    1 1 ms 1 ms 1 ms home.Home [192.168.200.1]
    2 4 ms 6 ms 4 ms mh1-dsl-74-215-164-1.fuse.net [74.215.164.1]
    3 3 ms 4 ms 3 ms 216.68.14.100
    4 20 ms 3 ms 4 ms 216.68.14.103
    5 20 ms * 551 ms 216.68.14.131
    6 30 ms 33 ms 26 ms eqix-dc2.blizzard.com [206.126.237.174]
    7 28 ms 31 ms 26 ms ae1-br01-eqdc2.blizzardonline.net [137.221.72.33]
    8 * * * Request timed out.
    9 35 ms 36 ms 998 ms 137.221.65.48
    10 81 ms 81 ms 94 ms 137.221.65.20
    11 * 113 ms 67 ms be2-pe01-eqla1.blizzardonline.net [137.221.68.71]
    12 * 82 ms * 137.221.66.3
    13 * 76 ms 124 ms 24.105.30.129

    pathping

    Tracing route to 24.105.30.129 over a maximum of 30 hops

    0 Badger-Den.Home [192.168.200.245]
    1 home.Home [192.168.200.1]
    2 mh1-dsl-74-215-164-1.fuse.net [74.215.164.1]
    3 216.68.14.100
    4 216.68.14.103
    5 216.68.14.131
    6 eqix-dc2.blizzard.com [206.126.237.174]
    7 ae1-br01-eqdc2.blizzardonline.net [137.221.72.33]
    8 * * *
    Computing statistics for 175 seconds...
    Source to Here This Node/Link
    Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
    0 Badger-Den.Home [192.168.200.245]
    1/ 100 = 1% |
    1 12ms 1/ 100 = 1% 0/ 100 = 0% home.Home [192.168.200.1]
    0/ 100 = 0% |
    2 7ms 1/ 100 = 1% 0/ 100 = 0% mh1-dsl-74-215-164-1.fuse.net [74.215.164.1]
    0/ 100 = 0% |
    3 6ms 4/ 100 = 4% 3/ 100 = 3% 216.68.14.100
    0/ 100 = 0% |
    4 12ms 1/ 100 = 1% 0/ 100 = 0% 216.68.14.103
    8/ 100 = 8% |
    5 36ms 9/ 100 = 9% 0/ 100 = 0% 216.68.14.131
    1/ 100 = 1% |
    6 48ms 10/ 100 = 10% 0/ 100 = 0% eqix-dc2.blizzard.com [206.126.237.174]
    5/ 100 = 5% |
    7 53ms 15/ 100 = 15% 0/ 100 = 0% ae1-br01-eqdc2.blizzardonline.net [137.221.72.33]
  • Hi there my friend,

    I am not seeing any problem in your area or on the server at that node. as for that packet loss, it starts before us, as such the loss later can be responses lost as they pass trough twice for each ping.

    Lets go ahead and start out with checking a few things on the computer.

    First, checking internet options.

    Next, I would like to jump in to a selective startup mode. This will rule out some other software that may be running.

    Make sure to let me know if any of this helps!

    /Nathardrick
  • Hi Daevas,

    Here in support we try to track trends based off reports we received. We do this in effort to keep the network team informed of the problems that are going on so that they can be investigated. At the same time, we try and attack the problem from the user end as well. When it comes to a connection issues, there is always a problem in one of three locations.
    • The server Which we send up when we see the report as well as many other data gathering tools.
    • The ISP Which is the connection point from us to you and from you to us. We do not have much influence here, as such it tends to be a pain point when the problem is there.
    • From the user end This is an area we can try and provide advice for. We try to give troubleshooting advice and things that could cause problems.

    This means we attack all connection problems from both ends, from the server side by tracking connection problems, and from the user end trying to troubleshoot possible causes. You can choose not to do the troubleshooting, but in the end, we are only trying to help you not have a problem when you play. The end goal is to have each and every one of our players have a fun time playing our games, and when a problem arises, to have it resolved as quickly as possible.

    /Nathardrick