GPT-4.1 Nano
openai/gpt-4.1-nano
Compare with GPT-4.1 Nano (batch), GPT-5 Nano, GPT-4.1
CompareGPT-4.1 Nano
| Provider | State | Uptime 5m | 24h | p50 latency | p99 | Throughput | Context | $/Mtok |
|---|---|---|---|---|---|---|---|---|
Azureazure | Healthy | 100% | 99.97% | 1.00s | 80.9s | 26 tps | 1.0M | $0.100 / $0.400 |
OpenAIopenai | Healthy | 99.50% | 99.43% | 585ms | 4.11s | 43 tps | 1.0M | $0.100 / $0.400 |
Azureazure/swedencentral | No data | — | — | — | — | — | 1.0M | $0.110 / $0.440 |
- Azure100%Healthy24h 99.97%
- p50
- 1.00s
- p99
- 80.9s
- Throughput
- 26 tps
- Context
- 1.0M
- $/Mtok
- $0.100 / $0.400
azure - OpenAI99.50%Healthy24h 99.43%
- p50
- 585ms
- p99
- 4.11s
- Throughput
- 43 tps
- Context
- 1.0M
- $/Mtok
- $0.100 / $0.400
openai - Azure—No data24h —
- p50
- —
- p99
- —
- Throughput
- —
- Context
- 1.0M
- $/Mtok
- $0.110 / $0.440
azure/swedencentral
Measured 2m ago. Latency and throughput are OpenRouter's rolling 30-minute windows.
History
1 endpoint reporting no data is omitted from the charts.
Availability
Axis starts at 90% so small differences stay visible; it expands to 0 when an endpoint falls below.
Time to first token
Logarithmic axis — the fleet spans two orders of magnitude. p50 and p99 are OpenRouter's rolling 30-minute windows.
Throughput
Median tokens per second.