201–210 of 620 posts
Earlier quoted context omitted.
Any that suspects fraud and doesn't want to be on the hook for the inevitable chargeback.
Caps or quotas are a better way to achieve this IMO. Random shutdowns do not make it sound as if DO is ready for production.
Caps or quotas are not sufficient to deal with this problem.
Who is good about not locking accounts or taking similar actions? Apple and Google are both notorious for blocking things for no reason, is AWS or Azure any better?
https://qbix.com/platform is one of many projects working to tackle this. Tim Berners-Lee’s SOLID project and others are, also.
Soooo... an automated script flagged them. they get themselves unflagged, and proceed to do the same thing immediately. without any real confirmation that they wouldn't be flagged again. They've basically been flagged as abusing the system multiple times, and they're surprised they had to kick up a storm to get themselves reactivated again? Not to mention, that process they need to run every couple of months, that ta…
Just a guess.
I think, going forward, a data backup is not going to be enough. You’ll need a full devops plan b/c where you just redeploy to another hosting provider. Even better: run your infrastructure across multiple hosting providers with something like consul. DO might cause slower service but not a death sentence.
Earlier quoted context omitted.
If you get DDOS'd they will stick your VMs in a black hole until the traffic stops to protect their network, no matter how much you plead with them. Good practice, actually, but it's something people usually get frustrated with and they're literally famous for doing it.
That's not true, OVH is one of the few ISPs with an actual free DDoS protection.
Some people on HN hate Linode because of their past security screwups (which is valid), but having used both DO and Linode quite a lot, the support on Linode is way, way, way better than DO's. DO's tier 1 support is almost useless. I set up a new account with them recently for a droplet that needed to be well separated from the rest of my infrastructure, and ran into a confusing error message that was preventing it f…
I've been on Linode for 8+ years now (moved there from Slicehost when Rackspace swallowed them up) and their service (not necessarily customer support) has significantly degraded. Not sure I blame them though. They've become far more popular since I started with them and are probably doing their best to grow... but I no longer recommend them as I used to. Just my experience though.
Some people on HN hate Linode because of their past security screwups (which is valid), but having used both DO and Linode quite a lot, the support on Linode is way, way, way better than DO's. DO's tier 1 support is almost useless. I set up a new account with them recently for a droplet that needed to be well separated from the rest of my infrastructure, and ran into a confusing error message that was preventing it f…
Long-time Linode customer here. What were the security screwups? I tried a couple searches but didn't turn up anything.
A Bitcoin theft via the Linode Manager interface in 2012: https://news.ycombinator.com/item?id=3654110
and a second Linode Manager compromise in 2016: https://news.ycombinator.com/item?id=10845170
In both cases, if you dig into the context a bit, the story turned out that Linode wasn't fully disclosing the breaches to their customers until they were forced to do so when the news about them reached a certain volume. They also may have been -- almost certainly were -- dishonest about the extent of the damage and how it may have impacted their other customers.
At the time, their Manager interface was a ColdFusion application, which tends to be a big pile of bad juju. They started writing a new one from scratch after, I think, the second compromise.
The really bad thing here is that they got soundly spanked for being less than truthful the first time, and then four years later -- when they'd had ample time to learn from that mistake -- they did it again.
So there's a nonzero chance at any given time that Linode's infrastructure has been compromised and they know it and have decided not to tell you about it.
That's what prompted me to start exploring DigitalOcean more. Unfortunately, I've found that there's a far greater chance that I'll experience actual trouble exacerbated by poor support than that I'll be impacted by an upstream breach, so about half my stuff still lives on in Linode.
Some people on HN hate Linode because of their past security screwups (which is valid), but having used both DO and Linode quite a lot, the support on Linode is way, way, way better than DO's. DO's tier 1 support is almost useless. I set up a new account with them recently for a droplet that needed to be well separated from the rest of my infrastructure, and ran into a confusing error message that was preventing it f…
I have interviewed with DO and they tried diverting me towards a support position. They told me that on a single day a support engineer was supposed to help/advice customers on pretty much whatever the customer was having issue with and also handle something between 80-120 tickets per day. It's nice to see that DO is willing to help on pretty much anything they (read: their team) has knowledge about, but with 80-120…