@coolspot said in dpinger latency vs. ping from command ping?:
Any ideas why dpinger reports a higher RTT and RTTsd than a command prompt ping?
You always need to set the source IP for ping to ensure you are using the expected interface regardless of routes. See the -S option to ping. NB: Static routes are optional. See System / Advanced / Miscellaneous / Gateway Monitoring.
With default parameters for command line ping, you are averaging a small number of packets, once per second. With default parameters for dpinger, you are averaging 116-120 packets spread over 60 seconds. The packets are also dramatically different sizes.
Google's 8.8.8.8 and 8.8.4.4 are not really very good for monitoring anymore. Lots of variance, particularly on 8.8.8.8. If you really need to go out across the internet, try Cloudflare (1.1.1.1) instead.
That you have such a high standard deviation on your WAN indicates that something between you and the monitoring target is not very stable.