I feel obligated to chime in on hostingx. Its been up and down over the last week more times than I can remember. I wonder where and how it arrived at its 99% uptime statistic. I didn't think its possible, but so far, its even worse than Ripplehost!! They even lost the account information, so some users, myself included, had to email them a new password for the control panel and email. And this is just my first few weeks with them. Perhaps you really need to pay more for a reliable host, who knows.
There are a few customers experiencing problems on one server. We did NOT "lose account information" - we emailed all the customers on that server and told them that the httpd.conf file had become corrupted along with the cPanel password files.
There was nothing we could have done to prevent this from happening but we are trying our best to fix this problem.
Up until now as stated before our servers kept a steady and true 99% uptime and we should expect that to resume in the near future.
Originally posted by spikez202
There are a few customers experiencing problems on one server. We did NOT "lose account information"
Thanks for posting here! I wasn't really concerned so much about the httpd.conf corruption issue, and I don't think the other post meant to imply that information was lost other than having to reset the cPanel passwords. (You are right to clarify that.)
Can you shed any light on the outage this morning? That seems to be a separate issue -- I couldn't reach hostingx.net, my domain. Couldn't get a ping response from the primary nameserver (I did not try the secondary). It's possible that there was a breakdown somewhere along the line, I guess, although I could reach everything else I tried.
It would be really nice if hostingx.net had a forum of some kind where explanatory info could be posted for your customers. (hint, hint)
Thanks, spikez202, for taking the time to post some info on the server problem. Hope that gets cleared up fast! I'm actually a relatively new customer of yours, but I didn't get an email about this latest problem. (I did get 3 emails about the httpd.conf problem, though!)