Website QA intelligence for teams who ship
Guides Tool Comparisons QA Glossary Archive RSS Feed
heads-up platform & cms 1 sources 1 min read

Cloudflare Workers Rulesets Rate Limiting Bypass Issue Fixed

Cloudflare identified and fixed an issue where some requests processed by Cloudflare Workers were not correctly enforcing rulesets rate limiting counts. The incident began on April 20, 2024, and was resolved within approximately one hour. During this period, requests that should have been rate-limited or blocked may have been allowed through to origin servers. Cloudflare implemented a fix and moved to monitoring status to ensure the issue was fully resolved.

Sites using Cloudflare Workers with rulesets rate limiting may have experienced higher than expected traffic volumes during the incident window. This could have resulted in increased origin server load, potential DDoS exposure, and circumvention of API rate limits designed to prevent abuse. E-commerce sites relying on rate limiting for checkout protection or bot mitigation may have been particularly vulnerable.

Cloudflare Workers allow developers to run serverless code at the edge, often used for custom security rules, API protection, and traffic management. Rulesets rate limiting is a key feature for preventing abuse and managing traffic spikes. Rate limiting failures can expose applications to various attacks including credential stuffing, inventory hoarding, and API abuse that can significantly impact site performance and security.

Review your Cloudflare Workers configurations and rate limiting rules to ensure they are still functioning as expected after this incident. Test critical rate-limited endpoints manually to verify protection is active. Consider implementing backup rate limiting at the application level for mission-critical endpoints. Monitor origin server metrics for any unusual traffic patterns that may have occurred during the incident window on April 20.

Monitor Cloudflare's status page for any related incidents or follow-up communications about this rate limiting issue. Check if Cloudflare releases any post-incident analysis or recommended configuration changes for Workers-based rate limiting rules.