Strange Latency Issues since patch 8.1

I’ve been down the rabbit hole trying to fix this using every combination of fixes Blizzard has posted. Yet no fix is in sight. Only thing I haven’t done is blown out WoW and totally reloaded (file size is an issue, don’t want to get account flagged by my provider).

  • Inconsistent Latency issues: 1. Mounting shows no mount, and auto dismount on combat ability does not cancel it. 2. Moving items from bag to character doesn’t change right away. 3. Looting and quest turn ins lag. 4. When you lag out it doesn’t show under the interface as having an issue. 5. Does seem to happen more often when leveling around Kul Tiras (I have 6 of 10 leveled to 120, noticed it).

I’ve checked the connection to WoW servers and see no spikes to indicate problems getting to the server. No unusual spikes along the route to say there are switch gear issues. Any new ideas?

running a Dell XPS 8930, 8th gen i7, 16gb ram, Nvidia GTX 1080 and NVMe SSD.

1 Like

Can we take a peek at that network test? :slight_smile:

This issue is directly connected to zone population. Whenever there’s a horde raid in the zone i’m in, and population in the area spikes I have terrible syncing issues. I’m getting tired of people asking for dxdiags and network summaries.

I’m running
i7700k
16gb ddr4 3200mhz ram
gtx 980 4gb gpu
the game is being played off a 256gb m.2…
and my internet connection is 200mb DL / 20mb UL

It is a blizzard issue. not a user issue, their servers are running out of whack. I just came back to the game after a few month Hiatus to level some characters an enjoy the expansion and I simply cannot enjoy a single thing. I am near the point of unsubbing again why am I going to throw money at a broken game.

1 Like

Not every connection issue is the same. It’s important for the network test data to be collected so Blizzard can use it to help diagnose any larger issues.

Sad thing is I ran MTR to the realm, I ran pingtest to the us central IP for world of warcraft, and I ran a trace route, all of which don’t show many issues.

MTR:

MTR:
Start: Wed Jan 16 20:11:33 2019 Blizzard  1.|-- Blizzard    0.0%    10    0.3   0.7   0.2   4.2   1.1
  2.|-- ???             100.0    10    0.0   0.0   0.0   0.0   0.0


16/01/2019 20:11:33 UTC
--------------------

MTR:
Start: Wed Jan 16 20:11:33 2019 Blizzard  1.|-- Blizzard    0.0%    10    0.2   0.2   0.2   0.3   0.0
  2.|-- ???             100.0    10    0.0   0.0   0.0   0.0   0.0


16/01/2019 20:11:33 UTC
--------------------

MTR:
Start: Wed Jan 16 20:11:33 2019 Blizzard  1.|-- Blizzard    0.0%    10    0.2   0.2   0.2   0.3   0.0
  2.|-- ???             100.0    10    0.0   0.0   0.0   0.0   0.0


16/01/2019 20:11:33 UTC
--------------------

MTR:
Start: Wed Jan 16 20:11:33 2019 Blizzard  1.|-- Blizzard    0.0%    10    0.2   0.3   0.2   0.4   0.0
  2.|-- ???             100.0    10    0.0   0.0   0.0   0.0   0.0


16/01/2019 20:11:33 UTC
--------------------

pathping to central -

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

--- 71.10.85.67 ping statistics ---
4 packets transmitted, 0 received, 100% packet loss, time 2999ms



16/01/2019 20:22:47 UTC
--------------------

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

--- 71.10.85.67 ping statistics ---
4 packets transmitted, 0 received, 100% packet loss, time 3000ms



16/01/2019 20:22:47 UTC
--------------------

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

--- 71.10.85.67 ping statistics ---
4 packets transmitted, 0 received, 100% packet loss, time 2999ms



16/01/2019 20:22:47 UTC
--------------------

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

--- 71.10.85.67 ping statistics ---
4 packets transmitted, 0 received, 100% packet loss, time 2999ms



16/01/2019 20:22:47 UTC
--------------------


Tracert - to central ip


