Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Multiple Digital Ocean services down

status.digitalocean.com

Post reply on HN
Print view View original

11–20 of 46 posts

Re: Multiple Digital Ocean services down

#12

Post by matt-p »

potato3732842 wrote: post #8
matt-p wrote: post #6

Earlier quoted context omitted.

Just spaces CDN, not spaces - you'd think they'd just turn the CDN off for a bit.

You can't just "turn off CDN" on the modern internet. You'd instantly DDOS your customers' origins. They're not provisioned to handle it, and even if they were the size of the pipe going to them isn't. The modern internet is built around the expectation that everything is distributed via CDN. Some more "traditional" websites would probably be fine.

If you are DO you could, you just decided not to bother. They control the origins it's spaces (s3), so they could absolutely spin up further gateways or a cache layer and then turn the CDN off.

Re: Multiple Digital Ocean services down

#16

Post by sgc »

hshdhdhj4444 wrote: post #5
archerx wrote: post #4

I have two projects on DO using droplets and they are still running fine.

It seems mostly a CludFlare related issue. My DOs are working fine as well.

Are you using their "reserved IPs"? I was thinking of starting to use them, but now I wonder if it is part of their load balancing stack under the hood.

Re: Multiple Digital Ocean services down

#18

Post by Lammy »

zx8080 wrote: post #13
giancarlostoro wrote: post #9

So yesterday Azure got hit hard, today CF and DO are down, bad week or something else?

Year-end promotion cycle is the worst time for end-users and the best one for engineers greedy for promotions.

Don't blame individual engineers who want to do what will be rewarded instead of company performance policies that reward this type of behavior.

Re: Multiple Digital Ocean services down

#20

Post by wesammikhail »

showerst wrote: post #10

I use DO's load balancers in a couple of projects, and they don't list Cloudflare as an upstream dependency anywhere that I've seen. It's so frustrating to think you're clear of a service then find out that you're actually in their blast radius too through no fault of your own.

slight off topic: I used DO LBs for a little while but found myself moving away from that toward a small droplet with haproxy or nginx setup. Worked much better for me personally!
Post reply on HN