Actually, the final destination is the most important hop - and yours looks very good (at least during the time period in question). We cover that in this knowledge base article here:

http://www.nessoft.com/kb/24

Of course, this is pretty frustrating to you - it *looks* like you've found a problem, but you've really not. It looks like something early in your route (it's hard to say for sure if it's hop 1, 2 3, or something else close to there) is dropping ICMP TTL expired packets (which is used to get data back on all intermediate hops), and showing packet loss for that type that's not "real". Remember that all data has to go through intermediate hops before reaching the final destination, so if you're not seeing packet loss at the final destination, then echo reply packets.

You might be able to improve your statistics a bit by only having a single outstanding packet - some routers have a propensity to drop multiple outstanding replies. We cover that here:

http://www.nessoft.com/kb/22

You might also try, just for fun (although this has only *occasionally* made an impact in this) switching your packet type to UDP and/or TCP packets instead of ICMP. For TCP, try using port 80. Depending on the problem, different packet types might behave differently and give you different results.

Even if your intermediate hops are showing packet loss (that isn't real), you can still use PingPlotter to troubleshoot the problem - you just need to find a period where you're having problems in-game and then look at the final destination to see if you're seeing packet loss or latency problems there. We cover this topic here:

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

When you see packet loss or latency at the final destination, then look for that same pattern at earlier hops. You'll need to look *through* the packet loss noise that you normally get at these hops, though, and identify just the packet loss that shows up at only the final destination - this can sometimes be difficult to do on hops with really high packet loss all the time, but usually there is a pattern that helps you identify an earlier hop as the culprit.

If you don't see any problems at the final destination *ever*, then it's probably not a network problem - it's something else (server problem, something with your computer, etc).

Let us know how this goes.

- Pete