TRACEROUTE:
traceroute to 71.10.85.67 (71.10.85.67), 15 hops max, 60 byte packets
 1  Blizzard Blizzard  0.312 ms  0.298 ms  0.295 ms Blizzard(24.105.18.2)  0.539 ms  0.898 ms  0.903 ms
 3  137.221.105.14 (137.221.105.14)  0.916 ms  0.925 ms  0.923 ms
 4  137.221.66.22 (137.221.66.22)  0.905 ms  0.905 ms  0.903 ms
 5  137.221.83.68 (137.221.83.68)  5.842 ms  5.851 ms  5.851 ms
 6  137.221.65.68 (137.221.65.68)  5.633 ms  5.798 ms  5.787 ms
 7  137.221.68.32 (137.221.68.32)  5.538 ms  5.601 ms  5.570 ms
 8  eqix-la1.chartercom.com (206.223.123.141)  5.861 ms  5.805 ms  5.788 ms
 9  * * *
10  * * *
11  * * *
12  * * *
13  * * *
14  * * *
15  * * *


16/01/2019 20:21:18 UTC
--------------------

TRACEROUTE:
traceroute to 71.10.85.67 (71.10.85.67), 15 hops max, 60 byte packets
 1  Blizzard Blizzard  2.271 ms  2.267 ms  2.268 ms Blizzard(24.105.18.2)  3.654 ms  3.676 ms  3.682 ms
 3  137.221.105.14 (137.221.105.14)  3.745 ms  3.747 ms  3.763 ms
 4  137.221.66.22 (137.221.66.22)  3.741 ms  3.742 ms  3.744 ms
 5  137.221.83.68 (137.221.83.68)  9.321 ms  9.324 ms  9.326 ms
 6  137.221.65.68 (137.221.65.68)  7.780 ms  25.618 ms  25.584 ms
 7  137.221.68.32 (137.221.68.32)  6.200 ms  6.079 ms  6.062 ms
 8  eqix-la1.chartercom.com (206.223.123.141)  6.070 ms  6.175 ms  6.162 ms
 9  * * *
10  * * *
11  * * *
12  * * *
13  * * *
14  * * *
15  * * *


16/01/2019 20:21:18 UTC
--------------------

TRACEROUTE:
traceroute to 71.10.85.67 (71.10.85.67), 15 hops max, 60 byte packets
 1  Blizzard Blizzard  0.490 ms  0.481 ms  0.481 ms Blizzard(24.105.18.2)  1.871 ms  1.874 ms  1.861 ms
 3  137.221.105.14 (137.221.105.14)  1.975 ms  1.976 ms  1.987 ms
 4  137.221.66.22 (137.221.66.22)  1.917 ms  1.922 ms  1.924 ms
 5  137.221.83.68 (137.221.83.68)  7.495 ms  7.500 ms  7.501 ms
 6  137.221.65.68 (137.221.65.68)  5.950 ms  6.058 ms  6.030 ms
 7  137.221.68.32 (137.221.68.32)  5.995 ms  5.722 ms  6.149 ms
 8  eqix-la1.chartercom.com (206.223.123.141)  6.161 ms  6.761 ms  6.791 ms
 9  * * *
10  * * *
11  * * *
12  * * *
13  * * *
14  * * *
15  * * *


16/01/2019 20:21:18 UTC
--------------------

TRACEROUTE:
traceroute to 71.10.85.67 (71.10.85.67), 15 hops max, 60 byte packets
 1  Blizzard Blizzard  0.317 ms  0.318 ms  0.319 ms Blizzard(24.105.18.2)  0.590 ms  0.684 ms  0.758 ms
 3  137.221.105.14 (137.221.105.14)  1.017 ms  1.043 ms  1.062 ms
 4  137.221.66.22 (137.221.66.22)  1.025 ms  1.036 ms  1.037 ms
 5  137.221.83.68 (137.221.83.68)  6.359 ms  6.365 ms  6.368 ms
 6  137.221.65.68 (137.221.65.68)  8.875 ms  6.490 ms  6.447 ms
 7  137.221.68.32 (137.221.68.32)  5.563 ms  5.552 ms  5.878 ms
 8  eqix-la1.chartercom.com (206.223.123.141)  5.972 ms  6.332 ms  6.329 ms
 9  * * *
10  * * *
11  * * *
12  * * *
13  * * *
14  * * *
15  * * *


16/01/2019 20:21:18 UTC
--------------------



Character - Oliverian - Alliance Paladin
Realm - Illidan
Zone(s) - Stormsong Valley (currently), happened the past few days in stormsong and drustvar
TIME: Today on 1/16/19 at around 130-2 pm
yesterday this same desyncing issue happened at 1130pm etc.

This is likely going to be related to the thread here. Its something we’ve escalated and is being looked into though we don’t have a timeframe on when it may be resolved. We’ll be posting updates as we get them on that thread though.

1 Like