rzeznikj@linux:~> ping -c 5 209.157.64.200
PING 209.157.64.200 (209.157.64.200) 56(84) bytes of data. 64 bytes from 209.157.64.200: icmp_seq=1 ttl=51 time=73.8 ms 64 bytes from 209.157.64.200: icmp_seq=2 ttl=51 time=74.5 ms 64 bytes from 209.157.64.200: icmp_seq=3 ttl=51 time=74.9 ms 64 bytes from 209.157.64.200: icmp_seq=4 ttl=51 time=74.0 ms 64 bytes from 209.157.64.200: icmp_seq=5 ttl=51 time=73.8 ms
--- 209.157.64.200 ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 3999ms rtt min/avg/max/mdev = 73.849/74.253/74.911/0.416 ms
Knowing that the time for an average site when functioning normally from my computer is roughly 70-80ms, I could tell there was something there--but why we were down, I have no clue.
Yet, neither Firefox, nor Konqueror, nor Internet Explorer (run through WINE) could load the site.
It's a lil trick I learned when I ran Slackware Linux 10.1 last summer.
Um. Little too technical for my peroxide level, but I think I git what you're saying.