Google: Gemma 4 26B A4B Performance
Compare measured TTFT, TTFB, throughput, uptime, and route health for Google: Gemma 4 26B A4B across TrustedRouter providers using metadata-only production probes.
google/gemma-4-26b-a4b-it
Measured performance
Continuously sampled p50/p95 time-to-first-token (TTFT), time-to-first-byte (TTFB), effective throughput, and success rate for Google: Gemma 4 26B A4B . Effective throughput uses provider-reported output tokens over complete request time. Unsupported route and probe-configuration rows are separated from provider downtime, and no prompt or output content is stored.
| Provider | p50 TTFT | p95 TTFT | p50 TTFB | Effective throughput | Uptime | Config excluded | Availability samples |
|---|---|---|---|---|---|---|---|
| deepinfra | 1411 ms | 1814 ms | 1411 ms | — | 100.00% | — | 3 |
| cloudflare-workers-ai | 1576 ms | 4344 ms | 1576 ms | — | 100.00% | 2 probe_config_error |
5 |
| parasail | 1643 ms | 8900 ms | 1643 ms | — | 100.00% | — | 7 |
Full provider & model leaderboard.
12 routes.
More routes give the auto router more room to fail over around provider 429 and 5xx responses.
Gateway overhead is measured separately.
Public status separates TLS/health overhead from full model latency so slow LLMs do not inflate the router metric.
Metadata rollups.
Status samples store latency, outcome, provider, model, route, cost, and region metadata only.
View public status or inspect provider routes.