Need help to pinpoint latency origin

Support Technical Support
1

Hello.

My ISP have, in their infinite wisdom, decided to discontinue their copper offering and have moved on to a 5G mobile internet solution. After this happened, latency in WOW has been insufferable and it’s impossible to play as it is highly unpredictable.

Running a traceroute gives these results:

Tracing route to 185.60.112.158 over a maximum of 30 hops

1     1 ms     1 ms     1 ms  unifi.localdomain [192.168.1.1]
2    12 ms    34 ms     4 ms  fwa5e66-65.bb.online.no [88.94.102.65]
3     *        *        *     Request timed out.
4    97 ms    52 ms    51 ms  ti0275c360-ae16-0.ti.telenor.net [146.172.99.157]
5    47 ms    56 ms    80 ms  ti3001c360-ae3-0.ti.telenor.net [146.172.14.150]
6     *       86 ms   100 ms  ti3001b400-ae4-0.ti.telenor.net [146.172.105.29]
7    59 ms   104 ms    37 ms  netnod-ix-ge-b-sth-1500.blizzard.com [194.68.128.6]
8    59 ms    58 ms    60 ms  ae1-br01-eqsk1.as57976.net [137.221.86.33]
9  3834 ms     *     3800 ms  et-0-0-3-br01-eqam1.as57976.net [137.221.65.110]
10  2002 ms  1538 ms   886 ms  137.221.65.75
11    66 ms    53 ms    56 ms  137.221.78.49
12    56 ms    50 ms    60 ms  185.60.112.158

Trace complete.

Tracing route to 185.60.112.157 over a maximum of 30 hops

1     2 ms     1 ms     2 ms  unifi.localdomain [192.168.1.1]
2     2 ms     2 ms     2 ms  fwa5e66-65.bb.online.no [88.94.102.65]
3     *        *        *     Request timed out.
4    56 ms    32 ms    47 ms  ti0300c360-ae15-0.ti.telenor.net [146.172.101.133]
5    27 ms    55 ms    49 ms  ti3163c360-ae8-0.ti.telenor.net [146.172.101.194]
6    43 ms    60 ms    87 ms  ti3001b400-ae3-0.ti.telenor.net [146.172.105.62]
7    56 ms    76 ms    68 ms  netnod-ix-ge-b-sth-1500.blizzard.com [194.68.128.6]
8    63 ms    58 ms    78 ms  ae1-br01-eqsk1.as57976.net [137.221.86.33]
9     *     2201 ms  2851 ms  et-0-0-3-br01-eqam1.as57976.net [137.221.65.110]
10  2178 ms  2189 ms  2219 ms  137.221.65.75
11    71 ms    52 ms    53 ms  137.221.78.47
12    52 ms    57 ms    58 ms  185.60.112.157

Trace complete.

Tracing route to 185.60.114.159 over a maximum of 30 hops

1     6 ms     2 ms     2 ms  unifi.localdomain [192.168.1.1]
2     6 ms     3 ms     5 ms  fwa5e66-65.bb.online.no [88.94.102.65]
3     *        *        *     Request timed out.
4    54 ms    34 ms    50 ms  ti0275c360-ae16-0.ti.telenor.net [146.172.99.157]
5    38 ms    38 ms    38 ms  ti3001c360-ae3-0.ti.telenor.net [146.172.14.150]
6    46 ms    48 ms    38 ms  ti3001b400-ae4-0.ti.telenor.net [146.172.105.29]
7    34 ms    31 ms    35 ms  netnod-ix-ge-b-sth-1500.blizzard.com [194.68.128.6]
8    75 ms    59 ms    87 ms  ae1-br01-eqsk1.as57976.net [137.221.86.33]
9     *        *     2975 ms  et-0-0-3-br01-eqam1.as57976.net [137.221.65.110]
10   242 ms   226 ms   227 ms  et-0-0-29-br02-eqam1.as57976.net [137.221.65.33]
11   135 ms    56 ms    60 ms  et-0-0-3-br02-eqpa4.as57976.net [137.221.65.92]
12    78 ms    75 ms    76 ms  et-0-0-1-pe04-eqpa4.as57976.net [137.221.77.53]
13    77 ms    88 ms    81 ms  137.221.66.39
14    67 ms    87 ms    69 ms  185.60.114.159

Trace complete.

From my understanding, having high results in the middle of the hops aren’t problematic as long as the end result is a low latency one. So the middle “problematic” hops shouldn’t impact performance.

What will also happen, sometimes, is that latency will be relatively low (i.e. 50-70ms) and then will slowly creep up during play and “normalize” between 150-250ms. Switching characters increases latency and will make this tick up faster.

My system is cabled as such:

5G Modem cabled to an UDM Pro Router, this is connected to a Cisco C2960X switch, after that WiFi is delivered through a Ubiquiti UniFi UAP-AC-HD Wireless Access Point. Connecting through cable or wireless makes no difference for latency. Switching operating systems from Fedora to Windows 10 makes no difference.

It’s sending me up the wall and if I can’t solve it I’ll have to unsubscribe, and I don’t really want to.

Any more information needed, feel free to ask.

2

you dont happen to have a logitech mouse and ghub installed ? i ask because i had my network being flooded with data and i discovered my mouse software (g502 hero) have this arx control

“The Logitech Arx Control™ app connects with Logitech Gaming Software to give you exclusive in-game display information, vital systems statistics, and PC remote control functions that extend the PC Gaming experience to your mobile device .”

after i disable this my network changed from constant spikes to 100% to normal…

could be that if you use that ghub app.

if not just change isp …

3

Wow, I actually do, I’ll try this out!

EDIT: Did not affect anything unfortunately.

Unfortunately they’re the only provider available at the moment.

4

I’ll have to mention the unpleasant elephant in the room first, and apologies in advance because sadly there really aren’t any good news possible here: on the very baseline, this connection type is not supported for WoW. This is because trouble with it is unfortunately all but guaranteed, based on the way the related technology works.

More specifically: while bandwidth on 5G networks tends to be pretty solid, often even rather great - quality of service is shaky at the best of times, and the described symptoms here are textbook examples of escalating delays/losses on the route. Paired with the fact that these issues started the moment the connection type changed there is very little doubt that the root cause of the problem is within the stability of the new setup. Most issues of that nature would not show up in traceroute-type testing (and they indeed do not really stand out in the data captured here), because they affect types of data packets that are quite different from those used for the testing method.

In terms of troubleshooting that sadly leaves very few options. Using a VPN may be worth a shot, if the routing issue occurs past the “last mile” area (basically beyond the effective wireless route to the residence), but odds are that benefits of this will be limited in magnitude.