I have been experiencing sudden significant lag issues recently. I have worked through the troubleshooting tips recommended and none have worked yet. I hooked up an ethernet cable and have ran the WinMTR program. My results are below:
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| 10.0.0.1 - 1 | 1255 | 1252 | 6 | 13 | 674 | 10 |
| 96.120.84.213 - 1 | 1237 | 1229 | 8 | 13 | 688 | 9 |
|ae-251-1204-rur02.visalia.ca.ccal.comcast.net - 1 | 1263 | 1262 | 8 | 14 | 594 | 10 |
| ae-9-ar01.fresno.ca.ccal.comcast.net - 1 | 1251 | 1247 | 10 | 16 | 654 | 10 |
|be-33667-cr02.losangeles.ca.ibone.comcast.net - 1 | 1247 | 1242 | 17 | 22 | 655 | 17 |
|be-2212-pe12.losangeles.ca.ibone.comcast.net - 1 | 1251 | 1247 | 17 | 22 | 571 | 19 |
|as12989-1-c.600wseventh.ca.ibone.comcast.net - 1 | 1251 | 1247 | 17 | 25 | 570 | 17 |
| ae1-br01-csla1.as57976.net - 1 | 1252 | 1248 | 17 | 26 | 626 | 20 |
| No response from host - 100 | 256 | 0 | 0 | 0 | 0 | 0 |
| 137.221.68.79 - 1 | 1247 | 1242 | 16 | 23 | 585 | 17 |
| lax-eqla1-ia-bons-02.as57976.net - 1 | 1255 | 1252 | 17 | 22 | 572 | 19 |
| 24.105.30.129 - 1 | 1255 | 1252 | 16 | 20 | 214 | 21 |
|________________________________________________|______|______|______|______|______|______|
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider
The problem is at hop 1. There was 1% data packet lost and high latency.
At first, I thought you were using wireless, but you said you were using ethernet cable. Let’s go thru the numbers.
The best ping 6 is abnormally high for wired connection. We expect 0 or 1 here.
The worst ping 674 indicates … no need further explanation … it is why you get lag spikes.
So, either your computer or router has problem.
To isolate the problem, try
- powering off both router and modem for 10 minutes. Then re-test to see if any improvement.
- bypassing the router. i.e. plug ethernet cable from computer to modem directly. If the problem gone, that means a faulty router.
- disabling background jobs (e.g. auto-update, overlay, antivirus, …).
Above steps are covered by the troubleshooting support article. Refer it for detailed procedures:
Edit: also try updating driver of the network card from the manufacturer.
Awesome. Thanks for showing me that. I’ll give that a go and see what comes up.
I see I am not the only one with lag issues, has gotten really bad the past couple weeks. Did a basic tracert to see what was going on as nothing else appears to lag this bad. Feels like dialup days…
Note I had to remove a few (.) so it wasn’t trying to post links.
Tracing route to 24.105.30.129 over a maximum of 30 hops
1 <1 ms <1 ms <1 ms 192.168.1.1
2 <1 ms <1 ms <1 ms 192.168.200.1
3 36 ms 21 ms 30 ms 140.190.1.1
4 * 26 ms 42 ms 104.218.221.129
5 39 ms 35 ms 32 ms 140.190.22.114
6 27 ms 26 ms 27 ms 192.168.4.6
7 * 35 ms 38 ms 192.168.4.10
8 40 ms 36 ms 38 ms 192.168.4.13
9 37 ms 39 ms 34 ms xe-4-3-2.bar1.Minneapolis2.Level3net [4.14.210.57]
10 * * * Request timed out.
11 84 ms 44 ms 48 ms BLIZZARD-EN.ear7.Chicago2.Level3net [4.7.196.134]
12 * * * Request timed out.
13 176 ms 85 ms 137 ms et-0-0-3-br02-eqla1.as57976net [137.221.65.4]
14 149 ms 116 ms 160 ms 137.221.68.91
15 109 ms 95 ms 125 ms lax-eqla1-ia-bons-03.as57976net [137.221.66.7]
16 123 ms 119 ms 111 ms 24.105.30.129
Trace complete.
Second round:
Tracing route to 24.105.30.129 over a maximum of 30 hops
1 <1 ms <1 ms <1 ms 192.168.1.1
2 1 ms <1 ms <1 ms 192.168.200.1
3 16 ms 26 ms 19 ms 140.190.1.1
4 133 ms 48 ms 42 ms 104.218.221.129
5 361 ms 84 ms 70 ms 140.190.22.114
6 38 ms 30 ms 30 ms 192.168.4.6
7 133 ms 111 ms 95 ms 192.168.4.10
8 47 ms 44 ms 42 ms 192.168.4.13
9 34 ms 38 ms 44 ms xe-4-3-2.bar1.Minneapolis2.Level3net [4.14.210.57]
10 * * * Request timed out.
11 77 ms 54 ms 68 ms BLIZZARD-EN.ear7.Chicago2.Level3net [4.7.196.134]
12 * * * Request timed out.
13 132 ms 297 ms 125 ms et-0-0-3-br02-eqla1.as57976net [137.221.65.4]
14 105 ms 113 ms 110 ms 137.221.68.91
15 * 96 ms 1912 ms lax-eqla1-ia-bons-03.as57976net [137.221.66.7]
16 99 ms 92 ms 89 ms 24.105.30.129
Trace complete.
Looks like my ISP isn’t perfect, but wow that 1912 ms on the second trace…
The as57976net nodes are configured to de-prioritize ICMP messages (used by ping, traceroute, WinMTR, etc. i.e. their data is irrelevant.
To get a better data, run a WinMTR report for at least 10 minutes while you are experiencing latency in the game, like what OP did. Read this for detailed procedure:
Paste the report between two “~~~” lines, like this:
~~~
WinMTR report here
~~~
I have also been experiencing significant lag spikes the last few days. I’ve tried several of the troubleshooting steps recommended by Blizzard Tech Support but so far nothing has worked.
MagnaQuam,
If the troubleshooting that Maskraider gave you fails, are you using any interesting adapters such as a powerline adapter, or are you wired in to a wifi router which then broadcasts to another router elsewhere in your house? You should be getting a much better connection via ethernet.
If none of the above is true of your setup, reach out to your ISP and see what you need to do to replace the router. Maskraider’s steps should have fixed anything in your control already regarding that packet loss and latency. Beyond that, it’s usually the router giving up the ghost.