Hey Draxton,

Thanks for reaching out!

Due to the nature of a screenshot, it is difficult to say exactly where this issue is originating. With that said it does look like this is starting around the first few hops in the route.

In further troubleshooting this issue I suggest running a trace directly to your router (Hop #1 IP) to help rule out if this is or isn't a local network issue (if there is packet loss in your trace to the router this could be indicative of a local network issue, if there is not it may be an ISP issue).

You can find more information about isolating the problem and interpreting your results using the following links:

https://www.pingplotter.com/wisdom/common-network-problems

https://www.pingplotter.com/fix-your-network/getting-started/troubleshooting-with-pingplotter.html

https://www.pingplotter.com/fix-your-network/interpret-results.html

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

Note that due to the limitations of PingPlotter Free, collecting sufficient data can take a while.

It is also worth mentioning that we developed PingPlotter Sidekick for issues such as this one. Featuring automatic target selection/data collection and assisted interpretation Sidekick can help take a lot of the time/effort out of resolving network issues. Sidekick is $20.00 USD for 28 days of usage (with no reoccurring charge after the 28 days). If you would like to take a closer look at Sidekick you can do so HERE

Let me know if this leaves you with any questions or concerns!

Thanks,
-TJ