Forum Discussion
NameWasWayTooLon Hop 1 in the traceroute is your home router. It's showing 59% packet loss and ping spikes over 500ms. The home router is causing ping spikes in your gaming.
The way traceroutes work is the lowest number hop showing a problem, affects all the hops that come after it.
Since Hop 1 is showing packet loss and ping spikes, it's going to cause packet loss and ping spikes for all the hops that come after it. Hop 2 thru Hop 10. The game server is basically Hop 10.
We need to troubleshoot why the home router is causing ping spikes. Usually if an ethernet cable is connected to the home router and a PC, the ping time to the home router is 1ms and really steady.
Is the PC connected to wifi or cable ethernet?
OskooI_007 I'm seeing packet loss at gateway as well on ping plotter , but I do not see it when opening a cmd and running a ping (gateway ip) -t.
This makes me want to believe it's something to do with new windows11 releases and ping plotter software. Possibly a routing cache displaying as ping loss? IDK just theorizing here.
- OskooI_0073 months agoLegend
Trichomecookin I welcome the help! I don't notice any packet loss on my home router with PingPlotter running on Win11 version 25H2.
PingPlotter starts off by running a traceroute and then switches to pinging all the IP addresses.
Now that you understand how traceroute works, we can talk about how PingPlotter works. When you first start a trace in PingPlotter, it initiates a traceroute so that it can find all of the hops between the computer and the intended target. Once it finds all of those hops, PingPlotter starts pinging each of those hops every 2.5 seconds. Every so often it will run another traceroute to see if the route to the final destination has changed.
https://www.pingman.com/kb/article/traceroute-vs-pingplotter-160.html
- Trichomecookin3 months agoSeasoned Novice
Interesting, if that's how ping plotter works, it seems that the traceroutes go through and display in the "cur" column, but the pings will not. Falsely displaying as packet loss. I'm going to consider this a non issue and not worry about it.