Here's a screenshot of PingPlotter Pro in action. Notice the four visible tabs, each tracing to a destination. Also worth noting is the jitter graph above the latency history graph at the bottom of the shot. Below the Address to trace entry box, you can see that there's a dropdown with one of the saved configurations being used. In this case we're using FTP, or Port 21 and utilizing the TCP trace feature.

This data has some interesting characteristics that become relatively easy to spot when graphed.

This is a graph of 48 hours of data. One of the most interesting pieces here is the packet loss and latency changes over time. Both packet loss and latency look relatively good around 5am, but around 8am, things start to look worse.

Both packet loss and latency start to degrade, and in the evening hours we're getting nearly 20% packet loss, and the latency is significantly higher than it is in the early morning hours..

This time-dependent latency, packet loss changes and Jitter are typical of bandwidth problems. During heavy load periods, performance degrades. The question, then, is whose problem is it?

If you have a look at the upper graph, hop 8 is showing no packet loss, while hop 9 is showing significant loss (keep in mind you can focus in on any period of time). Hop 8 is on the Roadrunner network, while hop 9 is on Alter.net. This is a junction point, and the link between these two providers is probably not big enough. The subscriber should contact RoadRunner in this case to encourage them to solve this problem.