Multiple Digital Ocean services down

3 hours ago (status.digitalocean.com)

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!

    • The point of an LB for these projects is to get away from a single point of failure, and I find configuring HA and setting up the networking and everything to be a pain point.

      These are all low-traffic projects so it's more cost effective to just throw on the smallest LB than spend the time setting it up myself.

They don't name names but it's probably due to the ongoing Cloudflare explosion. I know the DigitalOcean Spaces CDN is just Cloudflare under the hood.

  • 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.

      6 replies →

Yes all sites showing the CloudFlare error due to the massive outage. Seems their outages are getting more frequent and taking down the internet in new ways each time.

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.

      1 reply →

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

  • Droplets are fine.

    > This incident affects: API, App Platform (Global), Load Balancers (Global), and Spaces (Global).

  • 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.