Marco.org

I’m on a plane above Kentucky. This is Virgin America’s in-flight Gogo WiFi. It’s a very odd connection.

PING google.com (74.125.45.100): 56 data bytes
64 bytes from 74.125.45.100: icmp_seq=2 ttl=48 time=120.305 ms
64 bytes from 74.125.45.100: icmp_seq=7 ttl=48 time=180.299 ms
64 bytes from 74.125.45.100: icmp_seq=12 ttl=48 time=125.548 ms
64 bytes from 74.125.45.100: icmp_seq=17 ttl=48 time=94.383 ms
64 bytes from 74.125.45.100: icmp_seq=22 ttl=48 time=87.972 ms
64 bytes from 74.125.45.100: icmp_seq=27 ttl=48 time=118.603 ms
64 bytes from 74.125.45.100: icmp_seq=32 ttl=48 time=99.986 ms
64 bytes from 74.125.45.100: icmp_seq=37 ttl=48 time=98.320 ms
64 bytes from 74.125.45.100: icmp_seq=42 ttl=48 time=99.449 ms
64 bytes from 74.125.45.100: icmp_seq=47 ttl=48 time=83.807 ms
^C
--- google.com ping statistics ---
48 packets transmitted, 10 packets received, 79% packet loss
round-trip min/avg/max/stddev = 83.807/110.867/180.299/26.683 ms

It’s much more usable than ping would have you believe. I’m guessing they do a lot of packet shaping.