Hey there,

Thanks for getting in touch with us!

As far as what I can see on your traces that you've sent, I can't quite gather enough information to tell you for sure where the issue lies. It does look like, on your traces, there is some significant packet loss in intermediate hops, but that packet loss is not carrying to the final destination (which is the hop we really care about), so I'm not *quite* seeing a ton of area for concern (only taking into consideration the screenshots I can see).

I would suggest doing the following: Run the trace to your gaming server for as long as you can, 24x7 if you're able. When you notice an issue with your game, make a note of what time it happened, and head back to PingPlotter when you're ready. The goal here is to correlate PingPlotter results to actual real-world performance. Is there a "problem pattern" near the time of your game failing? If so, you can then trace back to see which device the problem started at. Here's a page we've got on some problem patterns and how to identify them:

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

If you don't see a problem pattern, then you might need to leave PingPlotter running for more time in order to actually find where your problem is. Just keep trying, and when you think you've caught something, that's when you should start investigating who caused it. Here's some information that might help you find this out:

https://www.pingplotter.com/fix-your-network/capture-problem.html

If nothing seems to help, you *may* need to turn to another potential solution; there may be a failing NIC, or an overloaded processor, or maybe a bad graphics card! There are so many variables in gaming that we definitely should look into not only the scope of the network, but also into other equipment that affects gameplay as well.

Let me know if there's anything else I can help with!