OpenAI: gpt-oss-20b Performance
Try gpt-oss-20b on us. Starter credit covers your first requests, then one key reaches all 13 provider routes with automatic failover.
openai/gpt-oss-20b
Measured performance
Continuously sampled p50/p95 time-to-first-token (TTFT), effective throughput, and success rate for OpenAI: gpt-oss-20b. 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 | Effective throughput | Uptime | Config excluded | Availability samples |
|---|---|---|---|---|---|---|
| nvidia-nim | 1058 ms | 1058 ms | — | 50.00% | — | 2 |
| greenference | 1125 ms | 1125 ms | — | 100.00% | — | 1 |
| akashml | 1179 ms | 2101 ms | — | 100.00% | — | 4 |
| regolo | 1541 ms | 1620 ms | — | 100.00% | — | 3 |
| databricks | 1557 ms | 1868 ms | — | 100.00% | — | 5 |
| cloudflare-workers-ai | 1997 ms | 3465 ms | — | 100.00% | — | 2 |
| deepinfra | — | — | — | — | 1 provider_error |
0 |
| openai | — | — | — | — | 1 provider_error |
0 |
Full provider & model leaderboard.
13 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.