Intermittent Lag Spikes Daily for a Week Now

For about a week now, I will get 10-45 second lag spikes and rubberbanding occurring from every few minutes to a couple times an hour. I only get this lag in WoW, no other game do I have this issue. I’ve tried restarting modem/router multiple times, power cycled all my devices, reset the modem/router, ran the scan and repair tool, reinstalled WoW, uninstalled all addons, adjusted framerates, adjust graphics, updated all drivers, and on, and on…

I have Spectrum which did have the outage a week ago but like I said, no other game, streaming service, etc. has this issue. Just WoW. To note, Spectrum just forced us to change out our hardware. Is there a possible issue there?

Hey there Universe! Let’s go ahead and have you run a WinMTR network test while the problem occurs in-game so that we can further investigate potential network-related issues between your computer and the game server. Here are the instructions:

  1. Download the tool from this page
  2. Enter the game IP into the “host” field. The IP address for our games are listed on the WinMTR instructions page
  3. Start the test and play the game for at least 15 minutes. Ensure the problem happens while the WinMTR tool is running.
  4. After recording the problem data, click “export text” and save the WinMTR file in an easy to find location.
  5. Once you have that made, open the file. You’ll need to copy and paste the contents of the Text document into the post, and put four Tilde (~) marks above the WinMTR. It’ll look like this:
WinMTR goes here

If you have issues pasting here, please use Pastebin and post the link (ex: Pastebin (dot) com/123456).

|------------------------------------------------------------------------------------------|

|                                      WinMTR statistics                                   |

|                       Host              -   %  | Sent | Recv | Best | Avrg | Wrst | Last |

|------------------------------------------------|------|------|------|------|------|------|

|                               plume.lan -    0 | 2621 | 2621 |    0 |    0 |   11 |    0 |

|                          142.254.177.45 -    0 | 2622 | 2622 |    5 |   12 |   59 |   10 |

|          agg55.lsdwcaro02h.socal.rr.com -    1 | 2618 | 2617 |    6 |   13 |   50 |    9 |

|          agg21.lamrcadq02r.socal.rr.com -    1 | 2604 | 2599 |    7 |   18 |   59 |   15 |

|          agg28.tustcaft01r.socal.rr.com -    1 | 2611 | 2608 |   10 |   19 |   66 |   18 |

|           ae-5-0.cr0.chi10.tbone.rr.com -    1 | 2617 | 2616 |   10 |   19 |   64 |   17 |

|                            66.109.5.241 -    1 | 2617 | 2616 |   11 |   19 |  100 |   12 |

|                            66.109.9.161 -    1 | 2607 | 2603 |    8 |   20 |  111 |   19 |

|              ae1-br01-eqla1.as57976.net -    1 | 2575 | 2565 |   21 |  247 | 4679 |   78 |

|                   No response from host -  100 |  530 |    0 |    0 |    0 |    0 |    0 |

|        et-0-0-0-pe03-swlv10.as57976.net -    1 | 2618 | 2617 |   15 |   23 |  147 |   25 |

|                           137.221.105.2 -    1 | 2614 | 2612 |   14 |   21 |   66 |   16 |

|________________________________________________|______|______|______|______|______|______|

   WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider

Hey Universe,

Thank you for taking the time to run that WinMTR network test. The test here is showing 1% packet loss beginning at the third “hop”, which could be what is causing the intermittent spikes:

plume.lan - 0 | 2621 | 2621 | 0 | 0 | 11 | 0 |
142.254.177.45 - 0 | 2622 | 2622 | 5 | 12 | 59 | 10 |
agg55.lsdwcaro02h.socal.rr(dot)com - 1 :warning: | 2618 | 2617 | 6 | 13 | 50 | 9

Does the problem persist while testing an alternate network?

If the issue is resolved when testing an alternate network such as a mobile hotspot or VPN, at that point we can be sure that the issue is isolated to the primary network. In these situations, we encourage contacting the Internet Service Provider (ISP) for assistance determining what is causing the issue to occur on that specific network. I always recommend requesting to speak with a “level 2 or level 3 technician” when contacting the ISP since the front-line representatives typically only have access to basic diagnostics and troubleshooting tools. I also encourage sharing the WinMTR data with whomever you speak with when contacting the ISP, because if they’re able to interpret the data, this may enable them to diagnose and resolve the issue more quickly.

I hope this information helps get you back in-game smoothly! Let us know if you have any questions going forward.