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.
I find stuff like this all the time, railway.com recently launched an object storage service, but it's simply a wrapper for wasabi buckets under the hood, and they don't mention this anywhere... not even the subprocessors page https://railway.com/legal/subprocessors - customers have no idea they are using wasabi storage buckets unless they dig around the dns records. so i have to do all this research to find upstream dependencies and go subscribe to status.wasabi.com alerts etc.
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!
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.
showerst|3 months ago
miken123|3 months ago
coreylane|3 months ago
dig b1.eu-central-1.storage.railway.app +short
s3.eu-central-1.wasabisys.com.
eu-central-1.wasabisys.com.
wesammikhail|3 months ago
bbss|3 months ago
jsheard|3 months ago
matt-p|3 months ago
TechRemarker|3 months ago
foxyv|3 months ago
archerx|3 months ago
soheilpro|3 months ago
> This incident affects: API, App Platform (Global), Load Balancers (Global), and Spaces (Global).
hshdhdhj4444|3 months ago
My DOs are working fine as well.
giancarlostoro|3 months ago
watermelon0|3 months ago
matt-p|3 months ago
BubbleRings|3 months ago
zx8080|3 months ago
igtztorrero|3 months ago
aforty|3 months ago
mrkramer|3 months ago
red-iron-pine|3 months ago
maybe also GCP, hetzner, akamai
drob518|3 months ago