Start typing to search.
Ranks providers by how quickly the first generated token appears. Providers without enough recent data remain visible after ranked rows.
Amazon Bedrock currently ranks first at 1.42 s via amazon-bedrock/us-east-1.
| Rank | Provider / route | Time to first token | Speed measurements | Endpoint details |
|---|---|---|---|---|
| #1 | Provider / route Amazon Bedrock amazon-bedrock/us-east-1 | Time to first token1.42 s | Speed measurements
| Endpoint details
|
| #2 | Provider / route Anthropic anthropic/2 | Time to first token1.73 s | Speed measurements
| Endpoint details
|
| #3 | Provider / route Google Vertex google-vertex/global | Time to first token1.82 s | Speed measurements
| Endpoint details
|
| #4 | Provider / route Azure azure/us-east-2 | Time to first token2.37 s | Speed measurements
| Endpoint details
|
| #5 | Provider / route Anthropic anthropic | Time to first token2.53 s | Speed measurements
| Endpoint details
|
| — | Provider / route Google Vertex google-vertex/europe | Time to first tokenInsufficient recent data | Speed measurements
| Endpoint details
|
Endpoint data fetched .
Claude Opus 4.6 endpoint guide
5 of 6 Claude Opus 4.6 endpoints currently have the published data required for this ranking. Amazon Bedrock leads at 1.42 s via amazon-bedrock/us-east-1. The table keeps unranked routes visible so missing measurements do not look like missing provider availability.
The first-token ranking orders endpoints by the recent median time before output begins. This is useful for interactive applications, but it should be read alongside throughput because the first provider to start is not always the first to finish a long answer.
Anthropic currently ranks second at 1.73 s. Compare that gap with input and output price, response-start time, output speed, 30-minute uptime, context length, and the exact route before deciding whether first place is meaningful for your workload.
Claude Opus 4.6 has 6 published provider options, and performance data is matched to each exact OpenRouter routing tag. Different quantization, context, regional deployment, or provider configuration can change price and behavior even when the underlying model name is identical.
