error rate limiting without set custom role

[plain rampart]

I’m currently testing a public API that goes through Cloudflare and a proxy. I tried with 200 concurrent connections, and it was successful. However, when I increased it to 500 concurrent connections, it immediately failed. Initially, I didn’t set any custom rules for specific rate limits, but I created a rule to skip the rate limit for my public API, and the result was as mentioned above. Is there a certain threshold from Cloudflare that cannot be managed by the user? And how can I fix this issue without disabling the proxy, as this issue only occurs due to rate limiting?

[toxic sigil]

Could be a multitude of things, general DDoS protection, any WAF rules, Workers burst rate limiting

You can configure the DDoS settings on your zone & configure waf/rate-limiting there.

For the Workers burst rate limiting, if you can confirm it is that then you can get that raised easily too.