everynow and then the game would stop responding i can see my char moving the animation of all the mobs are still working but the game not responding i can’t cast i can’t attack or get attacked or anything, the chat i can see it working properly can talk and see people talking but i’m froze in the game.
sometimes it happen for 5 sec or few sec in general sometimes it goes forever and i’m forcedto alt F4
my ping in game is 24 ms and i have no such problem in any other game ever, not even in WoW BFA
server Zandalari tribe
This is a symptom of temporary high packet loss between you and the server., which can be difficult to isolate the cause of, because by the time you fire up winmtr, the event has passed.
Invalid comparison because classic isn’t “any other game ever”, nor is it BFA.
That’s like complaining to the bus company that your number #22 bus was delayed due to roadworks, and it was the bus companies fault because the #44 bus which goes to an entirely different location had no problems, and yelling at them to fix their buses.
You can only compare like with like.
point is my internet is fine before i get replies to tell me its my internet fault.
Read the bus anology again, and try and understand it this time. If you still don’t understand it, rinse, repeat.
dude if i wanted to fish for a troll i would have went in any other forum but technical support, if you don’t have anything helpful to say please don’t say anything then.
Dude, you obviously don’t understand networking.
Is the server you care connecting to, housed at the same IP as “every game ever”, I certainly hope not or that server would need to be as big as a planet.
No, its housed at a different ip ADDRESS <- theres the bus anology.
Your routing to “every game ever” might be OK, but the routing to a particular server might have “roadworks and traffic lights”, causing transient packet loss.
What you are trying to argue is that because the internet connection to, for example, 8.8.8.8 works perfectly, then the internet connection to 201.7.1.3 must also work perfectly. NOT TRUE.
But this is pointless. You can lead someone to knowledge, but you can’t make them learn, so, good luck out there.
i’m not argueing against anything, i just had that piece of information there to whoever can figure out my problem might eliminate a bad internet from the list of problems, you not helping my problem if you can’t its ok no need to say anything unrelated.
i want someone to give me a real thing to try and do to fix my problem not point at it and say thats your problem, if you know alot then tell me how to fix it or stop posting.
Hello Mclothar 
I am afraid Trovlak may be actually correct in this case, the description you provided in the first topic is exactly what happens in case of network related issues such as a packet loss.
On this regard please also keep in mind that being able to connect without issues to other services is not exactly relevant, as the routing taken by your signal is different based on the physical location of the destination. The Bus analogy Trovlak posted is again correct, albeit maybe a bit generic.
To expand on it a bit, you can compare a network routing to the road network of a country.
So let’s say for example that you live in Paris, and you want to take a car trip to Madrid. You’ll need to take a specific road that will lead you to go towards a specific direction and that will cause you to pass through specific points and other cities.
Now let’s say instead that you decide to go to Florence, in Italy.
The situation is very similar to the above, however the specific road you’ll need to take will go towards a completely different direction, and you’ll pass through other points and other cities.
Along the road to Florence however something happens, and you find a long queue due to road works or an accident. That will cause you to stop, and will delay your arrival in Florence. However this will not have any effect on the road through Madrid.
The same applies to a connection.
The “road” your signal will take to reach WoW servers will not be the same - in full or in part - of the “road” that your ISP will use to reach servers of a different services. Such routing is decided by the ISP itself based on the physical location of the service you want to reach, and is relatively fixed.
As much as I understand you don’t want to consider this, I am afraid a network issue is not something that can be ruled out immediately. Exactly for this reason though I would like to ask you to provide us with results of a WinMTR test, left running for as long as possible and while the problem is happening.
Those results will hopefully show exactly what is happening, and may help ruling out - or confirm - a possible network related issue.
Here are the 3 tests on all of the Europe IPs.
WinMTR Statistics
WinMTR statistics
| Host | % | Sent | Recv | Best | Avrg | Wrst | Last |
| speedport.ip | 0 | 3510 | 3510 | 0 | 0 | 9 | 0 |
| 62.155.241.91 | 0 | 3509 | 3509 | 5 | 7 | 90 | 7 |
| 217.239.51.50 | 0 | 3510 | 3510 | 13 | 15 | 49 | 15 |
| 62.157.248.74 | 0 | 3510 | 3510 | 14 | 19 | 500 | 15 |
| ae1-br01-eqfr5.as57976.net | 0 | 3509 | 3509 | 21 | 24 | 126 | 52 |
| et-0-0-2-br01-eqam1.as57976.net | 0 | 3470 | 3470 | 21 | 49 | 3080 | 23 |
| et-0-0-31-pe02-eqam1.as57976.net | 0 | 3509 | 3509 | 21 | 25 | 106 | 22 |
| 185.60.112.157 | 0 | 3510 | 3510 | 17 | 19 | 52 | 20 |
WinMTR Statistics
WinMTR statistics
| Host | % | Sent | Recv | Best | Avrg | Wrst | Last |
| speedport.ip | 0 | 1263 | 1263 | 0 | 0 | 3 | 0 |
| 62.155.241.91 | 0 | 1263 | 1263 | 5 | 7 | 82 | 7 |
| 217.5.118.82 | 0 | 1263 | 1263 | 14 | 15 | 25 | 16 |
| 62.157.248.74 | 0 | 1263 | 1263 | 14 | 19 | 294 | 15 |
| ae1-br01-eqfr5.as57976.net | 0 | 1263 | 1263 | 21 | 24 | 143 | 22 |
| et-0-0-2-br01-eqam1.as57976.net | 0 | 1263 | 1263 | 21 | 25 | 137 | 22 |
| et-0-0-31-pe01-eqam1.as57976.net | 0 | 1263 | 1263 | 21 | 25 | 97 | 22 |
| 137.221.66.41 | 0 | 1263 | 1263 | 21 | 22 | 28 | 22 |
| 185.60.112.158 | 0 | 1263 | 1263 | 18 | 18 | 23 | 19 |
WinMTR Statistics
WinMTR statistics
| Host | % | Sent | Recv | Best | Avrg | Wrst | Last |
| speedport.ip | 0 | 1293 | 1293 | 0 | 0 | 5 | 0 |
| 62.155.241.91 | 0 | 1293 | 1293 | 6 | 7 | 96 | 7 |
| 194.25.6.182 | 0 | 1293 | 1293 | 14 | 14 | 30 | 15 |
| 62.157.248.74 | 0 | 1293 | 1293 | 14 | 20 | 502 | 15 |
| 137.221.80.35 | 0 | 1293 | 1293 | 25 | 27 | 122 | 26 |
| et-0-0-2-br01-eqpa4.as57976.net | 0 | 1284 | 1284 | 25 | 39 | 4620 | 26 |
| be1-pe01-eqpa4.as57976.net | 0 | 1293 | 1293 | 25 | 26 | 37 | 26 |
| 185.60.114.159 | 0 | 1293 | 1293 | 24 | 25 | 46 | 25 |
My problem seem to have gone away after i reinstalled the game, can’t tell for sure haven’t been playing for long but it used to happen frequently so hope it got fixed with the restart.
If the problem reoccurs, run the winmtr tests while you are having issues.
sure will try but problem is sometimes it only happen for couple sec i wont have time to run the test but when the long one happen i will, another problem is blizzard site provide me with 3 europe IPs not sure which one to use for my Zandalar tribe server.
Hello Mclothar 
Considering the randomness of the problem I would suggest you to simply leave WinMTR running in background while you play, it won’t have any impact on your latency.
As for which IP to use… ideally all 3 (you can open an run more than one instance of WinMTR at the time), but if you prefer to run just one any would do
i did the test i kept WinMTR running and the problem did happen everytime it would happen i copy the test resault and change the IP to different europe IP to see if it make difference but it doesn’t seem its a packet loss problem.
WinMTR Statistics
WinMTR statistics
| Host | % | Sent | Recv | Best | Avrg | Wrst | Last |
| speedport.ip | 0 | 2461 | 2461 | 0 | 0 | 6 | 0 |
| 62.155.241.91 | 0 | 2461 | 2461 | 5 | 7 | 92 | 7 |
| 217.239.51.50 | 0 | 2460 | 2460 | 13 | 14 | 47 | 14 |
| 62.157.248.74 | 0 | 2461 | 2461 | 13 | 18 | 105 | 39 |
| ae1-br01-eqfr5.as57976.net | 0 | 2461 | 2461 | 21 | 24 | 290 | 22 |
| et-0-0-2-br01-eqam1.as57976.net | 1 | 2368 | 2356 | 21 | 67 | 4995 | 22 |
| et-0-0-31-pe02-eqam1.as57976.net | 0 | 2460 | 2460 | 21 | 25 | 140 | 22 |
| 185.60.112.157 | 0 | 2460 | 2460 | 17 | 18 | 28 | 18 |
WinMTR Statistics
WinMTR statistics
| Host | % | Sent | Recv | Best | Avrg | Wrst | Last |
| speedport.ip | 0 | 11632 | 11632 | 0 | 0 | 6 | 0 |
| 62.155.241.91 | 0 | 11631 | 11631 | 4 | 7 | 104 | 7 |
| 217.5.118.82 | 0 | 11631 | 11631 | 13 | 15 | 36 | 16 |
| 62.157.248.74 | 0 | 11629 | 11629 | 12 | 19 | 2615 | 15 |
| ae1-br01-eqfr5.as57976.net | 0 | 11630 | 11630 | 20 | 24 | 137 | 23 |
| et-0-0-2-br01-eqam1.as57976.net | 0 | 11542 | 11542 | 19 | 39 | 3740 | 22 |
| et-0-0-31-pe01-eqam1.as57976.net | 0 | 11631 | 11631 | 20 | 25 | 129 | 73 |
| 137.221.66.41 | 0 | 11630 | 11630 | 20 | 22 | 49 | 23 |
| 185.60.112.158 | 0 | 11631 | 11631 | 16 | 18 | 55 | 19 |
WinMTR Statistics
WinMTR statistics
| Host | % | Sent | Recv | Best | Avrg | Wrst | Last |
| speedport.ip | 0 | 7711 | 7711 | 0 | 0 | 5 | 1 |
| 62.155.241.91 | 0 | 7710 | 7710 | 4 | 7 | 108 | 6 |
| 194.25.6.182 | 0 | 7710 | 7710 | 12 | 14 | 41 | 15 |
| 62.157.248.74 | 0 | 7710 | 7710 | 12 | 18 | 353 | 15 |
| 137.221.80.35 | 0 | 7710 | 7710 | 23 | 26 | 143 | 26 |
| et-0-0-2-br01-eqpa4.as57976.net | 1 | 7537 | 7519 | 23 | 53 | 4821 | 25 |
| be1-pe01-eqpa4.as57976.net | 0 | 7710 | 7710 | 23 | 25 | 42 | 26 |
| 185.60.114.159 | 0 | 7710 | 7710 | 22 | 24 | 53 | 25 |
EDIT : today same thing happen and got DC with code WOW51900319