Wooo, Windows support! Availability of network diagnostics tools in Windows has been problematic, particularly for very infrequent use. There are some good looking ones for purchase, but it's hard to purchase when we don't usually need it.<p>For a while, largely related I think to just not having enough bandwidth at our office, but also partly because our coax on the Xfinity cablemodem was sketchy, we were not infrequently having issues, and the majority of my coworkers are on Windows. ping and tracert aren't very good tools for finding out what is going on with intermitant networking issues, especially when it might also be people's home wifi from WFH. There were times I just wished they could run mtr.<p>Over the last year or so I've been seeing more Windows tools available, which has been great!
Another interesting tool in this space is trippy, which ‘combines the functionality of traceroute and ping’<p><a href="https://github.com/fujiapple852/trippy">https://github.com/fujiapple852/trippy</a>
What I like doing is using ttyplot and then it supports many commands and you can even specify an extraction param to plot on so then it's very Unix philosophy.<p><a href="https://github.com/tenox7/ttyplot">https://github.com/tenox7/ttyplot</a>
There already exists a tool called nping. It comes with nmap.<p><a href="https://nmap.org/nping/" rel="nofollow">https://nmap.org/nping/</a>
I wonder why www.google.com resolved to 31.13.94.37, which IPinfo tells me belongs to AS32934 Facebook, Inc.<p><a href="https://ipinfo.io/31.13.94.37" rel="nofollow">https://ipinfo.io/31.13.94.37</a>
Neat, reminds me a lot of noping which is a long-time favorite of mine (and its non-graphical counterpart oping): <a href="https://noping.cc/" rel="nofollow">https://noping.cc/</a><p>One thing I've always wanted in a ping tool but never found is something that can log anomalous results, so for example one could leave it running in a screen/tmux session and come back a day or two later to not just see that there had been some instances of high latency or packet loss but also see when it happened and for now long per burst.<p>With all the existing tools I'm aware of I can come back to a long-running ping after a day or two and see that there were 170 pings that got lost but have no idea if that was individual intermittent drops or one continuous event like a cable modem rebooting in the middle of the night.<p>A couple of times I've attempted to do it myself but the nature of ICMP means it ends up requiring lower level programming than I'm comfortable with.
Random question, but how consistent should you expect to get pings to be over consumer internet to something like google? Single-digit ms variance? Few ms? 10's of ms? Always kind of curious for trying to optimize my network setup at home.