I've noticed this sort of growing on a day to day basis.
This is the worst I've seen it though,

6 16 ms 13 ms 19 ms dalsbprj02-ae2.0.rd.dl.cox.net <68.1.1.243>
7 14 ms 14 ms 14 ms po21.bbr02.eq01.dal01.networklayer.com <66.109.9[br/>.222]
8 14 ms 14 ms 15 ms po6.dar01.sr01.dal01.networklayer.com <173.192.1[br/>8.211]
9 16 ms 18 ms 18 ms po1.fcr04.sr05.dal01.networklayer.com <66.228.11[br/>8.214]
10 463 ms 427 ms 441 ms srv01sldaltx.thirdhosting.com <67.228.169.82>
11 205 ms 220 ms 222 ms riverwind.thirdhosting.com <208.43.220.232>

Almost a full second! These servers are in dallas I think too!

Is this just me? Or is thirdhosting really having issues?

For comparison...


tcptraceroute carrionfields.net 9994
traceroute to carrionfields.net (208.43.220.232), 30 hops max,
40 byte packets
 1  wall (192.168.1.254)  0.154 ms  0.153 ms  0.161 ms
 2  se3-l0.milwwi.sbcglobal.net (65.43.19.93)  79.410 ms 
79.689 ms  79.694 ms
 3  dist2-vlan60.milwwi.ameritech.net (65.43.19.243)  79.861
ms  80.157 ms  80.230 ms
 4  151.164.190.132 (151.164.190.132)  80.235 ms  80.573 ms *
 5  * * *
 6  * * *
 7  * * *
 8  * * *
 9  * srv01sldaltx.thirdhosting.com (67.228.169.82)  160.930
ms  174.357 ms
10  riverwind.thirdhosting.com (208.43.220.232)  174.610 ms 
174.612 ms  76.427 ms


ping -c 5 carrionfields.net
PING carrionfields.net (208.43.220.232) 56(84) bytes of data.
64 bytes from riverwind.thirdhosting.com (208.43.220.232):
icmp_seq=1 ttl=50 time=37.0 ms
64 bytes from riverwind.thirdhosting.com (208.43.220.232):
icmp_seq=2 ttl=50 time=36.7 ms
64 bytes from riverwind.thirdhosting.com (208.43.220.232):
icmp_seq=3 ttl=50 time=35.9 ms
64 bytes from riverwind.thirdhosting.com (208.43.220.232):
icmp_seq=4 ttl=50 time=47.6 ms
64 bytes from riverwind.thirdhosting.com (208.43.220.232):
icmp_seq=5 ttl=50 time=48.4 ms

--- carrionfields.net ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 4015ms
rtt min/avg/max/mdev = 35.989/41.174/48.419/5.620 ms