It's always a shame to loose faith in your hosting provider but, after four months of trouble with this site I've left streamline.net for a different company, and one that specialises in ASP.Net hosting.
The problem seemed to center around using the .Net Framework on a sub domain, as there were never any problems having used it on a main domain. Around the start of this year I started getting a 'Server is too busy' message on this domain, so I would log a support ticket. Mysteriously each time I do this (there's an up to 48 hour, working day only, potential wait on any tickets) the site started working again a few hours before they would replay "We have tested blog.grahamlicence.co.uk and the site appears to be operating without issue. Similarly there have been no reported technical issues on the server hosting the domain".
This happened a few times so they asked for some details about the site to investigate. I didn't hear from them again for a month. After repeatedly following up the support ticket I was told my "issue requires further investigation by our engineers" after which I was told "that the issue has now been resolved". A few weeks later the site went down again, giving the IIS error 'Server is too busy'.
To add insult to injury I was then told "to clear or delete the browsing history of your web browser and check it again?" Which is clearly not how you reslove an IIS problem, especially as you have barely any control over IIS with them. No ability to add custom errors, view logs or allocate more resources to the machine hosting the site. Clearly another site was eating the CPU (traffic here is fairly low) and killing my site. Shouldn't this be easy for Streamline to fix? Clearly not.
Streamline.net are a staggerinly bad hosting company
Not my words but a reflection of the large number of very bad reviews on streamlinereviews.wordpress.com/reviews/

This was confirmed when another sub domain with the .Net Framework added stopped working because the application had clearly been disabled - a fairly strange thing to happen, especially when your paying good money for the service, luckily this was resolved fairly quickly.
On the 26th April this site went down again, really badly. There was no IIS error or any actualy connection, the domain just timed out. Two whole days of outage and, having to bite the bullet a little on losing what I've paid, I left Streamline.net for pastures new. If only the leaving process was straight forward.
28/4
Submitted support ticket to cancel hosting and add ons for my domains. As with all support tickets response should be within 48 hours.
3/5
Added follow up ticket as hadn't yet heard back.
6/5
Added another reply to original ticket as more than a week had passed before hearing anything. Also asked for explanation of their delay in replying.
10/5
First reply from Streamline. They added that each time I reply to a ticket it moves it back down the support ticket queue. Apart from being a ridiculous approach to support tickets this doesn't explain why it took so long to get back to me.
Replied same day to confirm backups had been made.
16/5
After 6 days with no response sent a follow up reply asking for confirmation of cancellation.
17/5
Cancellation confirmed. 29 days after support ticket opened.
There is clearly some significant organisational issues at Streamline for what is essentially a simple process to take so long to complete.
Things to bear in mind when leaving Streamline.net
-
There will be a long delay in replies to support tickets
-
Cancellation will only occur once they have started the process and have read your reply that you have made backups of all sites. It seems this delay tactic is a way of forcing people to pay when trying to cancel during a free trial. Contact trading standards and your credit card company if this happens to you
-
Cancel your card that is attached to your account to prevent payments during cancellation process. From what I understand by reading other people's experiences you won't be refunded if any payments are taken after you submit your cancellation request.