Bot Management Issues
Resolved
This incident has been resolved.
Update
Following a stable monitoring period over the weekend, we are now turning the detections back on for detection IDs: 50331648, 50331649 via a gradual, phased release.
We will continue to closely monitor system performance and customer impact throughout this rollout to ensure ongoing stability.
Update
We are continuing to update the identified issues with our Bot Management features for the rule IDs: 50331648, 50331649. After an additional review, we determined that impact existed prior to April 1st, 2026, and was present for a subset of Bot Management Customers. We have disabled the affected feature globally to prevent further impact; we are currently monitoring for stability over the weekend and detections are scheduled to be re-enabled on Monday, May 18th.
Update
We are continuing to update the identified issues with our Bot Management features for the rule IDs: 50331648, 50331649. After a additional review we determined that impact existed prior April 1st 2026, and was present for a subset of Bot Management Customers. We have disabled the affected feature globally to prevent further impact. An additional 72 hours is needed for stabilization, and review the detections.
Update
We are continuing to update the identified issues with our Bot Management features for the rule IDs: 50331648, 50331649. We have disabled the affected feature globally to prevent further impact. An additional 72 hours is needed for stabilization, and review of the detections.
Update
We have identified an issue with our Bot Management feature causing rules with IDs 50331648 and 50331649 to match traffic unexpectedly from April 1st 2026. Some customers using Bot Management may have seen an increase in requests flagged by these rules. We have disabled the affected feature to prevent further impact. A fix has been implemented, it will take 48 hours for detections to stabilize.
Update
We have identified an issue with our Bot Management feature causing rules with IDs 50331648 and 50331649 to match traffic unexpectedly. Customers using Bot Management may have seen an increase in requests flagged by these rules. We have disabled the affected feature to prevent further impact. Our team is actively working on a fix.
Update
The issue has been identified and a fix is being implemented.
Investigating
Cloudflare is investigating issues with our Bot Management feature. Customers may experience an unexpected increase in Bot Management rules matching detection IDs 50331648 and 50331649.
We are working to mitigate this problem. More updates to follow shortly.