MySQL is conspicuously absent from their uptime metrics. In fact, the status page only says this right now:
"System uptime stats currently offline (how ironic!)."
Before you assume the problem is on my end (it wasn't, and MySQL works fine now, but as long as we're having this discussion, I'll bite.....) I should point out that the host was completely dead. Couldn't ping it from my machine, couldn't ping it from my dreamhost shell. That's pretty conclusive. It couldn't have been a data corruption problem, because I hadn't had the opportunity to PUT any data in it in the first place!
I know this isn't an official board, I don't expect them to read or reply to anything here. My comment was directly in response to your statement that their absence was indicative of anything. It isn't. They could be hard at work fixing the problem, they could be drinking martinis in Aruba, or they could be trying to find their way out of David Bowie's Labyrinth. But to say that their absence and the sizable support queue is evidence that they're hard at work (and not incompetent) is indeed twisting things to make them look better (or at least, less bad) despite what you say.
I stand by my dismissal of the support contact page. The number of open support requests has only gotten LARGER since I've registered. It's at 200 now. Assuming 5 minutes to deal with each issue and send a response (that's being generous, I feel), working nonstop, that's a sixteen hour best-case response time if I file my request RIGHT NOW.
It's pretty presumptuous to insinuate that the errors I'm seeing are from my own lack of knowledge. Instead of trying to convince you otherwise, however, I'll just state that the errors (both MySQL inaccessibility and bad_httpd_conf) I've seen have BOTH happened simply by adding the service to my account using the control panel. Both services immediately failed to work. I never even had a chance to break them with my lack of knowledge.
At this point I'm not complaining about a specific problem. I know that's not going to do any good here. I am defending my overall impression of Dreamhost from your criticisms. Despite what you say, you are obviously not the "first one to admit when something's not going well" and you really are covering for Dreamhost.
I'm expecting them to be superman? No, I'm expecting that things work more than 50% of the time when I use their control panel. I'm expecting that when I add a MySQL service, it doesn't tell me to connect to an IP that doesn't respond to pings for 24 hours. I'm expecting that when I add a new subdomain, the damn thing doesn't come up with a fatal error in the browser right off the bat.