Hey Noin,

Thanks for writing in.

It's tough to speculate on what may be going on here with the limited amount of data we can see in this screenshot. For the most part, these results don't *seem* to point to any specific problems. 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 keep a trace running in PingPlotter constantly (24/7, if possible). When you experience problems with your network, 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 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.

Best wishes,

-Gary