Hey there Sycaway,

Thanks for getting in touch!

I appreciate all of those details you provided - after pulling in your data from the share page, it looks like your connection is fairly healthy, with the exception of one 10-minute period of intermittent packet loss occurring between 2:04pm and 2:15pm on 08/04. See image.

https://imgur.com/a/jUNjR32

You can discover where the problem lies by double-clicking on a hop to open the Time Graph, and following the pattern of packet loss and latency from the target back to the source - the earliest hop that resembles this pattern (or the connection just before it) is usually the culprit. As you can see in the image, hop 2 or the connection before it seems to be causing the problem.

However, since your device/router looks like it may be down-prioritizing returning responses (this is common, and doesn't have an effect on your connection), this could be masking actual packet loss and might be carrying through to hop 2. Therefore, I would recommend tracing directly to your router to determine if there could be an issue there (192.168.1.1), as well as investigate the connection from your router to hop 2.

Regarding the hop changes, it looks like your route to Google.com is frequently changing. You can see these changes by hovering over the red triangles at the bottom of your time graph. For big companies like Google, route changes are common and are usually a result of load-balancing - which improve your connection speeds.

If you're interested, here's a handful of articles covering packet loss, latency, graphs, and interpreting PingPlotter data:

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

https://www.pingplotter.com/manual/interpretgraphsexampleone.html

https://www.pingplotter.com/wisdom/article/latency-packet-loss.html

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

I hope that helps - if you have any other questions or concerns, please feel free to reach out!

All the best,
-Austin