[Luke Gibson]

Thanks for the info James. The reason that I was thinking it may be more of a 'traffic routing' problem through the NTL network is due to the fact that my HTTP browsing is working as expected. I appreciate that I shouldn't have to use a different webcache server but when I do it does work 'normally' (within the defined speeds of an expected 2Mb link).

So I can only assume that the physical links are fine and that it is something within the configs of specific customers setups. Either by our IP's being allocated addresses that route a certain 'wrong way', or by some local exchange being down and our traffic having to 'go around the houses' (excuse the pun) before reaching some local NTL server?

I understand some of the routing/cabling issues that can occur, but you may have more knowledge on the subject than me.

Oh, by the way. When I spoke to NTL earlier in the week the guy told me that they had (for some reason) set the config file on my 2Mb connection to be 56K!! So in addition to the problems with cables/traffic, you may wish to have your modem speed confirmed by NTL TS.

Best regards to all,

Luke