Hey Zawyn,

Thanks for writing in! We're glad to help.

I'm really glad to see all the detailed traces you ran. That's a great step in the right direction!

The first thing that I usually recommend is to leave PingPlotter running a trace to your gaming server, continually (24x7 is ideal). Play your game as normal, and when you notice lag, make a note of it somewhere. Here, your goal is to correlate the issues you're having to PingPlotter data, so when you're done playing the game, head back to PingPlotter and track down the times that correlate with the ones you made a note of. Can you see any "problem patterns" in PingPlotter at that time? If so, this can help point you towards which device(s) may be giving you issues along the way. I'd like to point you towards a page we have detailing a great way to get started on deciphering results for gamers (for after you've correlated a time in PingPlotter to the time you wrote down):

https://www.pingplotter.com/manual/interpretgraphsgamer.html

When you're running your traces, please keep in mind, the most important hop is the final destination. If you're seeing packet loss in intermittent hops, but no packet loss at the final hop, you are *most likely* in the clear. If you want more information on this, check out our article on packet loss in intermediate hops:

https://www.pingman.com/kb/24

Based off your traces to the American gaming servers, I can't quite see your final hop (although I assume that in your imgur post, it's that hop 22 with complete packet loss), so I don't have enough information to be able to really point you towards a definite solution. However, leave those traces running as aforementioned, and see if you can't correlate some patterns in preceding hops to the final hop packet loss, as well as to the issues you're experiencing at any given time!

You did a great job identifying that the American gaming servers may be giving you a lot of packet loss. I was about to make a mention of that until I saw you addressed it! I'd just advise you to keep that in mind; you may not necessarily be dealing with a lot of packet loss, but you may also be seeing a lot of latency because of the distance your packets must traverse. 800ms - 3000ms is not *that* uncharacteristic of a packet that must travel as far as yours need to, especially with the type of payload it's carrying. PingPlotter has a built-in latency monitor (that colored graph to the right of all your hops, and in the big graph at the bottom), so when you're making notes of your issues in your games, make sure that when you go back and take a look at PingPlotter, you're also looking for those latency spikes.

Finally, to address the general web traffic issues you're having, I'd point you in the same direction as I did when diagnosing your gaming issues. Start a trace to the service you're trying to access (like YouTube), and leave it running for the entirety of the time that you're using the service. Try and make those correlations between network symptoms and PingPlotter data! Is there anything sticking out of place?

Let me know if that got you started in the right direction! Thanks again for writing in.
_________________________
Regards,
Hayla