Hello!

Were these results captured during periods that you were experiencing issues with your game? In the "srcsample.pp2" file you provided, we can definitely see some clear spikes in latency (which looks to be occurring somewhere between hop #9 and #10 in the route) - but without knowing if this correlates to an instance where you were experiencing issues with your game, it's tough to say for certain if it's the culprit in the problem you're trying to chasing down.

To narrow things down a bit further, your best bet would be to set PingPlotter up to trace continuously (24/7, if possible) in the background while you play your game. From there, your goal should be to to try and correlate any problems you're experiencing playing your game to any patterns you can identify in your PingPlotter results. When you experience issues in your game, make note of it in PingPlotter (more details on how to do this here: http://www.pingplotter.com/manual/time_line_graphing.html), so you can see if any "problem" patterns are present in your PingPlotter results when you're actually running into problems with your game connection. If you're interested we cover this practice in quite a bit more detail here:

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

Hopefully this helps get you headed in the right direction! If you have any other questions - please let us know.

Best wishes,

-Gary