Liquidweb Woes

My company went with Liquidweb over 3 years ago on the strength of positive recommendations given in this forum. For the most part things have been good, but service and quality have visibly deteriorated in the last few months, and I feel that the community should know. Here are a few examples:

1) We ordered a new dedicated database server from Liquidweb. It started crashing randomly, requiring a full system reboot. The only software we were running on this server was Postgres, which doesn't typically halt linux systems. The first time it crashed we chalked it up to a fluke. The techs at Liquidweb said it was probably "due to serverload", even though this server wasn't heavily stressed at all.

A few weeks later it crashed again. I talked to a Liquidweb tech and he said there were some weird hard drive related messages on the terminal in the datacenter. He said he would have a systems restore "specialist" look into it. This was at 3AM in the morning. The next morning, the server was back up, but we wanted an explanation for the down time. Another Liquidweb tech put us in touch with a systems restore specialist, who said that "we don't know went wrong. the error seems so sporadic that we cannot debug it without an error message." I asked him what happened to the error messages that were on screen the previous night. He said that someone had reboot the system without taking note of the error messages! So basically, his attitude was to wait for it to crash again, rather than proactively try to solve the problem!

I grew frustrated with them and asked him to run an HD scan to check the integrity of the disk. He said that they didn't really have any tools to do that except for one, and seemed reluctant to run it. I told him to do it anyway. It turned up massive failures with the integrity of the hard disk (on this, our brand new server). The fact that I had to basically tell him how to do his job to get our server back running was not the kind of service we were paying for.

2. This morning. For no reason, one of our webservers was unable to contact any of the internal servers in our network, resulting in downtime. I called a specialist at Liquidweb. He didn't know what was going on. I asked him to check the network cables, because the servers were still accessible via their remote ips, just not on the internal ones. He went down to the server room and said that the network cable from our webserver to the switch was simply unplugged. I don't even know how that could have happened, given the fact that it had been working fine for months, and we hadn't had any changes of hardware. Don't these cables snap in with a clip? Can someone explain to me how that is possible short of someone tripping over the wire, then failing to put it back in?

3. Now. The Liquidweb network has been down for an hour. Completely down, inaccessible. This must affect hundreds of sites. The explanation, given on the support page (liquidweb.com/support), is:

"We are currently experiencing latency and packet loss affecting portions of our network. Our network engineers are currently working on the issue and we will update this page as more information is available."

It doesn't seem like a latency or packetloss issue. It's a connectivity issue. Their network is down. Their Dedicated SLA guarantees 100% uptime. I'm not a network expert, but this would seem to imply some redundancy or failover. Which should prevent this currently impossible situation from happening.

We have multiple servers with them, and are currently spending thousands of dollars each month. Given that Liquidweb is more expensive than many other alternatives, a material portion of our monthly fees go towards that unseen "premium" of quality service and quality technology that now seems to be rapidly falling.