A few days ago I posted about this new tool from dslreports, which measured how your connection behaved under load.
Well this week I am in San Jose (Intel Network Builders, OPNFV, NFV World Congress: the trifecta!)
And here, from San Jose, you can pretty much spit and hit Mountain View (Google HQ, home of the original vanity-plate IP, 220.127.116.11). So, enjoying some particularly variable performance on the network here, i try a little ping action.
<pre>$ ping 18.104.22.168
PING 22.214.171.124 (126.96.36.199) 56(84) bytes of data.
64 bytes from 188.8.131.52: icmp_seq=1 ttl=56 time=5007 ms
64 bytes from 184.108.40.206: icmp_seq=2 ttl=56 time=5256 ms
64 bytes from 220.127.116.11: icmp_seq=3 ttl=56 time=5159 ms</pre>
Yes, 5+ seconds of latency. Without loss. This means that poor TCP things, hey, lets go faster, o no, no ack, slow down, o wait, got the packet, what do i do?
You have to blindfold yourself to use ssh over this.