Extremly high ping for only half of the games


#1

For the last few months(maybe even more), I’m getting really high ping (500-5k). and its only happening in half of the game I’m playing maybe a bit less.

I can login and play a game with normal ping(80-90) and then the next game will be 500+.

my internet connection while playing in the high ping game is fine.

ping/pathping&tracert to 185.60.112.127/128 seems fine but looking glass seems weird

TRACEROUTE:
traceroute to 77.125.2.195 (77.125.2.195), 15 hops max, 60 byte packets
1 Blizzard Blizzard 0.904 ms 0.916 ms 0.919 ms
2 37.244.24.2 (37.244.24.2) 1.056 ms 1.147 ms 1.225 ms
3 Blizzard Blizzard 1.985 ms 2.019 ms 2.076 ms
4 137.221.66.42 (137.221.66.42) 1.309 ms 1.404 ms 1.429 ms
5 137.221.78.70 (137.221.78.70) 1.609 ms 1.639 ms 1.645 ms
6 137.221.78.34 (137.221.78.34) 2.318 ms 1.375 ms 1.334 ms
7 te0-0-0-9.rcr21.b021535-1.ams03.atlas.cogentco . com (149.6.128.8) 1.273 ms 1.246 ms 2.358 ms
8 be2322.ccr41.ams03.atlas.cogentco . com (130.117.50.81) 1.224 ms 1.227 ms 1.232 ms
9 be12194.ccr41.lon13.atlas.cogentco . com (154.54.56.93) 8.413 ms 8.439 ms 8.685 ms
10 be2870.ccr22.lon01.atlas.cogentco . com (154.54.58.174) 8.393 ms 8.748 ms 8.757 ms
11 be2867.rcr21.b015533-1.lon01.atlas.cogentco . com (154.54.56.242) 8.634 ms 8.743 ms 8.915 ms
12 149.14.147.91 (149.14.147.91) 8.216 ms 8.032 ms 8.015 ms
13 EDGE-LON-MX-01-ae0-102.ip4.012.net.il (80.179.165.105) 8.287 ms 8.309 ms 8.312 ms
14 EDGE-LON-MX-02-so-4-1-0-0.ip4.012.net.il (80.179.165.25) 68.062 ms 68.138 ms 68.104 ms
15 82.102.132.157 (82.102.132.157) 68.186 ms 68.166 ms 68.174 ms

06/02/2019 18:20:00 UTC

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

— 77.125.2.195 ping statistics —
4 packets transmitted, 0 received, 100% packet loss, time 2998ms

06/02/2019 18:20:00 UTC

MTR:
Start: Wed Feb 6 18:20:00 2019 Blizzard 1.|-- Blizzard 0.0% 10 0.3 0.3 0.3 0.5 0.0
2.|-- 37.244.24.2 0.0% 10 0.6 0.6 0.5 0.9 0.0
3.|-- Blizzard 0.0% 10 1.7 1.7 1.2 2.8 0.3
4.|-- 137.221.66.42 0.0% 10 0.7 1.3 0.7 4.1 0.9
5.|-- 137.221.78.70 0.0% 10 1.1 1.1 1.0 1.7 0.0
6.|-- 137.221.78.34 0.0% 10 0.9 1.0 0.8 1.2 0.0
7.|-- te0-0-0-9.rcr21.b021535-1.ams03.atlas.cogentco . com 0.0% 10 1.2 1.3 1.1 2.3 0.3
8.|-- be2322.ccr41.ams03.atlas.cogentco . com 0.0% 10 1.4 1.4 1.1 2.1 0.0
9.|-- be12194.ccr41.lon13.atlas.cogentco . com 0.0% 10 8.5 8.3 8.1 8.6 0.0
10.|-- be2870.ccr22.lon01.atlas.cogentco . com 0.0% 10 8.4 8.3 8.1 8.9 0.0
11.|-- be2867.rcr21.b015533-1.lon01.atlas.cogentco . com 0.0% 10 8.8 8.7 8.5 9.1 0.0
12.|-- 149.14.147.91 0.0% 10 8.7 8.7 8.0 13.6 1.6
13.|-- EDGE-LON-MX-01-ae0-102.ip4.012.net.il 0.0% 10 8.3 10.3 8.2 17.6 3.4
14.|-- EDGE-LON-MX-02-so-4-1-0-0.ip4.012.net.il 0.0% 10 68.3 67.9 67.3 68.3 0.0
15.|-- 82.102.132.157 0.0% 10 68.0 68.4 67.5 69.7 0.5
16.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0

06/02/2019 18:20:00 UTC


#2

I actually have been looking at this as well.

  2     *        *        *     Request timed out.
  3    46 ms    38 ms    35 ms  pl-ktw01a-rc1-ae18-0.aorta.net [84.116.253.129]
  4    63 ms    43 ms    37 ms  de-fra04d-rc1-ae30-0.aorta.net [84.116.137.41]
  5    60 ms    41 ms    40 ms  de-fra04c-ri1-ae9-0.aorta.net [84.116.140.190]
  6    36 ms    36 ms    37 ms  213.46.179.58.aorta.net [213.46.179.58]
  7    49 ms    52 ms    48 ms  ae1-br01-eqfr5.as57976.net [137.221.80.33]
  8    45 ms    61 ms    92 ms  et-0-0-2-br01-eqam1.as57976.net [137.221.65.29]
  9    44 ms    45 ms    49 ms  et-0-0-31-pe02-eqam1.as57976.net [137.221.78.69]
 10    47 ms    56 ms    49 ms  137.221.66.47
 11     *        *        *     Request timed out.
 12     *        *        *     Request timed out.
 13     *        *        *     Request timed out.
 14     *        *        *     Request timed out.
 15     *        *        *     Request timed out.
 16     *        *        *     Request timed out.
 17     *        *        *     Request timed out.
 18     *        *        *     Request timed out.
 19     *        *        *     Request timed out.
 20     *        *        *     Request timed out.
 21     *        *        *     Request timed out.
 22     *        *        *     Request timed out.
 23     *        *        *     Request timed out.
 24     *        *        *     Request timed out.
 25     *        *        *     Request timed out.
 26     *        *        *     Request timed out.
 27     *        *        *     Request timed out.
 28     *        *        *     Request timed out.
 29     *        *        *     Request timed out.
 30     *        *        *     Request timed out.

Trace complete.

Yours is in better condition than mine.


#3

electRon, some nodes display pretty high values. Have you already tried troubleshooting steps here? Especially the one concerning apps running in background - make sure you close everything.

Should there be no changes at all, please add your traceroute and pathping tests to your reply, as well as a link to your MSInfo file (you can upload it to Pastebin).



Feedback? Click here! https://www.surveymonkey.com/s/Vyraneer


#4

CasualPlayer, is the test you posted yours? Do you experience exactly the same issue like the one electRon described or yours is more of a general latency? If the test is yours and the above is the only one you have, could you please open your own thread, explain what happens in game and add a WinMTR as well?

Please indicate also troubleshooting steps you already tried yourself.

Thank you!



Feedback? Click here! https://www.surveymonkey.com/s/Vyraneer


#5

Have you already tried troubleshooting steps here?

yup, I tried all of them before but the DNS flush, which I did just now and tested and the issue still occurs.

please add your traceroute and pathping tests

no problem, here they are right at the end of a problematic game:
https:// pastebin. com/puVKH6C5

and here is my MSInfo:

https:// gist. github. com/ronhasson/fe4a0ea03b113a849c70d25ee13ebce9

btw, whyyy am I not allowed to put links in my posts? i just added spaces. ( and i used github’s gists bc pastebin limits to half a mb)


#6

I just keep task manager up and it solves the every 90 secs stutter.

I find it humorous that this trick works, every time I use a trick that works without reason I think of Todd Howard’s words:“It just works!”

XD


#7

That’s…uhm…rather curious. :thinking:
I’m afraid can’t come up with an explanation without knowing more about your issue and your system, but if you’re still trying to solve that stutter, odd 3rd-party software interaction and power management settings are the first things I’d check.

It seems it does indeed! But should you want to delve deeper into magic try and figure what the cause of the stuttering is, do not hesitate and open your own thread.
Beware though, you won’t be able to dodge the usual traceroute/pathping/MsInfo request!

Note: I tried to check if you already had a thread, but I couldn’t find any. :confused:



Feedback? Click here! https://www.surveymonkey.com/s/Vyraneer


#8

You can bypass this restriction by highlighting the link and using the </> button. :slight_smile:

Your MSInfo shows quite some programs running, ElectRon. :confused:
Please remove Hamachi completely (don’t just disable it) and repeat the selective startup once again. Make sure you only leave programs your system needs to function properly, and close everything else (overclocking suite, overlays, OneDrive, and so on). Bring also the clock speeds back to factory defaults.

Additionally, check if Windows Defender has real-time protection enabled - if it does, try disabling it for the test.



Feedback? Click here! https://www.surveymonkey.com/s/Vyraneer


#9

Usually I just get into tech support section of the forum, search who has a similar issue, read whats explained, usually laugh at the bad english and decide to either pinch in or answer with an unsolvable but working solution.

I mean, my method simply works, I know the cause as well.
There are multiple symptoms:
-tracert and ping lose packets, it’s hard to pinpoint the timing because it seems random, but it is around the 90 second pass.
If you perform a ping for 120 secs you will spot the lost packets, tracert will not run well enough to point out the error log on connection point, as it follows a route from point A to point B it will simply not show the correct error connection point unless you RNG it perfectly.

The log I showed is a genuine RNG Legendary WoW drop, seriously, I ran over a dozen tracerts to catch it. My assumption is that something at that point is causing the server to choke every 90 secs, most likely a faulty drive, or other piece of equipment. Probably not even related to Blizzard because it’s “along the way”.

Now why is the task manager solution working:
Simple, task manager is weird, it’s a part of Windows which is even weirder.
Task Manager monitors and maintains the order of processes and services ran on the OS.
While it’s up, it can occasionally “change” the route of the packets going outside.
The first time it peaks lag capacity after 90 secs it will send the packets a different route, not the shortest default one but a slightly longer one.

Normally you’d not expect Windows software to do this because: HOW?
The answer is: Windows tracking.
Microsoft Windows 10 is constantly tracking users, it invades the privacy just like google does, you can disable most of telemetry on Windows 10, but not ALL, and that’s enough for Windows to track telemetry and use teh data it recieves from multiple sources to change routes.

After all, Microsoft wants all our po_rn and it needs a safe route to extract all our data from our computers safely and reliably.

So yeah, the cause is that somewhere on the route of the shortest tracert to the EU server, the system encounters a faulty working connection point that has damaged equipment. Windows will simply redirect the signal.

This is the issue of EU basically having only 1 possible connection server per zone while areas like Asia and USA have a multitude of servers they can connect to on the go. I played on the US servers and could easily switch between 5 servers, and on Asian realm I could switch between 3.

European players only have ONE local server to connect to, whether it’s HotS or OverWatch or even Diablo III (RIP) European players can only connect to a single realm server, which really impacts our gameplay experience.

Task Manager simply works, I don’t need another solution.
A possible solution would be to make HotS work on Linux distros, but fat chance of that happening because then Blizzard wouldn’t be able to collect user data.

Nothing is perfect.


#12

OK since you were suggesting this is a software issue, Instead of running around and disabling everything (although I did this a month ago) and hoping that there isn’t a hidden windows thing that causes this, I decided to go extreme and install Linux on a new partition and install the game there.

A barebone fedora installation on a new partition with only the Nvidia drivers, wine(a compatibility layer) and discord to yell at my friends.

The game ran pretty smooth, only a 10 fps less from the windows version(expected with a compatibility layer)

But instantly I got a game with 500+ ping even tho I could play other online games like csgo without any lag and low ping.

:frowning:

ps, ty for the tip with the </> button