| Category | Function | Share | Rank | Negative rate | Labels | Quadrant | Since September 2026 |
|---|---|---|---|---|---|---|---|
| Load balancers | Network and edge | 0% | 15 of 94 | 0% | 18 | accepted challenger |
| Model | First choice | Alternative | Mention | Negative | Labels |
|---|---|---|---|---|---|
| Claude Haiku 4.5 | 0 | 1 | 3 | 0 | 4 |
| GPT-5.4 mini | 0 | 0 | 0 | 0 | 0 |
| Gemini 3.5 Flash | 0 | 1 | 0 | 0 | 1 |
| Perplexity Sonar | 0 | 0 | 0 | 0 | 0 |
| Grok 4.1 Fast | 0 | 0 | 1 | 0 | 1 |
| Mistral Small | 0 | 2 | 0 | 0 | 2 |
| DeepSeek V4 Flash | 0 | 1 | 0 | 0 | 1 |
| Llama 4 Maverick | 0 | 0 | 1 | 0 | 1 |
| Qwen 3.7 Flash | 0 | 0 | 1 | 0 | 1 |
| Kimi K2 | 0 | 1 | 0 | 0 | 1 |
| GLM 4.7 FlashX | 0 | 0 | 2 | 0 | 2 |
| MiniMax M2.5 | 0 | 1 | 1 | 0 | 2 |
| GPT-6 Luna | 0 | 1 | 0 | 0 | 1 |
| Muse Glimmer 30B | 0 | 0 | 1 | 0 | 1 |
Verbatim evidence the judge attached to positive labels.
“Starts at $0.025/hour for basic rules and offers instant autoscaling, making it a good option if you're on Google Cloud.” Mistral Small · Load balancers · budget prompt · alternative
“AWS Elastic Load Balancing, Azure Load Balancer, or Google Cloud Load Balancing” MiniMax M2.5 · Load balancers · budget prompt · alternative
“Best for: Google Cloud users needing global load distribution and auto-scaling.” Mistral Small · Load balancers · comparative prompt · alternative
“Google Cloud Load Balancing | Google Cloud | GCP workloads” Kimi K2 · Load balancers · 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.
Citations exist only for the models that return a source list, five of the fourteen in this edition, so these counts come from 51 of the 63 answers that named Google Cloud Load Balancing and are not a share of its labels.
206 of the 206 domain citations in answers naming Google Cloud 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.
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 Google Cloud 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 Google Cloud 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 Google Cloud Load Balancing by email, built from the raw record of the edition. It shows: