[invisiblea]

I use DO for several one or two box production sites (LEMP and RoR stacks), and have minimal complaints. I'm a big fan of scaling up the CPU without having to also increase HD size (which is a Linode requirement).

The biggest issue we've faced was their use of Google DNS. A couple of months back, Google DNS had an outage, and all our calls to external services semi-silently failed. Because this wasn't technically a DO service outage, it wasn't reported by them, and because we didn't know they used Google DNS we didn't trace the issue to the outage. We could have done more, but they could have also been more transparent.

Overall, we are starting to move more projects to DO from Linode, because I feel Linode's previously excellent support has slipped dramatically (customer for at least eight years). We also leverage a lot of AWS services (particularly S3 and SES).

[iDemonix]

What have you done to mitigate the DNS risk?

[stevekemp]

Simplest thing there is to split zones across two providers - e.g. Route53 + DNS Made Easy, etc.

(DO do have their own DNS API, but it is terrible to program against.)