Protection catching the wrong people.
THE SYMPTOMS
Customers reporting they cannot reach the site A challenge page appearing repeatedly Certain regions unable to access it Your own access blocked
WHERE TO LOOK
Cloudflare's security events log. It shows what was blocked or challenged, and which rule did it.
That identifies the cause immediately.
THE COMMON CAUSES
Security level set too high Under Attack mode left enabled after an incident A country block catching legitimate visitors Bot fight mode challenging a service you depend on A rule matching more broadly than intended
FIXING IT
Adjust the specific rule rather than lowering protection globally.
Add an allow rule for the case being caught wrongly.
UNDER ATTACK MODE
Check whether it is still on. People enable it during an incident and forget.
It presents an interstitial to every visitor and costs you traffic.
FOR SEARCH ENGINE CRAWLERS
If crawlers are being challenged, your site stops being indexed. Check the security events for crawler user agents.
Allow them explicitly.