Google: Gemini 2.5 Flash Performance
TrustedRouter performance signals and provider route posture for Google: Gemini 2.5 Flash.
google/gemini-2.5-flash
Measured performance
Continuously sampled p50/p95 time-to-first-token (TTFT), time-to-first-byte (TTFB), effective throughput, and success rate for Google: Gemini 2.5 Flash. 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 |
|---|---|---|---|---|---|---|---|
| google-ai-studio | 1145 ms | 17382 ms | 1145 ms | — | 100.00% | — | 12 |
| google-vertex | 1464 ms | 4042 ms | 1464 ms | — | 100.00% | — | 8 |
| lightning | 2015 ms | 3459 ms | 2015 ms | — | 100.00% | — | 8 |
| atlas-cloud | 2022 ms | 3800 ms | 2021 ms | — | 100.00% | — | 4 |
| deepinfra | 2584 ms | 2584 ms | 2583 ms | — | 100.00% | — | 1 |
Full provider & model leaderboard.
8 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.