Thanks for getting in touch.
When you mention that a continuous ping shows 6% packet loss, are you referring to a command prompt ping? The PingPlotter results that you've provided here don't explicitly point to any issues; you've got a pretty small amount of packet loss at the final destination in both traces (between 0.1% and 0.2%), but it's honestly tough to say if that's causing the issue you're experiencing.
That doesn't mean that you're not experiencing issues, though - it just means that a bit more work may be required to capture them.
If you're having issues with your connection, 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 trace to the service you're having trouble with. 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
Your next goal should be to eliminate any variables (that you have control over) to see if you can try to isolate what the culprit in your issue is. We've got a great article that provides some tactics and best practices on this front: https://www.pingplotter.com/fix-your-network
Hopefully this helps get you headed in the right direction! If you should find yourself with any other questions - please let us know.