Hey Luscion,

Thanks for sending over the additional data!

From what I can see in the .pp2 file you've provided; hop #3 starts having some spikes in latency that end up carrying through the rest of the route. From this - we can rule out the World of Tanks server as being the potential culprit, as this appears to be bandwidth saturation that's occurring *very* early in the route. I've attached a screenshot from your results to better show what I'm referring to here. As you can see in the highlighted area in the image - the spike occurs at hop #3, and pretty clearly carries on all the way to your target (and this seems to happen multiple times throughout the results).

The packet loss that's occurring (starting at hop #5) could potentially be a result of this saturation as well. It could also imply an issue inside of that provider (Columbus Trinidad).

There's a definite possibility that the bandwidth saturation here could be happening somewhere between you and your ISP. Are you by chance using a wireless connection? If so - it may be a good idea to move to a wired connection, and try tracing from there to see if the problem persists.

It would also be a good idea (if possible) to disconnect everything else from your network while you try running PingPlotter from a wired connection. The goal at this point is to eliminate as many variables as possible in order to better narrow down what could be causing the issue here. If you notice that the connection seems to get better after disconnecting everything else, then you can begin reconnecting devices (one at a time) to see if you can narrow down any potential culprits there.

We've recently released an article that goes over some troubleshooting tactics and strategies that may be helpful to your situation here as well:

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

Hopefully this helps get you headed in the right direction! If you have any other questions, or find yourself needing further assistance - please let us know.

Best wishes,

-Gary