Hey there,
So I want to clarify reading/using a WinMTR.
It is a live test, testing all nodes along a path at the same time. If there is an issue at any node, every node after will show similar or worse results. You won’t have a bad node and then everything after it look normal.
The easiest thing to do is look the first hop which is your PC to your network device. If everything looks good there, look at the final visible hop. If there is no data loss there and the latency looks about how it should, then the test can show anything on the nodes in between and it won’t matter because your data made it to the end point as it was supposed to.
Some nodes ignore test requests, some deprioritize such request and some mask the data giving fake results. What we are looking for over individual node numbers are patterns.
If you start losing data at say hop 2 and every node after that shows similar or worse data loss? that is something to look at. If latency jumps up really high a say hop 4 and then continues to increase … that is something to look at.
The other thing to keep in mind is that the test only measures what your connection is doing at that moment it is running. And connection issues have a bad habit of being intermittent. Enough to mess up a game over time but not gonna affect much else in a very noticeable way. So always run the test for a consistent length (10 minutes is what I recommend) while replicating the issue. If you cant replicate in 10 minutes, stop and restart the test every 10 minutes and keep going until the issue happens. Those are the results you want to analyze.