Hey Zerg,

Thanks for following up.

Were the results that you've provided here taken during a period where you were playing your game (and experiencing issues)?

If you're trying to get to the bottom of issues you're having with an online game - your best bet would be to set PingPlotter up to trace to the game server you're playing on, and let it run 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 connection to the game. We cover this practice in quite a bit more detail here:

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

If you can start to identify some patterns, your next goal should be to isolate, and eliminate any variables (that you have control over) to see if you can further narrow down the culprit (while continuing to collect data in PingPlotter, so you can see any effects on your results). Moving from a wireless to a wired connection is a *great* start. If you're already on a wired connection, swapping out the cable that's connecting your machine to your modem/router is also a great test. Once you can eliminate a few things as being culprits, it can help focus your troubleshooting efforts. We cover some other tactics on this front in more detail in the guide I referenced in my last message (http://www.pingplotter.com/fix-your-network).

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

Best wishes,

-Gary