This is why you should use FOSS as much as possible. So what if digital ocean shuts you down? You have a backed up copy at least once a day of your data at least once a day on off premises backup, right? You just move to another provider and make sure to tweet and HN about how awful DO (or whoever is) so they lose customers and your company keeps moving alone with a 1 day outage.
This is concerning. We were considering a move to DO from Huroku to save quite a few $, but I’m thinking AWS now. I dislike the convoluted mess of a UI that AWS presents, but this happening would be way worse.
I use AWS for a hobby project. It just costs a couple of Euros a month. I am in EU and according to PSD2 every payment would need strong authentication. AWS warns about this but my bank has never required it. I always fear some day they will require the authentication and just these days I will be late with checking mails/accounts, wherever this will turn up and I will notice only when AWS has shut down my server and deleted my data.
I would happily make a 20 or 50 EUR/USD payment in advance to avoid the risk. But AWS is not flexible enough to allow me to do so. I understand in some countries it's possible, but in EU there are no options.
I always wondered how AWS/Amazon got away without the strong authentication. It turned out that they don't anymore in my case:
Your card payment ending in XXXX failed when we attempted to charge it for AWS services on account YYYYYYYYYYYY because it requires additional authentication. To complete the payment, please complete your credit card authentication.
Expect an e-mail with subject "Action required – Your AWS account is past due" if you haven't gone through the authentication process for your card.
Luckily they were pretty noisy about it. I received the first mail about it on Dec 2nd and then reminders on Dec 6th, 9th and 13th. At this point I noticed it and made the payment. They didn't shut down any service meanwhile.
It appears to me that they are prepared because they warn about it. But my bank does not follow the rules so the payment goes through without strong authentication.
Good to know that they warn at least 10 days. If that is constant and not dependent on some algorithm. I could not find any information how fast they stop your server and whether data would get locked first or deleted immediately.
I’m in a similar position at the moment and I’d suggest if you were considering DO, to take a look at Vultr and UpCloud.
I’ve found support response time from both so far to be excellent (UpCloud in particular though their feature set is just slightly behind Vultr and DO currently).
I had been testing the water with DO with a view to hosting some production stuff with them, but I’ve seen a few too many similar stories like this one and decided to get out of DO and rule them out for production stuff for now. Many of their direct competitors seem to provide much better support at lower levels of spend too.
Comments
Something like this has happened before:
DigitalOcean Killed Our Company: https://news.ycombinator.com/item?id=20064169
Something like this was reported 8 hours ago[0] I find myself suspicious of this sudden negative press
[0]: https://news.ycombinator.com/item?id=29596138
This is why you should use FOSS as much as possible. So what if digital ocean shuts you down? You have a backed up copy at least once a day of your data at least once a day on off premises backup, right? You just move to another provider and make sure to tweet and HN about how awful DO (or whoever is) so they lose customers and your company keeps moving alone with a 1 day outage.
This is concerning. We were considering a move to DO from Huroku to save quite a few $, but I’m thinking AWS now. I dislike the convoluted mess of a UI that AWS presents, but this happening would be way worse.
I use AWS for a hobby project. It just costs a couple of Euros a month. I am in EU and according to PSD2 every payment would need strong authentication. AWS warns about this but my bank has never required it. I always fear some day they will require the authentication and just these days I will be late with checking mails/accounts, wherever this will turn up and I will notice only when AWS has shut down my server and deleted my data.
I would happily make a 20 or 50 EUR/USD payment in advance to avoid the risk. But AWS is not flexible enough to allow me to do so. I understand in some countries it's possible, but in EU there are no options.
I always wondered how AWS/Amazon got away without the strong authentication. It turned out that they don't anymore in my case:
Expect an e-mail with subject "Action required – Your AWS account is past due" if you haven't gone through the authentication process for your card.
Luckily they were pretty noisy about it. I received the first mail about it on Dec 2nd and then reminders on Dec 6th, 9th and 13th. At this point I noticed it and made the payment. They didn't shut down any service meanwhile.
It appears to me that they are prepared because they warn about it. But my bank does not follow the rules so the payment goes through without strong authentication.
Good to know that they warn at least 10 days. If that is constant and not dependent on some algorithm. I could not find any information how fast they stop your server and whether data would get locked first or deleted immediately.
I’m in a similar position at the moment and I’d suggest if you were considering DO, to take a look at Vultr and UpCloud.
I’ve found support response time from both so far to be excellent (UpCloud in particular though their feature set is just slightly behind Vultr and DO currently).
I had been testing the water with DO with a view to hosting some production stuff with them, but I’ve seen a few too many similar stories like this one and decided to get out of DO and rule them out for production stuff for now. Many of their direct competitors seem to provide much better support at lower levels of spend too.