High home MS issues, occasionally world

Support Technical Support
1

Hello, a quick description of my issues:

(note: I had to space out some of the links in the test so I could make this post)

It seems like lately I’ve been getting extremely high home MS, which causes my spells to delay–able to cast one spell every 3-5 seconds or so, and then it releases and starts lagging again, what I can only describe as rubberbanding. Players around me will run in place for the duration of the lag spike and rubberband as well. This mainly seems to happen when I am in a dungeon, LFR, or PvP. It always starts green, and then within 10 or so minutes, my latency spikes up dramatically and stays this way for (I think ) 20-30 minutes, sometimes longer. I usually log out out of frustration when it gets that long.

As I write this, both my world and home MS are over 1k, and the test I did using the looking glass program was taken during that time. I’m just standing still in Dazar’alor. The world MS is always that high, though–the home MS is usually higher, and I saw it get as high as 2k this morning during my LFR raid.

(update: the home ms has gone back down to 112 ms and world is at 132 ms. The spikes I mentioned earlier, all of this has happened within the last half hour or so).

Things I’ve tried:

  1. Closing any extraneous programs on my computer.
  2. Using the CMD prompt to do a reset (although I don’t think this worked properly).
  3. Restarting my computer.
  4. Disconnecting and reconnecting to my wifi

As stated, I ran a test using the battle .net looking glass. I checked the MTR, traceroute, and ping during the lag spike. The results follow this; please let me know if there is any other info I can provide:

TRACEROUTE:
traceroute to 68.13.79.112 (68.13.79.112), 15 hops max, 60 byte packets
1 Blizzard Blizzard 1.109 ms 1.110 ms 1.114 ms Blizzard(24.105.18.3) 2.162 ms 2.184 ms 2.192 ms
3 137.221.105.12 (137.221.105.12) 3.041 ms 3.063 ms 3.129 ms
4 137.221.66.16 (137.221.66.16) 3.063 ms 3.066 ms 3.073 ms
5 137.221.83.66 (137.221.83.66) 31.411 ms 31.462 ms 31.475 ms
6 137.221.65.68 (137.221.65.68) 6.447 ms 8.486 ms 8.432 ms
7 137.221.68.32 (137.221.68.32) 8.377 ms 7.285 ms 7.240 ms
8 70.191.61.9 (70.191.61.9) 7.201 ms 13.486 ms 13.474 ms
9 mtc1dsrj02-ae2.0.rd.om. cox. net (68.1.0.127) 49.387 ms 49.394 ms 49.402 ms
10 ip68-13-79-112.om.om. cox. net (68.13.79.112) 47.859 ms 52.798 ms 52.790 ms

20/02/2019 16:24:31 UTC

PING:
PING 68.13.79.112 (68.13.79.112) 56(84) bytes of data.
64 bytes from 68.13.79.112: icmp_seq=1 ttl=53 time=56.5 ms
64 bytes from 68.13.79.112: icmp_seq=2 ttl=53 time=48.2 ms
64 bytes from 68.13.79.112: icmp_seq=3 ttl=53 time=46.8 ms
64 bytes from 68.13.79.112: icmp_seq=4 ttl=53 time=48.8 ms

— 68.13.79.112 ping statistics —
4 packets transmitted, 4 received, 0% packet loss, time 2998ms
rtt min/avg/max/mdev = 46.801/50.121/56.575/3.802 ms

20/02/2019 16:24:31 UTC

TRACEROUTE:
traceroute to 68.13.79.112 (68.13.79.112), 15 hops max, 60 byte packets
1 Blizzard Blizzard 0.408 ms 0.424 ms 0.436 ms Blizzard(24.105.18.3) 0.557 ms 0.619 ms 0.960 ms
3 137.221.105.12 (137.221.105.12) 1.780 ms 1.842 ms 1.851 ms
4 137.221.66.16 (137.221.66.16) 1.788 ms 1.799 ms 1.836 ms
5 137.221.83.66 (137.221.83.66) 6.125 ms 6.215 ms 6.225 ms
6 137.221.65.68 (137.221.65.68) 5.825 ms 5.847 ms 5.813 ms
7 137.221.68.32 (137.221.68.32) 5.581 ms 5.603 ms 5.574 ms
8 70.191.61.9 (70.191.61.9) 5.511 ms 5.367 ms 5.503 ms
9 mtc1dsrj02-ae2.0.rd.om. cox. net (68.1.0.127) 48.108 ms 48.131 ms 48.047 ms
10 * * *
11 * * *
12 * * *
13 * * *
14 * * *
15 * * *

20/02/2019 16:24:31 UTC

PING:
PING 68.13.79.112 (68.13.79.112) 56(84) bytes of data.
64 bytes from 68.13.79.112: icmp_seq=1 ttl=53 time=53.3 ms

