Cloudflare Bot Management
cdn-bot-manager · Cloudflare · public (NET)
Challenged a default bot: 48.8% of 43 · newest measurement 2026-11-15
Marketing claims
No claim captured yet.
Claim archaeology — what has been marketed, and when
Monthly Wayback snapshots of the 1 page listed below, read back to 2019. A number reaches this timeline only after the sentence around it was read and judged to be Cloudflare Bot Management describing its own product. Those judgements were made by an AI model (claude-opus-5) and have not yet been checked by a person. Every one is published with the quote it was made from and the reason it was made, so you can check it against the archived page yourself. Numbers that turned out to be customer case studies, uptime SLAs or traffic-composition stats are listed further down — recorded, not published. Nothing is inferred between two dated snapshots.
| Period | Months | What the archived page said | Archived |
|---|---|---|---|
| Jan 2019 – Feb 2022 | 38 | No decision latency claim in 35 months where we read a page that has carried it; 3 further months had no readable snapshot | — |
| Mar 2022 – May 2023 | 15 | 0.3ms…required. Lowest Latency Cloudflare Bot Management delivers ultra low-latency bot defenses, with median latency of 0.3 milliseconds or less. Our bot management performance keeps applications in the fast lane. Rich Analytics and Logs… | first · last |
| Jun 2023 – Nov 2026 | 42 | No decision latency claim in 4 months where we read a page that has carried it; 38 further months had no readable snapshot | — |
No publishable claim was found on these pages for: detection accuracy, coverage, false-positive rate. Numbers we found and held back are listed below.
Our extractor pulled these numbers out of the same snapshots. Each was held back: a number bound to a metric is not automatically the vendor claiming a capability, and treating it as one would score Cloudflare Bot Management against something it never said.
| Number | Seen | What it actually is | Archived |
|---|---|---|---|
| 0.01% | 2019-04 – 2023-04 49 months | not a vendor claim a named customer testimonial, not Cloudflare describing its own product…Their mitigation strategies block bots without impacting real users - our false-positive rate is now less than 0.01%." Tony Bruess Engineer Forrester named Cloudflare a “Strong Performer” in bot management Cloudflare was named a… | link |
| Page | Era | Months probed | Months read |
|---|---|---|---|
| www.cloudflare.com/products/bot-management/ 2019-01 – 2026-11 | current | 95 | 54 |
“Months read” counts snapshots we actually retrieved and searched.
Sanctioned test surfaces
| Surface | Type | Tier | Basis |
|---|---|---|---|
| Own CF-proxied site (Turnstile free + Bot Management) | self-deploy-free | B | We own the site + CF account |
A — vendor invites testing · B — our own deployment · C — passive observation
Our test results
No sanctioned runs recorded yet.
Real-world challenge rate (passive, anonymized)
Across 43 sites detected running Cloudflare Bot Management, this is what a default automated client met:
ServedChallengedBlocked
Challenge rate 48.8% — 95% CI 35–63% (±14pp, n=43). A wide interval means a small sample; read it accordingly.
Newest measurement behind this figure: 2026-11-15. No site in this figure was last measured more than 21 days ago.
Site identities are not published. This measures whether a vanilla client is challenged — no bypass performed.
Detection is by CDN fingerprint, so “served” means the site sits behind Cloudflare Bot Management but a default bot was not actively challenged — CDN presence is not proof the paid bot-management product is engaged. The challenged + blocked share is where protection actively fired.
Challenged or blocked, week by week
Each point is one weekly measurement cycle: the share of sites detected running Cloudflare Bot Managementthat challenged or blocked a default automated client, taking each site’s latest run of the week. Weeks with no usable measurement are shown as gaps, and the line never crosses one — no usable measurement was recorded for those weeks, and nothing is inferred across them.
Weekly figures
| Week of | Sites | Stopped | 95% interval | Note |
|---|---|---|---|---|
| Aug 10 | 11 | 63.6% | 35–85% | |
| Aug 17 | 41 | 68.3% | 53–80% | |
| Aug 24 | — | — | — | no usable measurement recorded |
| Aug 31 | 43 | 65.1% | 50–78% | |
| Sep 7 | 39 | 69.2% | 54–81% | |
| Sep 14 | 42 | 69% | 54–81% | |
| Sep 21 | — | — | — | no usable measurement recorded |
| Sep 28 | 41 | 70.7% | 55–82% | |
| Oct 5 | 42 | 66.7% | 52–79% | |
| 2026-10-13 (UTC) | Our method changed: Classifier and attribution change | On this date we changed how we classify responses and attribute sites to a vendor: weaker-tier evidence can now attribute a site to Akamai, we read the cf-mitigated response header, and we apply a two-factor denial rule. Sites that had previously refused our client without being attributable could enter Akamai's sample from this date, and some Cloudflare sites moved between the challenged and blocked columns. We did not measure an effect on other vendors' samples, so this marker is shown only on the vendors it touched. This change affected Cloudflare Bot Management’s sample. A step in the line at this date may reflect our method. | ||
| Oct 12 | 41 | 73.2% | 58–84% | |
| 2026-10-20 (UTC) | Our method changed: Retired sites whose vendor we no longer detect | On this date we removed seven sites from the figures. Each had stopped carrying any signature we can read, or had moved to a different vendor, or had left our sweep list, and each retirement carries a date and a recorded reason. Until now such a site kept its last measurement published indefinitely, so a figure could rest on evidence weeks old. A step in a line at this date reflects that removal, not a change in how the vendor behaved. One further site qualified on age but was held back rather than retired, because removing it would have pushed a published figure below the sample size we are willing to publish. Nothing is deleted: the retired sites keep their measurement history, and a site detected again after its retirement date counts again. This change affected Cloudflare Bot Management’s sample. A step in the line at this date may reflect our method. | ||
| Oct 19 | 42 | 71.4% | 56–83% | |
| Oct 26 | 41 | 73.2% | 58–84% | |
| Nov 2 | 40 | 72.5% | 57–84% | |
| Nov 9 | 40 | 72.5% | 57–84% | |
Residential vantage only; datacenter runs are never pooled in. Hollow points rest on a small sample — read their intervals, not their position.
These points will not always match the headline rate above, and both are right: a point counts only the sites measured in that week, while the headline keeps each site’s most recent result whenever it was taken. A site missed in one week still counts above, but not in that week’s point.
Cited external benchmarks
- Scrapfly — Cloudflare bypass — reported bypass 98%Self-reported by Scrapfly (commercial bypass API) — vendor marketing figure, not independently verified (captured 2026-08-14).
- techinz/browsers-benchmarkIndependent open-source browser-automation benchmark; per-engine bypass rates vary.
We cite these rather than generating real-world bypass numbers against non-consenting production systems. Commercial-vendor figures are self-reported marketing claims, flagged as such above — treat them as the ceiling a paying bypass service advertises.