| Category | Function | Share | Rank | Negative rate | Labels | Quadrant | Since September 2026 |
|---|---|---|---|---|---|---|---|
| Bot management | Network and edge | 0% | 70 of 83 | 40% | 10 | criticized challenger |
| Model | First choice | Alternative | Mention | Negative | Labels |
|---|---|---|---|---|---|
| Claude Haiku 4.5 | 0 | 0 | 0 | 0 | 0 |
| GPT-5.4 mini | 0 | 1 | 0 | 0 | 1 |
| Gemini 3.5 Flash | 0 | 0 | 1 | 1 | 2 |
| Perplexity Sonar | 0 | 0 | 0 | 0 | 0 |
| Grok 4.20 | 0 | 0 | 1 | 0 | 1 |
| Mistral Small | 0 | 0 | 1 | 0 | 1 |
| DeepSeek V4 Flash | 0 | 0 | 0 | 1 | 1 |
| Llama 4 Maverick | 0 | 0 | 1 | 0 | 1 |
| Qwen 3.7 Flash | 0 | 0 | 0 | 0 | 0 |
| Kimi K2 | 0 | 0 | 1 | 1 | 2 |
| GLM 4.7 FlashX | 0 | 0 | 0 | 1 | 1 |
| MiniMax M2.5 | 0 | 0 | 0 | 0 | 0 |
| GPT-6 Luna | 0 | 0 | 0 | 0 | 0 |
| Muse Glimmer 30B | 0 | 0 | 0 | 0 | 0 |
Verbatim evidence the judge attached to positive labels.
“Want web + mobile bot defense with F5 integration: F5” GPT-5.4 mini · Bot management · comparative prompt · alternative
Verbatim evidence attached to negative labels. A warning on a product with few labels is a warning; on a product with many, it is one voice among them.
“such as DataDome, HUMAN, Kasada, Akamai, or F5), watch out for these contract and technical warning signs” Gemini 3.5 Flash · Bot management · negative prompt · soft negative
“Dated user interface • Limited efficacy transparency • Higher setup effort” GLM 4.7 FlashX · Bot management · negative prompt · soft negative
“More enterprise-oriented but scalable” Kimi K2 · Bot management · direct prompt · soft negative
“Good policy control | Niche fit” DeepSeek V4 Flash · Bot management · scale prompt · soft negative
Citations exist only for the models that return a source list, five of the fourteen in this edition, so these counts come from 30 of the 35 answers that named F5 Distributed Cloud Bot Defense and are not a share of its labels.
129 of the 129 domain citations in answers naming F5 Distributed Cloud Bot Defense came from somebody else's page.
Pages are listed as the models cited them.
Search figures are US estimates from DataForSEO, read September 28, 2026; AI search demand is its modeled, directional estimate, not a count of queries to any assistant. The answers are this edition's. Two measurements side by side: neither is read as the cause of the other.
An email the morning each edition publishes: where this product moved, where it held, and by how much against the noise floor. One address, confirmed by a click; a stop link in every email.
Already following? Everything you follow, with a stop for each.
What F5 Distributed Cloud Bot Defense's own pages state, read October 5, 2026: f5.com/products/distributed-cloud-services/bot-defense, f5.com/resources/demos/f5-distributed-cloud-bot-defense-demo, community.f5.com/t/f5-distributed-cloud-bot-defense-overview-and-demo/69204, community.f5.com/t/protect-your-mobile-applications-with-f5-distributed-cloud-bot-defense/70175, community.f5.com/t/f5-distributed-cloud-bot-defense-protecting-aws-cloudfront-distributions/70802. A claimed page can correct any of them.
Claiming is free and changes nothing in the data. A claimed page shows a verified contact who is told when each edition publishes and when F5 Distributed Cloud Bot Defense's standing changes by more than the noise floor; the right to propose corrections to the vendor table, meaning names the judge wrote that should or should not read as F5 Distributed Cloud Bot Defense, applied by version and listed in the change log; and a one-line description supplied by the vendor and marked as such.
A new claim receives the current edition's vendor brief for F5 Distributed Cloud Bot Defense by email, built from the raw record of the edition. It shows: