Hey there!

So when you’re trying to find the source of your issue, the final hop always takes precedence. If the final hop looks good, you can likely conclude your investigation without looking into the intermediate hops. This is the case for you – that final hop looks great, so the packet loss at hop 10 isn’t carrying through. However, if we did see poor behavior on the final hop, that’s when intermediate hop behavior will bear some weight in your investigation. Does this kind of make sense? To summarize - packet loss on intermediate hops won't be relevant in your trace unless that same packet loss is showing at the final.

What you will want to do, however, is find the IP address of the server you're playing on, and initiate a trace to that. You can usually find the IP by searching on the web, or by contacting that game's support technicians. Then, initiate the trace while you're playing, make a note of when you have issues, and look back to PingPlotter to find a problem pattern, potentially similar to one found here:

www.pingplotter.com/fix-your-network/common-network-problems

If you do this, let us know what you see - and we'll be glad to look at that trace if you'd like!