The checkbox says you passed, the page reloads, and Cloudflare asks you to verify you are human again. Then again. The loop is not random, and it is not usually about whether you are actually human. It means Cloudflare never handed your browser the token that ends the check, and that failure has a short list of causes split cleanly between your browser and your network. We run a proxy network and FFraud, an IP-intelligence engine that scores the same reputation Cloudflare reads, so this guide explains what the loop is, why it repeats, and how to break it on either side.
Why does Cloudflare keep asking me to verify I am human?
Cloudflare ends a challenge by issuing a clearance cookie, cf_clearance, that your browser then presents on every following request so the check does not run again. The loop happens when that cookie never takes effect, for one of two reasons. Either your browser cannot store or return the cookie, so each request arrives looking unverified, or the address you are coming from is trusted so little that Cloudflare will not grant clearance even after you complete the challenge. One is a browser problem and one is a network problem, and telling them apart is the whole job.
What the loop actually is
A managed challenge is meant to run once. You solve it, Cloudflare sets cf_clearance for the site, and subsequent requests carry that cookie and pass straight through until it expires. When the next request does not carry a valid clearance cookie, Cloudflare has no way to know you just passed, so it presents the challenge again, and the cycle repeats for as long as the cookie keeps failing to appear. So the loop is always a clearance problem. The question is only whether the clearance was never stored or never granted.
The browser-side causes, which are the common ones
Most loops are the browser failing to keep the cookie, and these are the first things to rule out because they cost nothing to check.
- Cookies are blocked. If cookies are disabled for the site, or a strict privacy mode clears them between requests,
cf_clearancenever survives to the next page. Third-party cookie blocking and aggressive private-browsing modes both do this. - A privacy extension is interfering. Content blockers and anti-tracking extensions sometimes block the challenge script or the cookie it sets. A loop that stops the moment you disable extensions, or open a clean profile, was an extension.
- The system clock is wrong. The clearance cookie is time-limited, and a device clock that is off by more than a little can make a freshly issued cookie read as already invalid. This is a common cause on devices that lost their time setting.
- The browser is old or scripting is off. The challenge needs JavaScript and a reasonably current browser to run. A blocked script or an outdated engine cannot complete it, so clearance is never issued.
The fixes match the causes: allow cookies for the site, turn off extensions or use a clean profile, correct the system clock, and use a current browser with scripting enabled. Work through these before you touch anything about your network, because on a normal home connection the cause is almost always here.
The network-side cause, when it is the IP
If the browser side is clean and the loop persists, or if it appears only when a VPN or proxy is on, the cause is the address you are coming from. Cloudflare reads the reputation of your IP before it decides how hard to challenge you, and a low enough reputation changes the loop from a puzzle you can solve into one you cannot. It will issue the challenge, but it will not grant clearance to an exit it distrusts, so you pass the checkbox and are asked again regardless. A datacenter or hosting IP, a known VPN exit, or a shared address that many people abuse all read this way. This is the same reputation gate we map in why is my IP blocked, reached through Cloudflare's challenge rather than a flat block.
How to tell which half you are in
One test settles it. Open the site on your ordinary home connection with every VPN and proxy turned off.
| What you see | Where the cause is |
|---|---|
| Still loops on a plain home connection | Browser-side: cookies, clock, or an extension |
| Loops only with a VPN or proxy on | Network-side: the exit address reputation |
| Loops on one browser, not another | Browser-side: profile, extensions, or settings |
| Loops for everyone on a shared office or campus network | Network-side: the shared address reputation |
Then read the address the way Cloudflare reads it. Run your exit through our proxy checker to see whether it resolves to a hosting range or a consumer ISP, and through FFraud to see the reputation it carries. A hosting classification or a high risk score is why clearance is refused.
How a clean IP breaks the loop, and when it does not
When the cause is reputation, a clean residential address ends the loop, because it reads as an ordinary home connection that Cloudflare has no reason to distrust, so the clearance it refused a datacenter exit is granted. Our residential proxies route through real consumer ISPs and start at $0.44/GB pay-as-you-go, and you can read any exit with the proxy checker first so you do not trade one distrusted address for another. What matters is that the exit reads clean, which is the whole subject of what a clean IP is.
Be clear about the limit, though, because it is the honest part. A clean IP does nothing for a loop that blocked cookies, a wrong clock, or a privacy extension caused, since those never let clearance survive no matter how trusted the address is. If the loop follows you onto a plain home connection, no proxy will fix it, and the answer is on the browser side. Change the thing that is actually broken, not the thing that is easiest to change.
Sources
- Cloudflare, "Cloudflare challenges": how a managed challenge issues clearance and why a request without it is challenged again.
- Cloudflare, "Understanding the cf_clearance cookie": the clearance cookie that ends the challenge and how long it lasts.
- Cloudflare, "Troubleshooting challenge loops": cookies, clock skew, and browser settings as the common causes of a repeating challenge.