I have a process on my web host that runs every hour and uses the database, so I get email whenever the database is unavailable. Every four or five months, DreamHost has an unannounced database outage, often for many hours. By count of the emails I received, the outage earlier this week lasted over 11 hours. Every time this happens, I fret for days about changing web hosts, only to be stalled by the cost of doing so, and then my interest fades until the next outage.
I have a hard time knocking DreamHost, because they're otherwise pretty stellar and deserving of their loyal following. Their prices are good, their automated features are many and powerful, and their customer service blows me away. I've sent several people to DreamHost based on these qualities, including a policy I renew every year for my mother for Mother's Day, and a high-traffic (high-paying) non-profit organization. But unannounced hours-long database outages are inexcusably unprofessional. To think that they hope to cater to small businesses.
It is pretty clear from previous outages that it isn't a matter of a poor planned outage notification policy. They just lose control of their database systems every once in a while, and have to scramble to get them restored. I remember one outage left me with corrupt tables and resulted in lost data. DreamHost has been struggling to figure out what a high-end web host looks like on the back-end, with high traffic or poorly written software installed by customers capable of affecting other customers. Their solution to the database problem: bill per database connection, and per query (the charge calculated from a combined number they call "conuery"). I don't know of any other web host that meters database usage like this. (Do you?)
Any anti-DreamHost thread deserves a mention of Pair.com, which has competitive prices and features, and is especially known for their reliability, size and industry experience. Nobody has ever complained about Pair, and they're always overwhelmingly mentioned in "what's a good web host?" discussions.
I'm also seriously considering self-hosting over my DSL line. I worry about this option because I don't understand my usage patterns well enough to know what the line can handle, and it will inevitably be less reliable than any web host. If my server goes down, not only would I be without access to email, but emails sent to me would bounce. If I'm on vacation when it happens, there's nobody to fix it until I get back. But I'm already paying for the static IPs, I have the know-how and the hardware, and I'd enjoy the control provided by self-hosting.
I'm hardly the first to complain about or leave DreamHost because of egregious quality control problems, but I may be the next.
I just upgraded my DSL to Speakeasy's 1.5/768 plan, and intend to bring my hosting in-house. It's my understanding that your mail won't start bouncing for some time if your server goes down; as long as there's a mail server defined in your DNS, hosts that are sending you mail will let it queue up until your host is back online -- up to several days depending on the host.
It is important that you get a lot of redundancy for your DNS, but luckily this is cheap/free (see Granite Canyon's Public DNS, MyDomains.com, etc.).