Hosting pain... painful memories recounted... Or How EZOShosting blows?

As you all might be aware, Brandi and I have a few web sites, some aren't live yet and other are. Well, about a month ago we moved the biggest of our sites TexasUnwrapped.com to a new server and hosting provider due to some poor performance and more appropriate some poor support.

After being online with TexasUnwrapped.com for a few months and implementing a new look and feel. We started to experience times when the site would be choke to death. Our PHP pages won't pull up at all and HTML would crawl to the screen if displayed at all. Brandi contacted the hosting provider through trouble ticket system and received a 'we don't see any issues' response. Being a busy guy, I didn't have time for the first week to get involved in the process, but day after day the site would choke and Brandi would attempt to get help. Sometimes they would restart the services or the server, but continued to claim they didn't have any issues.

Well, after Brandi explained the nonsense and her concerns over the problems, I took sometime to try and work the issue out. I started slowly by working with support on her trouble ticket. I asked if they could figure out the root cause of the performance issues that we were experiencing... my question was never responded to. After another outage, I figured I needed to pick up the pace. I thought that I might be able to reach tech support via the phone and a well placed call to sales, but the automated voice response hell offered no hope of real human interaction. Once again took to the trouble ticket with a demand for assistance, (ticket below) this time I was a bit more forceful indicating that the support provided was on worse then if I ran the server in my own house (I know nothing about Linux so my support would suck, but at least Brandi could turn it off and on during the day when problems occurred). I also contacted a friend with PHP and MySQL experience to discuss moving to another provider. With my friends encouragement and ezoshostings silence, I got space on another providers server and began to move the site.

Thirty-Six hours later, I was completing the DNS change for the new site and we finally received a response from ezoshosting. It seems all our issues were caused by a new spam filter they deployed. Glad to see that they were able to isolate the cause of the issue based on the recent changes they made. I wonder why I ask users when they complain about a problem if they installed something recently. Unbelievable... Frustration.... The good news is I learned a new skill and we won't have to deal with the company that hosts sites out of their basement.