Hello!

Thanks for getting in touch - sorry to hear about your lag problems.

In the results you've provided, we can definitely see latency spikes you mentioned - which seem to start at hop #1, and carry through the entire route to your final target. This *may* imply that the culprit in any potential issues may be "close to home" (somewhere between the machine running PingPlotter - and hop #1, your modem) - but it's tough to say for certain. Without any knowledge of the issue you're attempting to troubleshoot, or reference on how these results correlate to your actual experience with your network - it's honestly tough for us to speculate on what may be happening here.

Your goal should be to correlate your experience with your network connection to any patterns you can identify in your PingPlotter results. For best results, you'll want to continuously trace to the service you're having trouble with (24x7, if possible). When you experience problems, 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 network connection. We cover this practice in quite a bit more detail here:

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

We've also got a great guide that goes over how to use PingPlotter to troubleshoot network issues, which may also prove helpful to you here:

http://www.pingplotter.com/fix-your-network/

Hopefully this helps out. If you have any questions, or if there's anything else we can do to be of assistance - please don't hesitate to reach out!

Best wishes,

-Gary