Live data from Hacker News

Cloudflare took down our website

robindev.substack.com

471–480 of 483 posts

Re: Cloudflare took down our website

#472
Billion dollar unregulated casino that is burning through cloudflare ips.. i don't see where cloudflare can be blamed here, they stated you should BYOIP, you didn't approve and were banned, their is no blame here.

Just FYI some countries ban casino domains/ips that are not licensed to operate even when its "just a landing page that says sorry not available"

Re: Cloudflare took down our website

#473
post #389

As far as I can tell, the issue with this is: OP runs a casino/gambling site. Gambling is a regulatory mess (I have spent far too long dealing with this as an RNG supplier), and so it's very hard to comply with every jurisdiction, and each one needs you to prove compliance to operate in that jurisdiction.* Gaming companies spend a lot on compliance and tracking, but since the internet is the internet, it's pretty har…

It almost sounds like you are excusing them. Asking people to switch to the enterprise plan and bring your own IP is reasonable, but not on a timeline of 24h, and trashing their account when they tell you they are talking to a competitor makes me feel like I should flee Cloudflare services with all haste.

> and trashing their account when they tell you they are talking to a competitor

That is just a story they have made up. They don't know why Cloudflare shut their account down. I reckon the Fastly "reason" is likey a red herring.

Re: Cloudflare took down our website

#475

Earlier quoted context omitted.

>I have spent far too long dealing with this as an RNG supplier Is there much of a market for that? I thought random.org had it all sewn up.

No, random.org isn't in that market at all, aside from doing some drawings local to them and unofficial games. I think we are only one of ~3 TRNG suppliers who have been audited. Many games don't use a TRNG, though. Since it uses atmospheric noise, you can also influence the numbers from random.org by transmitting radio waves in the area nearby - the operator of random.org has mentioned that there's so much RF activi…

honestly this is fascinating to me, I was curious too and upon searching "RNG Supplier" I couldn't find anything, 3 supplies in the whole world is a crazy supply-side industry!

I was just curious to see what a landing page of a RNG supplier looked like, how do you even do sales for such a thing? With 3 players I guess it's just something you know in the industry and those partnerships are likely long-lived, right?

niches like this fascinate me for some reason!

Re: Cloudflare took down our website

#476

Earlier quoted context omitted.

My experience with Cloudflare is that anytime “Trust and Safety” are involved, no one will ever be told anything. Even if it’s a totally benign or even good situation. Even if they find a case in your favor or resolve an issue for you. Whoever runs that team really, really gets off on being withholding, as Buster Bluth would say.

This seems to be the rule in general with large companies. They say it's because if such teams don't operate under secret protocols, the "bad guys" will discover the loopholes in them. But I rather suspect that this has more to do with evading legal liability.

I tend to agree with you. Trust and Safety teams make a lot of judgement calls that they don’t want being disclosed because many of those calls are subjective.

Re: Cloudflare took down our website

#477

Earlier quoted context omitted.

I'd say worse than medical. As long as it works and doesn't fail, no one will give a fuck about medical hardware or the condition it's in. Just look at your average GP's ultrasound, it's probably older than the GP themselves is. Gambling however, you constantly have government auditors and the tax office crawling up your literal arse to make sure you don't cheat the gamblers, or worse, the government out of their mon…

Pretty sure it's your figurative arse but potato, pot-ahh-toh

Literal. Gotta make sure you're not hiding any numbers in there.

Re: Cloudflare took down our website

#478

As far as I can tell, the issue with this is: OP runs a casino/gambling site. Gambling is a regulatory mess (I have spent far too long dealing with this as an RNG supplier), and so it's very hard to comply with every jurisdiction, and each one needs you to prove compliance to operate in that jurisdiction.* Gaming companies spend a lot on compliance and tracking, but since the internet is the internet, it's pretty har…

This is just how people communicate now in the business world. It's up to you to read between the lines. One thing I've learned to be wary of on the job is "do you need help?" That phrase is often code for "You are not performing up to our expectations. This is your first and only warning. Get in shape or get out."

Poor communication is worse than no communication.

Re: Cloudflare took down our website

#479
post #389

Earlier quoted context omitted.

It almost sounds like you are excusing them. Asking people to switch to the enterprise plan and bring your own IP is reasonable, but not on a timeline of 24h, and trashing their account when they tell you they are talking to a competitor makes me feel like I should flee Cloudflare services with all haste.

> and trashing their account when they tell you they are talking to a competitor That is just a story they have made up. They don't know why Cloudflare shut their account down. I reckon the Fastly "reason" is likey a red herring.

It does not really matter, the 24h deadline is incredibly unprofessional. And deleting their account even more so.

I think the lesson here is to be as provider agnostic as possible and have a backup plan in case your current provider decides they don’t like you anymore or they just delete all your data just because they can.

Re: Cloudflare took down our website

#480

Earlier quoted context omitted.

That's strange. What was the "correct" answer?

They wanted me to roll out a fix first. Apparently rolling back first was not moving fast enough for the interviewer’s liking.

Depending on the service’s criticality, the cost of rolling back versus pushing a fix, service dependencies in their environment… having to push a fix might have been the better approach.

Without more details about the environment, it is a 50/50 call.

Post reply on HN