(edit: we’re on the paid Workers Unlimited plan.)
we’ve built a non-trivial worker (a smart caching layer for our global APIs) and once we pushed this worker in production we got many reports from customers about being rate-limited.
We’ve tried our hardest to fix this with the builtin Cloudflare tools (Custom Firewall whitelist, PageRules) and to disable all sorts of firewall features but to no avail.
I noticed that among the blocked requests in the firewall log were internal Worker requests (to our pseudo caching host, to our google pubsub logging endpoint, etc) and saw this in the documentation:
Cloudflare’s abuse protection methods do not affect well-intentioned traffic. However, if you send many thousands of requests per second from a small number of client IP addresses, you can inadvertently trigger Cloudflare’s abuse protection. If you expect to receive 1015 errors in response to traffic or expect your application to incur these errors, contact Cloudflare to increase your limit.
Is it possible we ran into this issue already? Is there hope to remove these restrictions for us? What’s the best way to go about this - we had to revert our production launch due to these issues. :-/
Many thanks in advance