I'm in birmingham.
i just tried pinging bbc.co.uk for 30 mins and had the following results which don't look anywhere near as bad as yours but I know i definatley have a problem somewhere
Ping statistics for 212.58.224.82:
Packets: Sent = 1639, Received = 1620, Lost = 19 (1% loss),
Approximate round trip times in milli-seconds:
Minimum = 17ms, Maximum = 487ms, Average = 20ms
I have a screenshot what pages can look like when they don't display properly which i'll post up soon
---------- Post added at 23:09 ---------- Previous post was at 23:05 ----------
this is what a web page can look like for me at it's worst. if i refresh it will come up ok!
this was tomtom.com
http://www.ish.pwp.blueyonder.co.uk/web.doc
---------- Post added at 23:12 ---------- Previous post was at 23:09 ----------
and downloading that .doc back from my webspace it looks like this for me now
http://www.ish.pwp.blueyonder.co.uk/web2.jpg
(THE ABOVE 2 PICS SHOULD BE DIFFERENT?)
---------- Post added at 23:25 ---------- Previous post was at 23:12 ----------
here is a tracert to blueyonder.co.uk
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\Documents and Settings\Ish>tracert
www.blueyonder.co.uk
Tracing route to
www.blueyonder.co.uk [62.30.31.86]
over a maximum of 30 hops:
1 1 ms 2 ms 1 ms 192.168.123.254
2 8 ms 14 ms 8 ms 10.63.248.1
3 9 ms 7 ms 8 ms gsr01-sm.blueyonder.co.uk [62.30.193.129]
4 14 ms 15 ms 13 ms pc-62-30-247-53-do.blueyonder.co.uk [62.30.247.5
3]
5 21 ms 12 ms 12 ms pc-62-30-247-2-do.blueyonder.co.uk [62.30.247.2]
6 13 ms 12 ms 14 ms brad-wit-pos.telewest.net [194.117.136.22]
7 13 ms 13 ms 14 ms 194.117.136.153
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 ^C