← Back to context

Comment by showerst

5 hours ago

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.

8 comments

showerst

Reply
coreylane  3 hours ago

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.

dig b1.eu-central-1.storage.railway.app +short

s3.eu-central-1.wasabisys.com.

eu-central-1.wasabisys.com.

wesammikhail  4 hours ago

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!

  • showerst  3 hours ago

    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.