— 68.13.79.112 ping statistics —
4 packets transmitted, 1 received, 75% packet loss, time 2998ms
rtt min/avg/max/mdev = 53.300/53.300/53.300/0.000 ms

20/02/2019 16:24:31 UTC

TRACEROUTE:
traceroute to 68.13.79.112 (68.13.79.112), 15 hops max, 60 byte packets
1 Blizzard Blizzard 0.756 ms 0.759 ms 0.765 ms Blizzard(24.105.18.3) 1.817 ms 1.821 ms 1.825 ms
3 137.221.105.12 (137.221.105.12) 1.835 ms 1.838 ms 2.060 ms
4 137.221.66.16 (137.221.66.16) 1.783 ms 1.789 ms 1.795 ms
5 137.221.83.66 (137.221.83.66) 6.503 ms 6.507 ms 6.528 ms
6 137.221.65.68 (137.221.65.68) 6.494 ms 6.244 ms 6.236 ms
7 137.221.68.32 (137.221.68.32) 5.920 ms 5.902 ms 6.234 ms
8 70.191.61.9 (70.191.61.9) 6.177 ms 6.174 ms 6.172 ms
9 mtc1dsrj02-ae2.0.rd.om. cox. net (68.1.0.127) 48.395 ms 48.647 ms 48.631 ms
10 ip68-13-79-112.om.om. cox. net (68.13.79.112) 48.906 ms * *

20/02/2019 16:24:35 UTC

PING:
PING 68.13.79.112 (68.13.79.112) 56(84) bytes of data.
64 bytes from 68.13.79.112: icmp_seq=1 ttl=53 time=48.2 ms
64 bytes from 68.13.79.112: icmp_seq=2 ttl=53 time=47.5 ms
64 bytes from 68.13.79.112: icmp_seq=3 ttl=53 time=47.0 ms
64 bytes from 68.13.79.112: icmp_seq=4 ttl=53 time=47.3 ms

— 68.13.79.112 ping statistics —
4 packets transmitted, 4 received, 0% packet loss, time 2998ms
rtt min/avg/max/mdev = 47.001/47.537/48.204/0.433 ms

20/02/2019 16:24:35 UTC

TRACEROUTE:
traceroute to 68.13.79.112 (68.13.79.112), 15 hops max, 60 byte packets
1 Blizzard Blizzard 0.270 ms 0.267 ms 0.277 ms Blizzard(24.105.18.3) 1.571 ms 1.616 ms 1.625 ms
3 137.221.105.12 (137.221.105.12) 0.633 ms 0.779 ms 0.823 ms
4 137.221.66.16 (137.221.66.16) 0.560 ms 0.602 ms 0.825 ms
5 137.221.83.66 (137.221.83.66) 5.919 ms 5.950 ms 5.960 ms
6 137.221.65.68 (137.221.65.68) 5.720 ms 5.779 ms 5.759 ms
7 137.221.68.32 (137.221.68.32) 5.651 ms 5.679 ms 5.700 ms
8 70.191.61.9 (70.191.61.9) 5.431 ms 5.453 ms 5.459 ms
9 mtc1dsrj02-ae2.0.rd.om. cox. net (68.1.0.127) 47.934 ms 47.840 ms 47.841 ms
10 * * *
11 * * *
12 * * *
13 * * *
14 * * *
15 * * *

20/02/2019 16:24:37 UTC

PING:
PING 68.13.79.112 (68.13.79.112) 56(84) bytes of data.

— 68.13.79.112 ping statistics —
4 packets transmitted, 0 received, 100% packet loss, time 2999ms

20/02/2019 16:24:39 UTC

MTR:
Start: Wed Feb 20 16:24:31 2019 Blizzard 1.|-- Blizzard 0.0% 10 0.4 0.4 0.3 0.4 0.0 Blizzard 0.0% 10 0.8 0.6 0.5 0.8 0.0
3.|-- 137.221.105.12 0.0% 10 1.0 0.7 0.6 1.0 0.0
4.|-- 137.221.66.16 0.0% 10 0.8 0.7 0.6 0.9 0.0
5.|-- 137.221.83.66 0.0% 10 5.7 8.2 5.7 28.6 7.2
6.|-- 137.221.65.68 0.0% 10 5.9 7.9 5.8 26.6 6.5
7.|-- 137.221.68.32 0.0% 10 5.6 5.7 5.5 5.8 0.0
8.|-- 70.191.61.9 0.0% 10 5.7 5.7 5.4 6.6 0.3
9.|-- mtc1dsrj02-ae2.0.rd.om .cox. net 0.0% 10 48.0 50.5 48.0 66.9 5.9
10.|-- ip68-13-79-112.om.om. cox. net 0.0% 10 53.0 50.5 47.2 53.1 2.2

20/02/2019 16:24:30 UTC

MTR:
Start: Wed Feb 20 16:24:31 2019 Blizzard 1.|-- Blizzard 0.0% 10 0.3 0.3 0.2 0.4 0.0 Blizzard 0.0% 10 0.7 1.2 0.5 6.4 1.7
3.|-- 137.221.105.12 0.0% 10 0.6 0.6 0.6 0.7 0.0
4.|-- 137.221.66.16 0.0% 10 0.8 0.7 0.5 0.8 0.0
5.|-- 137.221.83.66 0.0% 10 6.0 9.5 5.7 42.3 11.5
6.|-- 137.221.65.68 0.0% 10 5.8 7.2 5.7 17.3 3.6
7.|-- 137.221.68.32 0.0% 10 5.6 6.5 5.6 11.8 1.7
8.|-- 70.191.61.9 0.0% 10 5.5 5.5 5.4 5.9 0.0
9.|-- mtc1dsrj02-ae2.0.rd.om. cox. net 0.0% 10 48.2 52.0 47.9 72.4 8.3
10.|-- ip68-13-79-112.om.om. cox. net 80.0% 10 48.9 48.0 47.2 48.9 1.0

20/02/2019 16:24:31 UTC

MTR:
Start: Wed Feb 20 16:24:31 2019 Blizzard 1.|-- Blizzard 0.0% 10 0.2 0.3 0.2 0.5 0.0 Blizzard 0.0% 10 0.5 1.0 0.5 4.6 1.2
3.|-- 137.221.105.12 0.0% 10 0.5 0.6 0.5 0.8 0.0
4.|-- 137.221.66.16 0.0% 10 0.6 0.7 0.6 1.1 0.0
5.|-- 137.221.83.66 0.0% 10 5.8 5.9 5.7 6.1 0.0
6.|-- 137.221.65.68 0.0% 10 5.8 7.5 5.7 17.3 3.6
7.|-- 137.221.68.32 0.0% 10 5.6 5.7 5.6 6.0 0.0
8.|-- 70.191.61.9 0.0% 10 5.6 5.6 5.4 5.7 0.0
9.|-- mtc1dsrj02-ae2.0.rd.om. cox .net 0.0% 10 47.9 48.0 47.9 48.4 0.0
10.|-- ip68-13-79-112.om.om. cox .net 80.0% 10 48.3 48.1 48.0 48.3 0.0

20/02/2019 16:24:31 UTC

MTR:
Start: Wed Feb 20 16:24:35 2019 Blizzard 1.|-- Blizzard 0.0% 10 0.4 0.3 0.2 0.4 0.0 Blizzard 0.0% 10 0.5 0.5 0.5 0.6 0.0
3.|-- 137.221.105.12 0.0% 10 0.6 0.6 0.5 0.8 0.0
4.|-- 137.221.66.16 0.0% 10 0.9 0.7 0.5 1.2 0.0
5.|-- 137.221.83.66 0.0% 10 5.7 6.0 5.7 7.6 0.3
6.|-- 137.221.65.68 0.0% 10 5.8 8.7 5.7 29.3 7.4
7.|-- 137.221.68.32 0.0% 10 5.6 5.7 5.6 6.2 0.0
8.|-- 70.191.61.9 0.0% 10 6.4 5.8 5.5 7.1 0.5
9.|-- mtc1dsrj02-ae2.0.rd.om. cox .net 0.0% 10 48.2 48.9 47.9 53.0 1.7
10.|-- ip68-13-79-112.om.om .cox .net 60.0% 10 47.0 47.5 46.5 48.8 0.8

20/02/2019 16:24:35 UTC

2

Hi could you test this with wired and see if the problem goes away to rule out if your wifi is misbehaving? Also could you run a WinMTR and post the results here.

3

Hi Tristian

There is an indication of packet loss on or near the home network here:

10 ip68-13-79-112.om.om. cox. net (68.13.79.112) 48.906 ms * * (The * indicate packet loss)

Those tests are from Blizzard’s servers to your home network firewall. The WinMTR that Kneanderthal linked may show us more. It will pick up the home network and connection path to Blizzard.

4

Hello, I did a run of the MTR program. A few days ago I tried to do it when my latency was red but I wasn’t able to replicate the issue. I ran this today in a timewalking dungeon during which I had yellow latency and the usual rubberbanding (even when the latency showed green).

|------------------------------------------------------------------------------------------|
| WinMTR statistics |

Host - % Sent Recv Best Avrg Wrst Last
ip68-13-79-112.om.om. cox. net - 2 469 463 3 51 3456 15
________________________________________________ ______ ______ ______ ______ ______ ______

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

5

