Looks like whoever runs MiamiHawkTalk needs to do some b****in' .... it took me SEVEN tries, but I finally got a traceroute to work:
gts # traceroute
http://www.miamihawktalk.com
traceroute to jag.opensourcehost.com (69.93.35.100), 30 hops max, 40 byte packets
1 * * 10.129.0.1 (10.129.0.1) 32.723 ms
2 172.22.32.242 (172.22.32.242) 12.716 ms 11.506 ms 27.456 ms
3 172.22.32.194 (172.22.32.194) 10.164 ms 10.317 ms 10.909 ms
4 12.125.220.73 (12.125.220.73) 12.723 ms 12.125.220.41 (12.125.220.41) 24.632 ms 12.125.220.73 (12.125.220.73) 12.520 ms
5 tbr2-p012301.attga.ip.att.net (12.123.149.5) 35.491 ms 35.157 ms 38.958 ms
6 12.122.2.89 (12.122.2.89) 31.392 ms 31.712 ms 32.302 ms
7 12.122.82.37 (12.122.82.37) 39.291 ms 32.126 ms 35.496 ms
8 * * *
9 vl31.dsr01.dllstx3.theplanet.com (70.85.127.29) 38.842 ms vl32.dsr02.dllstx3.theplanet.com (70.85.127.62) 38.965 ms vl32.dsr01.dllstx3.theplanet.com (70.85.127.61) 35.775 ms
10 vl21.dsr01.dllstx2.theplanet.com (70.85.127.67) 37.202 ms vl22.dsr02.dllstx2.theplanet.com (70.85.127.76) 37.851 ms 42.839 ms
11 vl1.car12.dllstx2.theplanet.com (12.96.160.17) 38.584 ms 35.038 ms 39.069 ms
12 jag.opensourcehost.com (69.93.35.100) 42.762 ms 41.194 ms 36.306 ms
Looks like the jump from their datacenter to the outside world is really being hammered or is really flaky one. That sort of latency explains why every time I tried to access it I got time out errors.