Hey Fooram,

Thanks for writing in!

You're dead on here - the most important hop is your final destination. Often times when you see packet loss at an intermediate hop, it's because the device at that location doesn't prioritize timed out ICMP request very high (or doesn't respond to them at all). As long as the packet loss at these hops doesn't carry through to your final target - then you don't need to worry about factoring it into your troubleshooting efforts. We cover this topic in a bit more detail here:

http://www.pingman.com/kb/5

That being said - the four screenshots you've attached here don't specifically point to any sort of a problem (around 30ms round trip latency with no packet loss to a final destination is *usually* a pretty good result). That isn't to say that you aren't experiencing any issues, though. At this point - the best course of action is likely to continue your monitoring. Ideally, you want to keep PingPlotter running continuously (even in the background while you're playing your game).

The timeline graphs that are found in PingPlotter Standard and Pro can also be a *huge* help in spotting any problem patterns as well. Each version of the program does come with a 30-day free trial (which is usually a good amount of time to narrow down any issues) - so I'd definitely recommend downloading and installing one of those versions to give yourself a "leg up" here.

We've also got a guide that goes over some additional strategies for troubleshooting an issue such as this - which may prove helpful to you here:

http://www.pingplotter.com/netnirvana/

Hopefully this helps get you headed in the right direction! If you should find yourself with any other questions, or needing any assistance - please be sure to let us know.

Best wishes,

-Gary