| Category | Function | Share | Rank | Negative rate | Labels | Quadrant | Since September 2026 |
|---|---|---|---|---|---|---|---|
| Load balancers | Network and edge | 6% | 4 of 94 | 12% | 33 | accepted challenger |
| Model | First choice | Alternative | Mention | Negative | Labels |
|---|---|---|---|---|---|
| Claude Haiku 4.5 | 2 | 1 | 1 | 0 | 4 |
| GPT-5.4 mini | 0 | 0 | 0 | 0 | 0 |
| Gemini 3.5 Flash | 1 | 2 | 0 | 0 | 3 |
| Perplexity Sonar | 0 | 1 | 1 | 0 | 2 |
| Grok 4.1 Fast | 2 | 1 | 0 | 2 | 5 |
| Mistral Small | 0 | 2 | 0 | 0 | 2 |
| DeepSeek V4 Flash | 0 | 2 | 0 | 0 | 2 |
| Llama 4 Maverick | 0 | 0 | 2 | 0 | 2 |
| Qwen 3.7 Flash | 1 | 0 | 1 | 0 | 2 |
| Kimi K2 | 0 | 1 | 1 | 1 | 3 |
| GLM 4.7 FlashX | 1 | 0 | 0 | 0 | 1 |
| MiniMax M2.5 | 1 | 1 | 1 | 1 | 4 |
| GPT-6 Luna | 0 | 1 | 0 | 0 | 1 |
| Muse Glimmer 30B | 0 | 1 | 1 | 0 | 2 |
Verbatim evidence the judge attached to positive labels.
“Cloud-native load balancers (AWS ALB, Azure LB) are often the best fit - they scale automatically, integrate with your infrastructure, and have predictable costs” Claude Haiku 4.5 · Load balancers · direct prompt · first choice
“For very small budgets: Start with cloud-native load balancers (AWS ALB, etc.) as they eliminate upfront costs” MiniMax M2.5 · Load balancers · budget prompt · first choice
“Prefer managed cloud-native: AWS ALB/NLB, GCP Premium/Global, Azure Standard—high reliability scores” Grok 4.1 Fast · Load balancers · negative prompt · first choice
“Cloud‑native LBs (AWS ALB/NLB, GCP Cloud LB, Azure Standard LB) are designed to do exactly this.” GLM 4.7 FlashX · Load balancers · negative prompt · first choice
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.
“Avoid cloud-native load balancers (like AWS ALB/ELB) if your budget is tight” Kimi K2 · Load balancers · budget prompt · hard negative
“Cloud-native load balancers (AWS ELB, Azure LB, GCP LB) excel in their ecosystems but may lack deep packet inspection” MiniMax M2.5 · Load balancers · negative prompt · soft negative
“Relies on CloudWatch; tuning timeouts/limits needed.” Grok 4.1 Fast · Load balancers · negative prompt · soft negative
“Auto-scales, but costs add up with volume.” Grok 4.1 Fast · Load balancers · budget 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 77 of the 93 answers that named AWS Elastic Load Balancing and are not a share of its labels.
279 of the 304 domain citations in answers naming AWS Elastic Load Balancing came from somebody else's page.
Pages are listed as the models cited them.
Search figures are US estimates from DataForSEO, read October 5, 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 AWS Elastic Load Balancing's own pages state, read October 5, 2026: aws.amazon.com/elasticloadbalancing/network-load-balancer, aws.amazon.com/elasticloadbalancing/gateway-load-balancer, aws.amazon.com/elasticloadbalancing/application-load-balancer, aws.amazon.com/blogs/aws/internal-elastic-load-balancers, aws.amazon.com/blogs/aws/elastic-load-balancing-resources. 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 AWS Elastic Load Balancing'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 AWS Elastic Load Balancing, 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 AWS Elastic Load Balancing by email, built from the raw record of the edition. It shows: