Ever since patch WORLD LAt. super high

Support Technical Support
1

Well since new patch world lat. has been running super high . any reason why this is ?
home lat 61
world Lat. 189
why?

2

Post a WinMTR so we can see why, run it for 10 min while the issue is happening and post the results here.

3

As Kneanderthal, for latency issues like these we’re going to want to get a WinMTR test ran while you’re having issues in-game. When posting those results, please format it by encasing it in a set of ~~~ like so:

~~~
WinMTR Contents
~~~

4 
|------------------------------------------------------------------------------------------|

|                                      WinMTR statistics                                   |

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

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

|                                10.0.0.1 -    0 |  955 |  955 |    0 |    0 |    4 |    1 |

|                             96.120.28.9 -    0 |  955 |  955 |    7 |   10 |   24 |   12 |

|be146-rur02.wchicago.il.chicago.comcast.net -    0 |  955 |  955 |    7 |   10 |   17 |   11 |

|be-124-ar01.area4.il.chicago.comcast.net -    0 |  955 |  955 |   11 |   14 |   22 |   12 |

|be-33491-cr02.350ecermak.il.ibone.comcast.net -    0 |  955 |  955 |   11 |   15 |   22 |   18 |

|be-10506-cr01.chicago.il.ibone.comcast.net -    0 |  955 |  955 |   10 |   14 |   23 |   14 |

|be-10614-cr02.56marietta.ga.ibone.comcast.net -    0 |  955 |  955 |   28 |   32 |   38 |   31 |

|be-1402-cs04.56marietta.ga.ibone.comcast.net -    1 |  951 |  950 |   29 |   31 |   40 |   31 |

|be-2401-pe01.56marietta.ga.ibone.comcast.net -    0 |  955 |  955 |   28 |   31 |   37 |   33 |

|                          50.208.232.138 -    0 |  955 |  955 |   28 |   34 |  195 |   30 |

|              ae1-br01-eqat2.as57976.net -    0 |  955 |  955 |   50 |   55 |  163 |   56 |

|         et-0-0-4-br02-eqch2.as57976.net -    0 |  955 |  955 |   29 |   54 |  163 |   30 |

|              be2-pe01-eqch2.as57976.net -    0 |  955 |  955 |   51 |   54 |   61 |   52 |

|        chi-eqch2-ia-bons-02.as57976.net -    0 |  955 |  955 |   52 |   54 |   68 |   53 |

|                           24.105.62.129 -    0 |  955 |  955 |   52 |   55 |   61 |   52 |

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

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

It’s going to be a bad hop to the ae1-br01-eqat2.as57976 node. I’ve made 3 posts about it this week and its still not fixed. Many people are having this problem and nothing is being done.

6

That’s not it. There have been blue parts about those hoops. Check your other threads.

7

I did and the fact that we get 200+ ms due to going through some security measure in one of their nodes is a lame excuse. The blue posts state that it’s a security feature that will always show high latency in a traceroute test, but not actually show as increased latency in-game. So how does that explain the fact it feels like I’m playing with Aussie ping? And how does it explain that it’s only been a problem for 4-5 days in the past year? Played the game with 68-70 ms for 12 years. Give me my good ping back.

8

Rotmuch,

Your tests actually look fine, nothing that would cause consistently high latency. With that in mind, you’re likely looking at a UI problem. I’d uninstall any addon managers (twitch/wowmatrix/etc) and reset your UI. If that works, it should be safe to manually reinstall the latest versions of your addons from your favorite addon site, and after you confirm it’s still stable without addons, reinstall any addon managers you use.

Nastylite,

Zungar is correct, those hops have mitigation and are entirely unrelated to this player’s problem. If they were having an actual routing issue, Rotmuch would most often have identical home/world latency numbers. They do not.

If you’re having an issue of your own, feel free to post your own thread, or try what I mentioned in this post. 9 times out of 10 when I see a player spontaneously get high ping or low FPS right after a patch, it’s just an addon or corrupt game data, and the steps above fix.

9
WinMTR Statistics

WinMTR statistics

Host % Sent Recv Best Avrg Wrst Last
10.0.0.1 0 220 220 0 4 118 0
96.120.28.9 3 200 195 7 16 139 23
be146-rur02.wchicago.il.chicago.comcast.net 3 200 195 7 16 129 24
be-124-ar01.area4.il.chicago.comcast.net 3 200 195 11 20 142 32
be-33491-cr02.350ecermak.il.ibone.comcast.net 3 200 195 12 21 140 29
be-10563-pe01.350ecermak.il.ibone.comcast.net 4 196 190 11 20 144 27
173-167-56-238-static.hfc.comcastbusiness.net 3 200 195 11 24 153 28
ae1-br02-eqch2.as57976.net 3 200 195 11 27 747 28
be2-pe01-eqch2.as57976.net 3 200 195 11 20 151 27
chi-eqch2-ia-bons-02.as57976.net 3 200 195 10 21 148 29
24.105.62.129 3 200 195 12 21 142 29
10

Horrible lag tonight on Drenden-Arathor. I can’t run a Win MTR because I have Verizon and it just comes up all 0’s or timeouts

11

Well this is odd,

It looks like there’s now a measurable problem in your tests - packet loss starting right after your modem. I assume you caught a connection problem with this test this time? If power cycling your hardware doesn’t fix it, I’d contact your ISP. They may need to replace the modem or there may be a problem between your house and their router box down the street. You’ll want to show a tier 2 or 3 tech this test and point out the packet loss. Based on how you get spikes in your house too - it’s possible that the modem is dying.

12
WinMTR Statistics

WinMTR statistics

Host % Sent Recv Best Avrg Wrst Last
10.0.0.1 0 77 77 0 0 2 1
96.120.28.9 0 77 77 7 12 75 9
be146-rur02.wchicago.il.chicago.comcast.net 0 77 77 8 11 17 10
be-124-ar01.area4.il.chicago.comcast.net 0 77 77 11 16 20 18
be-33491-cr02.350ecermak.il.ibone.comcast.net 0 77 77 12 16 29 13
be-10563-pe01.350ecermak.il.ibone.comcast.net 0 77 77 11 14 20 12
173-167-56-238-static.hfc.comcastbusiness.net 0 77 77 12 18 67 18
ae1-br02-eqch2.as57976.net 0 77 77 12 19 98 17
be2-pe01-eqch2.as57976.net 0 77 77 12 15 19 14
chi-eqch2-ia-bons-02.as57976.net 0 77 77 14 17 20 18
24.105.62.129 0 77 77 13 16 20 17
13

Rotmuch,

This is another very short test and the information is basically not helpful as a result. We need to ensure that the tests are run for several minutes - roughly 10 minutes to get enough usable data. I also need you to ensure that during the test, you catch a problem so that we know it’s relevant data. Can you try again for me?

14

This doesn’t show what happened to me earlier before this BG I just did. In a previous BG, you had me routed to a IP in the Netherlands…no idea how or why but on this current BG I just did. I had little to no lag.

WinMTR Statistics

WinMTR statistics

Host % Sent Recv Best Avrg Wrst Last
192.168.1.254 1 1166 1165 0 0 1 0
My IP 0 1169 1169 0 3 22 4
99.173.76.206 0 1169 1169 1 25 792 1
cr1.rlgnc.ip.att.net 0 1169 1169 10 14 19 13
cr1.attga.ip.att.net 0 1169 1169 10 13 19 14
gar18.attga.ip.att.net 0 1169 1169 10 10 12 10
12.247.68.74 0 1169 1169 10 14 84 11
ae1-br01-eqat2.as57976.net 0 1169 1169 29 31 127 125
et-0-0-4-br02-eqch2.as57976.net 0 1169 1169 29 32 325 29
be2-pe01-eqch2.as57976.net 0 1169 1169 29 29 32 29
chi-eqch2-ia-bons-02.as57976.net 0 1169 1169 30 31 43 31
24.105.62.129 0 1169 1169 30 30 34 30

The BIG Blip you see was me logging into WoW and my character loading. Game always freezes, after that I ran it for a good long time and for a major portion of the BG before I got DC’d from random lag during the BG.

Adding Blizzard’s Through the Looking Glass so they can see the problem is indeed on their end. Seeing bad lag at a blizzard owned server: 137.221.65.68.

TRACEROUTE:
traceroute to 107.140.242.220 (107.140.242.220), 15 hops max, 60 byte packets
1 Blizzard Blizzard 0.850 ms 0.837 ms 0.824 ms
2 24.105.18.3 (24.105.18.3) 0.977 ms 1.509 ms 1.537 ms
3 137.221.105.16 (137.221.105.16) 0.932 ms 0.965 ms 1.508 ms
4 137.221.66.22 (137.221.66.22) 1.521 ms 1.697 ms 1.710 ms
5 137.221.83.68 (137.221.83.68) 30.731 ms 30.944 ms 30.982 ms
6 137.221.65.68 (137.221.65.68) 57.088 ms 275.095 ms 275.093 ms
7 137.221.68.32 (137.221.68.32) 7.695 ms 7.683 ms 7.265 ms
8 12.245.64.9 (12.245.64.9) 7.211 ms 7.204 ms 7.205 ms
9 * * *
10 * * *
11 * * *
12 * * *
13 * * *
14 99.173.76.207 (99.173.76.207) 55.702 ms 55.578 ms 55.676 ms
15 * * *

21/07/2019 12:41:02 UTC

TRACEROUTE:
traceroute to 107.140.242.220 (107.140.242.220), 15 hops max, 60 byte packets
1 Blizzard Blizzard 0.361 ms 0.377 ms 0.381 ms
2 24.105.18.3 (24.105.18.3) 1.762 ms 1.792 ms 1.810 ms
3 137.221.105.16 (137.221.105.16) 1.770 ms 1.788 ms 1.805 ms
4 137.221.66.22 (137.221.66.22) 1.820 ms 1.826 ms 1.831 ms
5 137.221.83.68 (137.221.83.68) 58.799 ms 58.807 ms 58.815 ms
6 137.221.65.68 (137.221.65.68) 472.214 ms 469.851 ms 469.824 ms
7 137.221.68.32 (137.221.68.32) 6.048 ms 6.068 ms 6.075 ms
8 12.245.64.9 (12.245.64.9) 5.907 ms 6.064 ms 5.868 ms
9 * * *
10 * * *
11 * * *
12 * * *
13 * * *
14 99.173.76.207 (99.173.76.207) 55.576 ms 55.574 ms 55.452 ms
15 * * *

21/07/2019 12:41:02 UTC

TRACEROUTE:
traceroute to 107.140.242.220 (107.140.242.220), 15 hops max, 60 byte packets
1 Blizzard Blizzard 0.372 ms 0.378 ms 0.387 ms
2 24.105.18.3 (24.105.18.3) 4.771 ms 4.794 ms 4.827 ms
3 137.221.105.16 (137.221.105.16) 4.757 ms 4.773 ms 4.806 ms
4 137.221.66.22 (137.221.66.22) 4.811 ms 4.801 ms 4.805 ms
5 137.221.83.68 (137.221.83.68) 18.920 ms 18.926 ms 18.933 ms
6 137.221.65.68 (137.221.65.68) 265.059 ms 260.117 ms 260.095 ms
7 137.221.68.32 (137.221.68.32) 9.408 ms 7.808 ms 8.180 ms
8 12.245.64.9 (12.245.64.9) 7.731 ms 8.173 ms 7.971 ms
9 * * *
10 * * *
11 * * *
12 * * *
13 * * *
14 99.173.76.207 (99.173.76.207) 55.589 ms 55.609 ms 55.664 ms
15 * * *

21/07/2019 12:41:02 UTC

TRACEROUTE:
traceroute to 107.140.242.220 (107.140.242.220), 15 hops max, 60 byte packets
1 Blizzard Blizzard 0.279 ms 0.276 ms 0.280 ms
2 24.105.18.3 (24.105.18.3) 1.029 ms 1.040 ms 1.055 ms
3 137.221.105.16 (137.221.105.16) 0.990 ms 1.017 ms 1.029 ms
4 137.221.66.22 (137.221.66.22) 1.043 ms 1.046 ms 1.049 ms
5 137.221.83.68 (137.221.83.68) 5.937 ms 5.957 ms 5.961 ms
6 137.221.65.68 (137.221.65.68) 6.594 ms 6.070 ms 6.060 ms
7 137.221.68.32 (137.221.68.32) 6.212 ms 6.213 ms 6.152 ms
8 12.245.64.9 (12.245.64.9) 5.845 ms 5.855 ms 5.855 ms
9 * * *
10 * * *
11 * * *
12 * * *
13 * * *
14 99.173.76.207 (99.173.76.207) 57.490 ms 56.991 ms 63.683 ms
15 * * *

21/07/2019 12:41:07 UTC

MTR:
Start: Sun Jul 21 12:41:02 2019 Blizzard 1.|-- Blizzard 0.0% 10 0.4 1.7 0.3 13.8 4.2
2.|-- 24.105.18.3 0.0% 10 0.7 1.8 0.5 11.2 3.2
3.|-- 137.221.105.16 0.0% 10 0.6 0.7 0.5 1.0 0.0
4.|-- 137.221.66.22 0.0% 10 1.1 2.7 0.8 17.3 5.1
5.|-- 137.221.83.68 0.0% 10 5.9 6.6 5.8 13.1 2.2
6.|-- 137.221.65.68 0.0% 10 5.8 40.0 5.7 203.4 64.4
7.|-- 137.221.68.32 0.0% 10 54.2 11.0 5.8 54.2 15.2
8.|-- 12.245.64.9 0.0% 10 5.8 6.5 5.7 12.5 2.1
9.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
10.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
11.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
12.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
13.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
14.|-- 99.173.76.207 0.0% 10 55.7 55.7 55.6 55.9 0.0
15.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0

21/07/2019 12:41:02 UTC

MTR:
Start: Sun Jul 21 12:41:03 2019 Blizzard 1.|-- Blizzard 0.0% 10 0.3 0.4 0.3 0.6 0.0
2.|-- 24.105.18.3 0.0% 10 2.0 1.9 0.6 5.2 1.2
3.|-- 137.221.105.16 0.0% 10 0.9 0.7 0.5 1.2 0.0
4.|-- 137.221.66.22 0.0% 10 1.3 6.3 1.0 33.8 11.2
5.|-- 137.221.83.68 0.0% 10 6.0 5.9 5.7 6.1 0.0
6.|-- 137.221.65.68 0.0% 10 6.8 96.2 5.8 473.1 154.2
7.|-- 137.221.68.32 0.0% 10 6.2 6.6 5.9 9.0 0.7
8.|-- 12.245.64.9 0.0% 10 6.0 6.0 5.6 6.3 0.0
9.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
10.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
11.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
12.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
13.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
14.|-- 99.173.76.207 0.0% 10 55.9 55.7 55.4 56.0 0.0
15.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0

21/07/2019 12:41:02 UTC

MTR:
Start: Sun Jul 21 12:41:03 2019 Blizzard 1.|-- Blizzard 0.0% 10 0.5 0.4 0.3 0.5 0.0
2.|-- 24.105.18.3 0.0% 10 2.0 1.3 0.5 3.0 0.7
3.|-- 137.221.105.16 0.0% 10 0.9 0.7 0.5 1.0 0.0
4.|-- 137.221.66.22 0.0% 10 1.3 6.8 1.0 38.6 12.6
5.|-- 137.221.83.68 0.0% 10 6.1 5.9 5.8 6.3 0.0
6.|-- 137.221.65.68 0.0% 10 6.8 94.9 5.6 473.1 155.4
7.|-- 137.221.68.32 0.0% 10 6.2 6.1 5.9 6.8 0.0
8.|-- 12.245.64.9 0.0% 10 5.9 5.9 5.7 6.3 0.0
9.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
10.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
11.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
12.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
13.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
14.|-- 99.173.76.207 0.0% 10 56.0 55.7 55.4 56.1 0.0
15.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0

21/07/2019 12:41:02 UTC

MTR:
Start: Sun Jul 21 12:41:07 2019 Blizzard 1.|-- Blizzard 0.0% 10 0.4 0.3 0.3 0.4 0.0
2.|-- 24.105.18.3 0.0% 10 2.0 0.8 0.5 2.0 0.3
3.|-- 137.221.105.16 0.0% 10 0.6 0.7 0.5 1.0 0.0
4.|-- 137.221.66.22 0.0% 10 1.2 8.0 0.9 61.3 18.9
5.|-- 137.221.83.68 0.0% 10 6.0 8.9 5.7 35.0 9.2
6.|-- 137.221.65.68 0.0% 10 143.0 80.3 5.7 406.2 125.0
7.|-- 137.221.68.32 0.0% 10 7.3 6.2 5.9 7.3 0.3
8.|-- 12.245.64.9 0.0% 10 6.0 6.0 5.8 6.2 0.0
9.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
10.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
11.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
12.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
13.|-- gar8.rlgnc.ip.att. net 80.0% 10 55.0 54.9 54.7 55.0 0.0
14.|-- 99.173.76.207 0.0% 10 55.7 55.8 55.6 56.5 0.0
15.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0

21/07/2019 12:41:07 UTC