Hey Spencer!
From what we can see in your results (thanks for sending those over, by the way!) - it looks like you've got some packet loss and spikes in latency occurring right at hop #1 that are carrying through the rest of your route to the final destination. This pretty strongly implies that the culprit in your issue is *likely* somewhere between your machine (the one running PingPlotter), and hop #1 (your modem/router).
Your next goal should be to eliminate any variables that you have control over to see if you can isolate what the culprit is. If you're on a wireless connection, moving to a wired connection is a *great* first step. You could also try running PingPlotter on a different network all together (if possible), to see if the issue may be related to your machine (if you see the same results on a different network - this would be a pretty strong indicator). Anytime you're eliminating a variable, make sure to keep PingPlotter running so you can see if you notice any changes in your results (as this can help you identify what may be causing your problem).
We've got a great guide that walks through the process of using PingPlotter to troubleshoot an issue like this one, which may prove helpful to you here:
https://www.pingplotter.com/fix-your-networkHopefully this helps out! If you should find yourself needing any other guidance, please let us know.
Best wishes,
-Gary
Previous Topic
Index
