Hey Tidal,

Sorry to hear about your gaming woes - stuff like this is never fun to deal with.

The screenshot that you provided doesn't show any obvious issues (as you've already deduced) - 22ms round trip latency with no packet loss is *usually* considered to be a great connection. You're dead on with your assumption on hops #9 and #10 here as well - those devices may just be set to not respond to ICMP TTL expired packets.

Is your screenshot here from an instance where you were attempting to play the game/connect to the server? If not - do you get any sort of different results in PingPlotter if you run it while trying to connect?

Your goal in troubleshooting here should be to try and correlate any issues you're experiencing with your PingPlotter results (a tactic we cover in more detail here: http://www.pingman.com/kb/47). This becomes especially difficult, however, when the issues you're experiencing don't seem to be reflected in your results. It *looks* like you're using the Free version of PingPlotter here - have you attempted to use PingPlotter Standard or Pro (in evaluation mode) to change up the packet type you're using? With either of these versions, you could switch over to TCP and target specific ports to see if there's any difference in your results there (which may help to provide some additional clues into your issue).

If you have any other questions - or if there's anything else we can try and do to help out, please let us know!

Best wishes,

-Gary