Host problem....? (transfer rate issues)

[Daytona]

Connecting to my host used to be really fast. Lately, it takes around 30 seconds to login and around 16 seconds to upload a single 3kb file. It takes another 16 seconds just to change directory up one level. To download a whole folder takes ages! The actual transfer time is fast. It just takes so much time to actually load a directory before the transfer takes place.
So far, to try to resolve the problem, I have -:
Checked for problems with broadband speed with my ISP - No problems (586K).
Performed a tracert (ping) check - Average 15ms =Ok
Performed a broadband speed test (upload/download) = Ok
Used a different FTP client - No change in results/speed (I knew Core was Ok)
Used a different computer on my network - No different
Complained to my host/web space provider - They say there is no problem their end at all and suggest I try a different FTP program (This I did - Of course = No change).
Other web sites hosted by the same host, also have the same problem.
I can connect to web sites with other hosts and experience no problems at all.
The only thing I have left to try, is to connect to the host from a different location. But as I say - my broadband connection is fine.

Any suggestions any one please?

[Daytona]

Thanks for your advice CP. I have connected to the FTP server from a different location today, just for the excersize of course and still it was just as slow. Even though that connection is 1 Megabit bandwidth.
And so, I have again written to the hosts asking them to quit denying their is a problem at their end and to try connecting via an external source themselves as you suggested. At least then they will see at first hand that there really is a problem.

I wouldn't mind so much, but I have 5 other web sites hosted with these people and they are all slow in FTP transfer from any location. I'll let the forum know how I get on when I recieve their latest response .

[Daytona]

Thanks again CP, but I am unable to provide a test account for you to try.
The latest problem occurred today, where I can't now fully upload a simple Html file. It uploads a part of it and then fails. Now the web site doesn't show the vital information that it should.

However, I have had a response from the host provider. Their response being -:

"The only thing I can do at this point is offer you a refund."

That is all very well, but now it means that to change host I'll need to transfer all the domains over. That may well involve transfer fees. Not to mention all the configuration changes to forms and email. However, firstly I'll need to find a good host with their own network and not a 3rd party provider such as the one I am with currently. If anyone has any recommendations, preferably in the UK, please let me know.

[Daytona]

It seems that the aforementioned problems may not necessarily be down to my hosting provider. Whilst I can connect to other hosts reasonably faster than the one I thought was at fault, I now find that files are only being partially uploaded (I'd show you a screenshot image if I could upload it!) to any host I connect to. Also, Core FTP seems to 'Hang' on certain files and once that has happened the rest of the files fail to upload (Message in Core FTP = Entering Passive Mode (212. When I then disconnect and reconnect, I can't re-establish a connection unless I reboot my PC (Message in Core FTP = Can't establish a connection [connect Socket 520, port 21]).

I reckon the answer to this problem lays in either my ISP connection, even though I can browse the Internet and get good Ping results or in Core FTP. My ISP's are going to send a cable engineer to me to check for 'noise' on the line. They remotely tested the cable connection downstream with good results. However the upstream from my modem gave poorer results, hence the need for an engineers visit. Is there any reason that Core FTP could actually be the culprit at all? (I did try others... similiar results). Any advice would certainly be appreciated.

I've got to the stage where I don't know which tree I should be barking at.... so I'm barking at both trees for the time being... woof, woof!