Nightly latency issues

[worldofneil]

What is this level 3 that you are talking about Scott?

If you do a traceroute to the SE server when you're having a problem you'll likely find that on route to the SE server you're going through one or more nodes that are owned by level3.net and at that point your connection falls apart and the ping increases and possibly packet loss as well (before it gets to SE).

[LionFranco]

If you do a traceroute to the SE server when you're having a problem you'll likely find that on route to the SE server you're going through one or more nodes that are owned by level3.net and at that point your connection falls apart and the ping increases and possibly packet loss as well (before it gets to SE).

How do i do the traceroute? i saw the instructions posted in the other topic, but i have no clue exactly how to do it. i cant even figure out the command, and it is different in Win10?

[Galibier]

How do i do the traceroute? i saw the instructions posted in the other topic, but i have no clue exactly how to do it. i cant even figure out the command, and it is different in Win10?

I would suggest using this. http://winmtr.net. first it is brain dead easy, just type IP address in the box and hit run. Next it will run until you stop it. A simple trace route can be deceptive because on highly congested nodes such a long can either be ignored or given a lower priority. Since WinMTR runs until you stop it, providing max and average pings as well as % loss it gives you a much more accurate picture.