Sorry but that is not the whole WinMTR we need to see all the hops please.

That one you linked shows a 2% loss.

6

Sorry, I’m not familiar with this sort of thing…

After running it, I stopped the program and chose the copy to clipboard option and then ctrl +v’d that here, is there a specific way I should do it next time? And for how long should it run?

7

It should be run for at least 10 min. Ideally you should have it running in the background, won’t cause any issues, until you get the problem then run it for about 10 minutes while the issue is happening or until you get a disconnect.

It should look like this:

|------------------------------------------------------------------------------------------|
|                                      WinMTR statistics                                   |
|                       Host              -   %  | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
|                             192.168.1.1 -    0 |    4 |    4 |    0 |    0 |    0 |    0 |
|                   x.x.x.x.wavecable.com -    0 |    4 |    4 |   13 |   15 |   18 |   18 |
|                          174.127.183.74 -    0 |    4 |    4 |   12 |   14 |   16 |   16 |
|     cr2-sea-b-hu-0-7-0-4.bb.as11404.net -    0 |    4 |    4 |   13 |   21 |   29 |   17 |
|                  six.blizzardonline.net -    0 |    4 |    4 |   13 |   16 |   19 |   19 |
|              ae1-br01-eqse2.as57976.net -    0 |    4 |    4 |   48 |   56 |   60 |   48 |
|       xe-0-0-0-1-br01-eqsv5.as57976.net -    0 |    4 |    4 |   57 |   63 |   77 |   60 |
|       xe-0-0-1-1-br02-eqla1.as57976.net -    0 |    4 |    4 |   56 |   59 |   62 |   62 |
|        et-0-0-29-br01-eqla1.as57976.net -    0 |    4 |    4 |   57 |   60 |   65 |   60 |
|        et-0-0-2-br01-swlv10.as57976.net -    0 |    4 |    4 |   53 |   56 |   59 |   59 |
|       et-0-0-31-pe02-swlv10.as57976.net -    0 |    4 |    4 |   56 |   57 |   59 |   59 |
|                           137.221.105.2 -    0 |    4 |    4 |   53 |   55 |   58 |   58 |
|________________________________________________|______|______|______|______|______|______|
   WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider

Make sure you are using the Blizzard IP to West Coast or East Coast, whichever you use, given in the link when starting it.

8

We will want to try gettign another WinMTR as Kneanderthal mentioned. A traceroute test may also provide us with some additional info.

Based on what has been provided in the last post though, we are seeing packet loss and a spike of 3456 ms on the Cox network:

ip68-13-79-112.om.om.cox.net - 2 469 463 3 51 3456 15

Notice this is the same hop that we saw in the looking glass test:

10 ip68-13-79-112.om.om.cox.net (68.13.79.112) 48.906 ms * *

We’ll take a look over the new WinMTR\traceroute but based on what we have so far, this does look like something Cox will need to look into.

9

Sorry for taking so long to reply, but I finally had some time to let the MTR test run. Hopefully this is more helpful:

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

| WinMTR statistics |

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

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

| 192.168.0.1 - 8 | 2884 | 2661 | 0 | 35 | 3317 | 6 |

| 10.96.88.1 - 8 | 2914 | 2708 | 0 | 86 | 4850 | 17 |

| 172.27.13.50 - 8 | 2887 | 2674 | 9 | 86 | 3631 | 19 |

| 172.27.13.32 - 8 | 2914 | 2707 | 0 | 88 | 3469 | 15 |

| chgobprj01-ae0.0.rd.ch. cox. net - 8 | 2918 | 2713 | 0 | 101 | 3469 | 22 |

| 68.105.30.218 - 7 | 2922 | 2719 | 0 | 102 | 3470 | 27 |

| ae1-br02-eqch2.as57976 .net - 8 | 2915 | 2710 | 0 | 106 | 3642 | 23 |

| be2-pe01-eqch2.as57976 .net - 8 | 2918 | 2713 | 0 | 99 | 3470 | 72 |

| 24.105.62.129 - 7 | 2922 | 2719 | 0 | 102 | 3642 | 64 |

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

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

At one point, world latency spiked to almost 2.1k ms! And at one point when I tabbed out to look at what was going, the percentage was as high as 29.

10

The WinMTR tells the story Tistian. 8% packet loss starts at the router. It carries down each hop switch all the way to Blizzard. There was one latency spike near 5 seconds.

You mention you are on Wifi. Try an Ethernet cable if you can at all. Even as a test. If you can toggle the Wifi between 2.4 Ghz and 5 Ghz bands try that.

The router should have a reset button … small button somewhere that you may need a pen tip to press. Press then hold that button down for 30 seconds.

Unplug router power then leave for 10 or 15 minutes unplugged. (Drains capacitors inside device)