If they are providing essentially a bare machine or VPS, then clearly they shouldn't have editorial control over your blog that happens to be hosted on the hardware. But when it gets to more managed services I think the issue is blurred.
- Scenario 1: hire a VPS, set up a mail server on it, send emails that your host doesn't want you sending. - I'd say there's nothing they should be able to do here. - Scenario 2: using a scalable email service (like Amazon SES?) to send emails that the host doesn't like. - I'm much less sure about this.
So basicly the only reasons a hosting provider should have grounds to terminate/interfere with service are - court order/stopped payment/the way service is used actively disrupts other customers.
We should have service "first sale doctrine" equivalent - once you have sold the access service etc you have no say in how it is used.
There is obviously an increased risk if many layers claim the right to interfere. E.g. SAAS operated on Heroku running on Amazon gives at least three parties ability to interfere (or just have downtime/issues).
In this case however there was only one party Digital Ocean who operate the data centre and provided the service so I'm not sure it matters that they are a 'cloud' service rather than offering traditional hosting or a colocation service. That said I think that DO got this decision badly wrong.
I think that cloud services and telecoms and ISPs should be designated as common carrier with the protections and obligations that come from that.