Start typing to search.
Ranks providers by the uptime OpenRouter measured during the latest 30-minute window.
Anthropic currently ranks first at 100.00% via anthropic.
| Rank | Provider / route | Uptime (last 30 min) | Speed measurements | Endpoint details |
|---|---|---|---|---|
| #1 | Provider / route Anthropic anthropic | Uptime (last 30 min)100.00% | Speed measurements
| Endpoint details
|
| #2 | Provider / route Amazon Bedrock amazon-bedrock/global | Uptime (last 30 min)99.98% | Speed measurements
| Endpoint details
|
| #3 | Provider / route Google Vertex google-vertex/global | Uptime (last 30 min)99.63% | Speed measurements
| Endpoint details
|
| — | Provider / route Azure azure/us-east-2 | Uptime (last 30 min)Insufficient recent data | Speed measurements
| Endpoint details
|
| — | Provider / route Google Vertex google-vertex/europe | Uptime (last 30 min)Insufficient recent data | Speed measurements
| Endpoint details
|
| — | Provider / route Amazon Bedrock amazon-bedrock/eu-west-1 | Uptime (last 30 min)Insufficient recent data | Speed measurements
| Endpoint details
|
Endpoint data fetched .
Claude Haiku 4.5 endpoint guide
3 of 6 Claude Haiku 4.5 endpoints currently have the published data required for this ranking. Anthropic leads at 100.00% via anthropic. The table keeps unranked routes visible so missing measurements do not look like missing provider availability.
The reliability ranking uses the published 30-minute endpoint uptime measurement. This short operational window can reveal current instability, but it is not a service-level agreement or a substitute for longer-term availability monitoring.
Amazon Bedrock currently ranks second at 99.98%. 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 Haiku 4.5 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.
