Akamai Bot Manager
cdn-bot-manager · Akamai · public (AKAM)
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 41 months we were able to read on the pages we track, out of 92 probed between 2019-01 and 2026-08. 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.
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.
| Number | Seen | What it actually is | Archived |
|---|---|---|---|
| 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 |
| Page | Era | Months probed | Months read |
|---|---|---|---|
| www.akamai.com/products/bot-manager 2019-01 – 2026-08 | current | 92 | 27 |
| www.akamai.com/us/en/products/security/bot-manager.jsp 2019-01 – 2026-08 | legacy URL | 92 | 14 |
“Months read” counts snapshots we actually retrieved and searched.
Sanctioned test surfaces
| Surface | Type | Tier | Basis |
|---|
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 41 sites detected running Akamai Bot Manager, this is what a default automated client met:
ServedChallengedBlocked
Challenge rate 0.0% — 95% CI 0–9% (±4pp, n=41). A wide interval means a small sample; read it accordingly.
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.
Cited external benchmarks
- Scrapfly — Akamai bypass — reported bypass 97%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.