Hi BenT,
Thanks for reaching out - I'm happy to lend a hand here.
Test results from a command-line ping can be different than what PingPlotter is showing. It's possible that this traffic is a lower priority than the command-line ping (thus the spikes), and PingPlotter operates with both ping
and traceroute.
In addition, your packet configuration in PingPlotter (Edit -> Options -> Chadwick Internal) may be slightly different than what command-line ping is using.
If you're interested, we've got an article here which talks about the differences between ping -t and PingPlotter:
Ping -t vs PingPlotter We've also got an article which speaks to the benefits of using PingPlotter over ping -t:
And the Best Ping Tool is... Should I Trust My PingPlotter Results? Let us know if you have questions or need help with anything else!
All the best,
Austin BernerSoftware Support Technician | Pingman Toolssupport@pingman.com | (208) 345-0030