Imperva Advanced Bot Protection
full-suite · Thales (absorbed Distil Networks) · Thales
Challenged a default bot: 75.0% of 4 · newest measurement 2026-11-15
Marketing claims
No claim captured yet.
Claim archaeology — what has been marketed, and when
Monthly Wayback snapshots of the 2 pages listed below, read back to 2019. A number reaches this timeline only after the sentence around it was read and judged to be Imperva Advanced Bot Protection 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.
No claim we could publish as Imperva Advanced Bot Protection describing its own product has been found in any of the 9 months we were able to read on the pages we track, out of 95 probed between 2019-01 and 2026-11. That is a statement about these pages only — see the list below.
No publishable claim was found on these pages for: detection accuracy, coverage, false-positive rate, decision latency.
| Page | Era | Months probed | Months read |
|---|---|---|---|
| www.distilnetworks.com/ 2019-01 – 2026-11 | pre-acquisition domain | 95 | 9 2 blocked |
| www.imperva.com/products/advanced-bot-protection/ 2019-01 – 2026-11 | current | 95 | 0 7 blocked |
“Months read” counts snapshots we actually retrieved and searched. 9 snapshot(s) were the vendor’s own bot wall rather than the page — the archiver was blocked, so those months are recorded as unreadable, never as “no claim”. Pages with no readable months contribute nothing either way.
Of 190 page-months probed across 2 tracked pages, 9 were walled (the archived page looks like a block page) and 0 were not this vendor (the archived page does not carry Imperva Advanced Bot Protection’s name). None of them is a month where Imperva Advanced Bot Protection was read and found to carry no claim.
| Page | Read | Walled | Not this vendor | No HTTP-200 capture |
|---|---|---|---|---|
| www.distilnetworks.com/ 2019-01 – 2026-11 · 95 months probed | 9 of 95 | 2 of 95 2019-05 – 2019-06 | — | 84 of 95 |
| www.imperva.com/products/advanced-bot-protection/ 2019-01 – 2026-11 · 95 months probed | 0 of 95 | 7 of 95 2023-12 – 2026-03 | — | 88 of 95 |
Walled. The archived page looks like a block or bot-protection page rather than the page itself (a text-pattern check, not a manual one), so it could not be read for Imperva Advanced Bot Protection’s claims. Not this vendor. The archived page does not carry Imperva Advanced Bot Protection’s name, so it cannot be shown to be Imperva Advanced Bot Protection’s marketing and none of its numbers is attributed to Imperva Advanced Bot Protection. This is a name check only: it does not establish who published the page or when ownership changed. These months are kept as unknown in the timeline, not counted for or against Imperva Advanced Bot Protection. No HTTP-200 capture. The archive lookup only counts captures that returned HTTP 200, so a month whose only capture was an error or a redirect is listed here too.
A walled, not-this-vendor or no-HTTP-200 month is not evidence that Imperva Advanced Bot Protection marketed no number then. For that page it is evidence of nothing, and the timeline treats that page-month as unreadable, never as “no claim”. The timeline is per vendor-month, so a month can still be classed from another tracked page that was read.
Sanctioned test surfaces
| Surface | Type | Tier | Basis |
|---|---|---|---|
| Cloud WAF free/community tier on own site | self-deploy-free | B | Own deployment |
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 4 sites detected running Imperva Advanced Bot Protection, this is what a default automated client met:
ServedChallengedBlocked
Challenge rate 75.0% — 95% CI 30–95% (±33pp, n=4). 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.
Challenged or blocked, week by week
Each point is one weekly measurement cycle: the share of sites detected running Imperva Advanced Bot Protectionthat 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 17 | 3 | 66.7% | 21–94% | thin sample |
| Aug 24 | — | — | — | no usable measurement recorded |
| Aug 31 | 3 | 66.7% | 21–94% | thin sample |
| Sep 7 | 3 | 66.7% | 21–94% | thin sample |
| Sep 14 | 3 | 66.7% | 21–94% | thin sample |
| Sep 21 | — | — | — | no usable measurement recorded |
| Sep 28 | 3 | 66.7% | 21–94% | thin sample |
| Oct 5 | 3 | 66.7% | 21–94% | thin sample |
| Oct 12 | 3 | 66.7% | 21–94% | thin sample |
| Oct 19 | 3 | 66.7% | 21–94% | thin sample |
| Oct 26 | 3 | 66.7% | 21–94% | thin sample |
| Nov 2 | 4 | 75% | 30–95% | thin sample |
| Nov 9 | 4 | 75% | 30–95% | thin sample |
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
None cited yet.