Fasthosts

The past few weeks SEO Creative have been re designing some websites for clients, normally this isn't a big issue and it all runs quite smoothly but 2 of our clients had previously been on Fasthosts servers.

We haven't used Fasthosts for over 18 months as the servers were very slow and they prevented the use of htaccess files meaning that 301 redirects and SEO friendly permalinks were impossible. This is a fundamental functionality. This combined with no proper cpanel meant second rate sites with problems with re designs.

Having lost the will to live after various issues with fasthosts I eventually closed all accounts down and moved everything to another server. We have had no problems with any servers we use now and forgot about our previous issues with fasthosts.... until now!

We tried to rebuild the sites using the current servers but it was clear once the new site went live there were going to be 404 errors all over the place and without htaccess we couldn't 301 redirect them. We decided to move the sites to our own servers but even that was an issue.

I could go on for ages about the technical problems we were having but what really annoyed me was the customer service. Trying to close the accounts you have to ring a premium number give them account details and tell them the problem. Instead of sorting the account however they always say we will get someone to call you back.

After 4 days waiting for a call back and another call to customer service I ranted on my Twitter page. I was quite pleased when Fasthosts Twitter account got back to me. It was an unorthodox way of working but they fixed the first problem quickly.

However the second site we went through the same issue, we called up and were told that this elusive customer service team would call us back... this is now 5 days ago.

I suggested using the Twitter method and 3 days ago tweeted them - nothing....

I have tweeted them again but not a peep from Fasthosts. In the mean time we have a client very angry at us that we can't sort this problem out.

Word to anyone considering using fasthosts- DON'T - Just Don't!