Start typing to search.
Ranks providers by estimated time to return 500 tokens, combining the wait for the first token with output speed.
Google Vertex currently ranks first at 7.57 s via google-vertex/europe.
| Rank | Provider / route | Estimated response time | Speed measurements | Endpoint details |
|---|---|---|---|---|
| #1 | Provider / route Google Vertex google-vertex/europe | Estimated response time7.57 s | Speed measurements
| Endpoint details
|
| #2 | Provider / route Google Vertex google-vertex/global | Estimated response time9.70 s | Speed measurements
| Endpoint details
|
| #3 | Provider / route Amazon Bedrock amazon-bedrock/us | Estimated response time10.23 s | Speed measurements
| Endpoint details
|
| #4 | Provider / route Anthropic anthropic | Estimated response time10.41 s | Speed measurements
| Endpoint details
|
| #5 | Provider / route Amazon Bedrock amazon-bedrock/eu-west-1 | Estimated response time11.09 s | Speed measurements
| Endpoint details
|
| #6 | Provider / route Anthropic anthropic/2 | Estimated response time11.99 s | Speed measurements
| Endpoint details
|
| #7 | Provider / route Azure azure/us-east-2 | Estimated response time19.94 s | Speed measurements
| Endpoint details
|
Endpoint data fetched .
Claude Opus 4.8 endpoint guide
7 of 7 Claude Opus 4.8 endpoints currently have the published data required for this ranking. Google Vertex leads at 7.57 s via google-vertex/europe. The table keeps unranked routes visible so missing measurements do not look like missing provider availability.
The fastest ranking estimates a 500-token answer by adding the recent median first-token wait to 500 divided by median output throughput. It represents an example complete response, not a guarantee for every prompt or request size.
Google Vertex currently ranks second at 9.70 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.8 has 7 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.
