I’m about done with this game… the Lag is ridiculous !!!
I go into bolarus and open up a work order… delayed …
I go into a pvp 40 man battleground… LAG !
AND NOW !!!
i try to do 5 mask and i die because of lag on the last boss , the others are just about doable as i push through the other zones…
So i now have to farm 10.0000 essence something i don’t want to do, to go back into a vision, to wipe because my ping is 33 HOME 500 WORLD ! with random game pausing spikes !!!
this really is becoming a joke, the game is just not fun and more becoming stressful !!! with the server side issues ! its not what i paid for !!!
1 Like
Just lost my run also because of the same issue LAG and DC
[EU] With the help of EU ISPs, we made configuration changes yesterday that should fix a major spike in ping at peak hours for some players. European networks remain under high load, so we’ll continue to monitor and address what we can.
^
this will never be blizzard. go figure out which F2P game company it is blizzard is just indie company boyo. for blizzard it’s always your isps fault where you pay more to blizzard than your isp they still don’t and won’t care.
this ongoing lag issue for past 1-2 weeks cost too much time and mental health for me i just gave up on wow.
We have seen a fair few cases of lag reports recently and with the situation happening in the EU, there’s alot of congestion happening on networks. There can be many different things causing the problem here though please don’t take that to mean I am putting the blame on you.
Depending on location, the route your connection is taking may be running into problems and in order to help further troubleshoot things, it would be great to see how your game is connecting to our servers. To do this, please run a traceroute and copy the results into a website like Pastebin.
By doing that, you can then respond to this thread and use the </> symbol above the text box to include your Pastebin link so we can take a look.
Contrary to popular belief, we do care and we want to try and get things more manageable for you. I hope we can see a reply to this real soon
I can see improvement today but still there is lag, here is the WinMTR and traceroute
https://pastebin.com/raw/WWhMv1Vh
https://pastebin.com/raw/T9prNU2F
https://pastebin.com/raw/Rv0UDvx2
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
Host - % |
Sent |
Recv |
Best |
Avrg |
Wrst |
Last |
192.168.1.1 - 0 |
591 |
591 |
0 |
0 |
4 |
0 |
192.168.0.1 - 0 |
591 |
591 |
0 |
0 |
10 |
0 |
172.26.33.1 - 0 |
591 |
591 |
13 |
25 |
98 |
98 |
172.26.254.146 - 0 |
591 |
591 |
13 |
19 |
90 |
90 |
88.201.57.57 - 0 |
591 |
591 |
14 |
27 |
80 |
27 |
89.148.62.81 - 0 |
591 |
591 |
13 |
21 |
83 |
18 |
80.249.208.83 - 0 |
591 |
591 |
106 |
119 |
220 |
116 |
ae1-br02-eqam1.as57976.net - 0 |
591 |
591 |
106 |
122 |
953 |
111 |
137.221.78.85 - 0 |
591 |
591 |
106 |
117 |
217 |
140 |
185.60.112.158 - 1 |
587 |
586 |
105 |
115 |
294 |
122 |
________________________________________________ |
______ |
______ |
______ |
______ |
______ |
______ |
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
Host - % |
Sent |
Recv |
Best |
Avrg |
Wrst |
Last |
192.168.1.1 - 0 |
154 |
154 |
0 |
0 |
0 |
0 |
192.168.0.1 - 0 |
153 |
153 |
0 |
0 |
5 |
0 |
172.26.33.5 - 0 |
154 |
154 |
21 |
74 |
273 |
73 |
172.26.107.209 - 0 |
154 |
154 |
16 |
69 |
272 |
72 |
172.26.254.146 - 0 |
153 |
153 |
19 |
67 |
266 |
26 |
88.201.57.57 - 0 |
154 |
154 |
21 |
74 |
271 |
74 |
89.148.62.81 - 0 |
153 |
153 |
18 |
69 |
268 |
27 |
80.249.208.83 - 0 |
153 |
153 |
112 |
166 |
504 |
118 |
ae1-br02-eqam1.as57976.net - 0 |
154 |
154 |
119 |
177 |
596 |
166 |
et-0-0-3-br02-eqpa4.as57976.net - 0 |
153 |
153 |
127 |
183 |
423 |
133 |
be2-pe2-eqpa4.as57976.net - 0 |
154 |
154 |
116 |
167 |
365 |
167 |
No response from host - 100 |
30 |
0 |
0 |
0 |
0 |
0 |
No response from host - 100 |
30 |
0 |
0 |
0 |
0 |
0 |
No response from host - 100 |
30 |
0 |
0 |
0 |
0 |
0 |
No response from host - 100 |
30 |
0 |
0 |
0 |
0 |
0 |
No response from host - 100 |
30 |
0 |
0 |
0 |
0 |
0 |
No response from host - 100 |
30 |
0 |
0 |
0 |
0 |
0 |
No response from host - 100 |
30 |
0 |
0 |
0 |
0 |
0 |
No response from host - 100 |
30 |
0 |
0 |
0 |
0 |
0 |
No response from host - 100 |
30 |
0 |
0 |
0 |
0 |
0 |
No response from host - 100 |
30 |
0 |
0 |
0 |
0 |
0 |
No response from host - 100 |
30 |
0 |
0 |
0 |
0 |
0 |
No response from host - 100 |
30 |
0 |
0 |
0 |
0 |
0 |
No response from host - 100 |
30 |
0 |
0 |
0 |
0 |
0 |
No response from host - 100 |
30 |
0 |
0 |
0 |
0 |
0 |
No response from host - 100 |
30 |
0 |
0 |
0 |
0 |
0 |
No response from host - 100 |
30 |
0 |
0 |
0 |
0 |
0 |
No response from host - 100 |
30 |
0 |
0 |
0 |
0 |
0 |
No response from host - 100 |
30 |
0 |
0 |
0 |
0 |
0 |
No response from host - 100 |
30 |
0 |
0 |
0 |
0 |
0 |
________________________________________________ |
______ |
______ |
______ |
______ |
______ |
______ |
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
Host - % |
Sent |
Recv |
Best |
Avrg |
Wrst |
Last |
192.168.1.1 - 0 |
169 |
169 |
0 |
0 |
0 |
0 |
192.168.0.1 - 0 |
169 |
169 |
0 |
0 |
5 |
0 |
172.26.33.5 - 0 |
169 |
169 |
13 |
86 |
292 |
61 |
172.26.107.209 - 0 |
169 |
169 |
21 |
87 |
275 |
63 |
172.26.254.146 - 0 |
169 |
169 |
14 |
80 |
270 |
51 |
88.201.57.57 - 0 |
169 |
169 |
17 |
88 |
276 |
72 |
89.148.62.81 - 0 |
169 |
169 |
20 |
85 |
284 |
59 |
80.249.208.83 - 0 |
169 |
169 |
110 |
175 |
390 |
140 |
ae1-br02-eqam1.as57976.net - 0 |
169 |
169 |
113 |
175 |
397 |
138 |
137.221.78.89 - 0 |
169 |
169 |
115 |
180 |
371 |
200 |
137.221.66.47 - 0 |
169 |
169 |
112 |
176 |
371 |
144 |
185.60.112.157 - 0 |
169 |
169 |
110 |
174 |
371 |
144 |
________________________________________________ |
______ |
______ |
______ |
______ |
______ |
______ |
Ok so the MTR’s there are in good shape and showing no packet loss which is a good thing
The traceroutes though seem to show a different story. While the connection is getting through, there’s a delay spike which while not major is probably the reason why your getting lag. In essence, your packets are getting through to us but delayed which would mean you stay connected but occasionally will see a slow down.
On the https://pastebin.com/raw/WWhMv1Vh link, this happens on step 4, 5 and 7 on the first attempt. Then it normalises and goes back down. This is echoed in the other two links you gave to a degree but on https://pastebin.com/raw/T9prNU2F you have a missing test on step 2 (marked by a *)
That means that 2 out of 3 tests went through and 1 failed. Step 2 is usually your router going out into the world and sometimes a simple router restart can resolve that.
Granted this gives you a whole host of information but not alot of resolution on what to do next. With this information though, you can head to your Internet Provider and show them the results. We have no control over the nodes that are showing the slowdown in your traceroute results but your Internet Provider should be able to highlight the issue appropriately and get things looked into.
Fingers crossed it’s something that can be sorted quickly, they may even be aware of the issue already. If not then by giving them the results you have (the three traceroute links) and highlighting the areas of delay, it’ll help point them in the right direction.
Thanks for the troubleshooting and reaching out to us. Stay safe and all the very best o/