Sping – a modern ping for humans
https://i.redd.it/u4toy3ynsvsh1.gif
https://github.com/LambdaBytes/sping
I built Sping because I kept running into the same problem: ping tells you that something is not replying, but then you still have to figure out whether the problem is your local network, your gateway, the Internet connection, or the target itself.
Sping tries to put that context in one place. It monitors the target, gateway and WAN connectivity at the same time, and combines that with latency, jitter, packet loss, TTL, trends and a simple quality score.
It is written in Rust and uses its own ICMP implementation on Linux, macOS and Windows rather than shelling out to the system ping command. It also supports IPv4/IPv6, multiple targets, batch mode and a stable NDJSON output for scripting.
The goal is not to replace tools like mtr or traceroute. It is mainly meant to answer the first practical question when something feels wrong: is the problem local, upstream, or just the target?
I would be interested in feedback from people using it on different networks and platforms, especially cases where the diagnostics get the situation wrong.