Yep, well and truly gone crazy. I did another traceroute and ping which will be of more use.
code:
20:06PM | 29 May 2005
ping msghelp.net
Pinging msghelp.net [64.62.180.102] with 32 bytes of data:
Reply from 64.62.180.102: bytes=32 time=231ms TTL=58
Request timed out.
Reply from 64.62.180.102: bytes=32 time=230ms TTL=58
Request timed out.
Ping statistics for 64.62.180.102:
    Packets: Sent = 4, Received = 2, Lost = 2 (50% loss),
Approximate round trip times in milli-seconds:
    Minimum = 230ms, Maximum = 231ms, Average = 230ms
tracert msghelp.net
Tracing route to msghelp.net [64.62.180.102]
over a maximum of 30 hops:
  1    22 ms    21 ms    23 ms  loopback1.ar2.gs1.systems.pipex.net [62.241.161.
244]
  2    22 ms    21 ms    21 ms  ge-2-0-0.cr1.gs1.systems.pipex.net [62.241.161.1
02]
  3    21 ms    21 ms    21 ms  xp-ix.lon.he.net [217.79.160.99]
  4   164 ms   161 ms   163 ms  pos8-0.gsr12416.nyc.he.net [216.218.200.101]
  5   231 ms   230 ms   230 ms  pos7-0.gsr12012.sjc.he.net [216.218.254.153]
  6   230 ms   230 ms   230 ms  pos1-2.gsr12416.fmt.he.net [64.71.128.182]
  7   234 ms   234 ms   232 ms  64.62.180.102
Trace complete.