Bot Blocker Index

← Index

Akamai Bot Manager

cdn-bot-manager · Akamai · public (AKAM)

Challenged a default bot: 0.0% of 49 · 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 Akamai Bot Manager 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 Akamai Bot Manager describing its own product has been found in any of the 43 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. Numbers we found and held back are listed below.

Found on these pages, not published as a claim

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 Akamai Bot Manager against something it never said.

NumberSeenWhat it actually isArchived
90%2019-06 – 2020-11
11 months
not a vendor claim a named customer case study about that customer's own traffic mix, not a claim about Akamai's detection rate
…Research Page CASE STUDY eplus Bot Manager Leading ticket sales company blocks scalpers and takes control of over 90% of its website traffic coming from automated bots. View the Case Study CASE STUDY Luisa Via Roma Italian luxury…
link
Pages excavated
PageEraMonths probedMonths read
www.akamai.com/products/bot-manager
2019-01 – 2026-11
current9529
www.akamai.com/us/en/products/security/bot-manager.jsp
2019-01 – 2026-11
legacy URL9514

“Months read” counts snapshots we actually retrieved and searched.

Sanctioned test surfaces

SurfaceTypeTierBasis

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 49 sites detected running Akamai Bot Manager, this is what a default automated client met:

ServedChallengedBlocked

Challenge rate 0.0% — 95% CI 0–7% (±4pp, n=49). A wide interval means a small sample; read it accordingly.

Newest measurement behind this figure: 2026-11-15. 1 of 49 sites was last measured more than 21 days ago. Their most recent result is still counted in the figure.

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 Akamai Bot Manager 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 Akamai Bot Managerthat 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.

Akamai Bot Manager: share of sites that stopped a default bot, week by week (measured from a residential IP; challenged or blocked)
Weekly share, n ≥ 10 sitesThin sample, n < 10 (dashed line)No usable measurement recorded that weekWhiskers: 95% intervalDated change to our method (a step here may reflect it)
0%25%50%75%100%No usable measurement recorded for the week of Aug 24. Nothing is drawn or inferred for this week.no dataNo usable measurement recorded for the week of Sep 21. Nothing is drawn or inferred for this week.no data2026-10-13 (UTC): 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 Akamai Bot Manager’s sample. A step in the line at this date may reflect our method.method change2026-10-20 (UTC): 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 Akamai Bot Manager’s sample. A step in the line at this date may reflect our method.method changeWeek of Aug 10: 50% stopped (7 of 14 sites), 95% interval 27–73%Week of Aug 17: 42.5% stopped (17 of 40 sites), 95% interval 29–58%Week of Aug 31: 43.6% stopped (17 of 39 sites), 95% interval 29–59%Week of Sep 7: 43.2% stopped (16 of 37 sites), 95% interval 29–59%Week of Sep 14: 47.2% stopped (17 of 36 sites), 95% interval 32–63%Week of Sep 28: 44.7% stopped (17 of 38 sites), 95% interval 30–60%Week of Oct 5: 47.2% stopped (17 of 36 sites), 95% interval 32–63%Week of Oct 12: 54.2% stopped (26 of 48 sites), 95% interval 40–67%Week of Oct 19: 55.6% stopped (25 of 45 sites), 95% interval 41–69%Week of Oct 26: 53.2% stopped (25 of 47 sites), 95% interval 39–67%Week of Nov 2: 54.2% stopped (26 of 48 sites), 95% interval 40–67%Week of Nov 9: 53.3% stopped (24 of 45 sites), 95% interval 39–67%Aug 10n=14Aug 31n=39Sep 14n=36Oct 5n=36Oct 19n=45Nov 2n=48
Weekly figures
Week ofSitesStopped95% intervalNote
Aug 101450%27–73%
Aug 174042.5%29–58%
Aug 24———no usable measurement recorded
Aug 313943.6%29–59%
Sep 73743.2%29–59%
Sep 143647.2%32–63%
Sep 21———no usable measurement recorded
Sep 283844.7%30–60%
Oct 53647.2%32–63%
2026-10-13 (UTC)Our method changed: Classifier and attribution changeOn 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 Akamai Bot Manager’s sample. A step in the line at this date may reflect our method.
Oct 124854.2%40–67%
2026-10-20 (UTC)Our method changed: Retired sites whose vendor we no longer detectOn 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 Akamai Bot Manager’s sample. A step in the line at this date may reflect our method.
Oct 194555.6%41–69%
Oct 264753.2%39–67%
Nov 24854.2%40–67%
Nov 94553.3%39–67%

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

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.