zlacker

Cloudflare is really transparant about things ( eg. outages).

Reality is that Cloudflare serves 60% of the internet and this issue popped up. They are checking it internally what happened, as I understand from jgrahamc.

>>NicoJu+(OP)
I don't think you realize it, but your answer while being wrong on many levels isn't even saying what you think it is saying. Reading your message, what one understands is "Cloudflare has so much on their hand you would be stupid to give them your business and think they would have time to deal with it", aka run away.

>>nolok+9O
That's not what it says. Having many employees means you need to improve processes sometimes.

I actually don't know any businesses ( except solo ones) that don't have issues tbh. It's part of having employees.

That cloudfare handles 60% of the internet, just makes the odds really high for someone to complain.

It's resolved pretty quick and they are following up internally on what happened.

And the OP mentioned himselve what the issue was fyi. Check his latest post. This whole thing is about someone bending the rules concerning CW and he knows it :)

>>NicoJu+qw3
> This whole thing is about someone bending the rules concerning CW and he knows it :)

Hell no. Using workers for non-html content is not "bending the rules". It's a normal and encouraged use case. And saying "I'm a heavy user, is that maybe part of it?" does not mean they did anything wrong.

I don't see any signs of bending rules.

>>Dylan1+3d5
A very heavy user where they literally said "it could potentially work".

>>NicoJu+PI6
What comment are you talking about?

And someone going "Is this too much load? Are they not being paid enough?" as desperate guesses after getting banned, does not mean they were actually doing anything borderline or that they "know it".