It's more dramatic, and historically useful, to pipe the output from ping into Graphite, and keep a few months worth of data. Really shuts up the techs who come over and say everything's fine.
while [ "true" ]
do
printf 'google_ping %f %s' $(ping -c1 www.google.com | awk '/ms/ {print $7};' | awk -F '=' '{print $2};') $(date +%s) | nc graphite_host 2003
sleep 10
done ping -n www.google.com | awk '/ms/ {split($7,p,"="); print "ping.google " p[2] " " strftime("%s")}; fflush()' | nc -q0 127.0.0.1 2003 &I have a local VM with Routers2 installed, which pings our LAN router, the TW modem, the first TW hop, and one of our VMs at Linode. The latency spikes start at the first TW hop. Routers2 provides great insight in to how TW is performing.
You can get Routers2 here: http://www.steveshipway.org/software/