Lag Spikes in OW and D3

  • For the past few nights (around 8-10 pm est) (usually doesn't happen during the day but it has a couple times) I have been getting massive lag spikes while playing overwatch and D3 (I also play HS but they are harder to notice due to the nature of the game).
    These are represented by stuttering in place in OW and moving around in D3 firing nothing and no mobs moving but just the attack animation occuring. They then result in a jump forward (and usually a death). I have current Nvidia drivers and have restarted router, comp and all the usual standard solutions. I have Time Warner (spectrum) internet.
    Here are my path ping and trace. Thanks for the help.

    Tracing route to 24.105.30.129 over a maximum of 30 hops

    0 DESKTOP-9IAMGEO.ma.rr.com [192.168.0.2]
    1 192.168.0.1
    2 142.254.154.221
    3 ae62.trrhin6402h.midwest.rr.com [74.128.4.245]
    4 be30.clmkohpe01r.midwest.rr.com [65.29.11.130]
    5 bu-ether15.chctilwc00w-bcr00.tbone.rr.com [66.109.6.68]
    6 bu-ether11.chcgildt87w-bcr00.tbone.rr.com [66.109.6.20]
    7 0.ae4.pr1.chi10.tbone.rr.com [66.109.1.66]
    8 66.109.9.149
    9 37.244.1.33
    10 * * *
    Computing statistics for 225 seconds...
    Source to Here This Node/Link
    Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
    0 DESKTOP-9IAMGEO.ma.rr.com [192.168.0.2]
    0/ 100 = 0% |
    1 0ms 0/ 100 = 0% 0/ 100 = 0% 192.168.0.1
    5/ 100 = 5% |
    2 173ms 7/ 100 = 7% 2/ 100 = 2% 142.254.154.221
    0/ 100 = 0% |
    3 161ms 7/ 100 = 7% 2/ 100 = 2% ae62.trrhin6402h.midwest.rr.com [74.128.4.245]
    0/ 100 = 0% |
    4 185ms 7/ 100 = 7% 2/ 100 = 2% be30.clmkohpe01r.midwest.rr.com [65.29.11.130]
    0/ 100 = 0% |
    5 212ms 5/ 100 = 5% 0/ 100 = 0% bu-ether15.chctilwc00w-bcr00.tbone.rr.com [66.109.6.68]
    1/ 100 = 1% |
    6 197ms 6/ 100 = 6% 0/ 100 = 0% bu-ether11.chcgildt87w-bcr00.tbone.rr.com [66.109.6.20]
    0/ 100 = 0% |
    7 208ms 7/ 100 = 7% 1/ 100 = 1% 0.ae4.pr1.chi10.tbone.rr.com [66.109.1.66]
    0/ 100 = 0% |
    8 190ms 7/ 100 = 7% 1/ 100 = 1% 66.109.9.149
    0/ 100 = 0% |
    9 194ms 6/ 100 = 6% 0/ 100 = 0% 37.244.1.33

    Trace complete.

    Tracing route to 24.105.30.129 over a maximum of 30 hops

    1 <1 ms <1 ms <1 ms 192.168.0.1
    2 23 ms 72 ms 12 ms 142.254.154.221
    3 29 ms 21 ms 21 ms ae62.trrhin6402h.midwest.rr.com [74.128.4.245]
    4 27 ms 24 ms 21 ms be30.clmkohpe01r.midwest.rr.com [65.29.11.130]
    5 45 ms 40 ms 46 ms bu-ether15.chctilwc00w-bcr00.tbone.rr.com [66.109.6.68]
    6 34 ms 39 ms 40 ms bu-ether11.chcgildt87w-bcr00.tbone.rr.com [66.109.6.20]
    7 40 ms 31 ms 32 ms 0.ae4.pr1.chi10.tbone.rr.com [66.109.1.66]
    8 33 ms 40 ms 38 ms 66.109.9.149
    9 78 ms 88 ms 79 ms 37.244.1.33
    10 * * * Request timed out.
    11 80 ms 80 ms 80 ms 24.105.30.129

    Trace complete.
  • Hello Merlin,

    Thanks for posting the detailed info and for the tracroute/pathping. I do see an issue showing up in the pathping test:

    Computing statistics for 225 seconds...
    Source to Here This Node/Link
    Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
    0 DESKTOP-9IAMGEO.ma.rr.com [192.168.0.2]
    0/ 100 = 0% |
    1 0ms 0/ 100 = 0% 0/ 100 = 0% 192.168.0.1
    5/ 100 = 5% |
    2 173ms 7/ 100 = 7% 2/ 100 = 2% 142.254.154.221
    0/ 100 = 0% |
    3 161ms 7/ 100 = 7% 2/ 100 = 2% ae62.trrhin6402h.midwest.rr.com [74.128.4.245]
    0/ 100 = 0% |
    4 185ms 7/ 100 = 7% 2/ 100 = 2% be30.clmkohpe01r.midwest.rr.com [65.29.11.130]
    0/ 100 = 0% |


    What this is showing us is that there appears to be an issue starting between the 1st and 2nd "hop" in the connection path. The issue is causing high latency (173ms) very early on, and the bigger issue is the data loss which is between 5-7% packet loss at that point in the connection path. This would definitely cause the type of issues that you're describing.

    Since you mentioned that it only tends to happening in the evenings/nights or during "primetime" for internet usage it is likely an internet provider issue affecting your specific area. The 1st hop in the test is your router, so the 2nd hop is usually the ISP box outside your home or down your street. I would definitely recommend giving Spectrum / Time Warner a call so they can sent a technician out to investigate this for you.

    Hopefully this info helps!