Hi, first post be gentle.
Post 34, gives some useful information to investigate the problem with the PingPlotter Pro attachment
Doing a traceroute to the same address I get the following
$ traceroute server25.teamhost.co.uk
traceroute to server25.teamhost.co.uk (85.234.155.53), 30 hops max, 40 byte packets
SNIP
3 cdif-t2cam1-a-v114.inet.ntl.com (62.254.255.161) 10.689 ms 10.498 ms 16.356 ms
4 cdif-t2core-a-ge-wan83.inet.ntl.com (195.182.175.201) 16.414 ms 16.634 ms 16.619 ms
5 bir-bb-a-so-730-0.inet.ntl.com (213.105.174.185) 24.846 ms 24.076 ms 24.496 ms
6 nth-bb-b-so-220-0.inet.ntl.com (62.253.185.85) 24.942 ms 13.790 ms 13.756 ms
7 tele-ic-1-as0-0.inet.ntl.com (62.253.184.2) 14.838 ms 17.738 ms 17.000 ms
8 212.250.14.90 (212.250.14.90) 17.800 ms 17.261 ms 20.811 ms
9 ge-5-2.the.uk.euroconnex.net (87.127.231.90) 123.588 ms 123.502 ms 122.814 ms
10 server25.teamhost.co.uk (85.234.155.53) 21.941 ms 18.887 ms 19.225 ms
$
Post 35, misses out the hops prior to hop 9, which would be useful to see the path it takes to get from a to b.
If each person posts a traceroute to the server they are having problems they can be compaired and see what the common hop is and that may be the one having the problem.