Provider Fallback Outage Routing
OpenRouter · OpenRouter
OpenRouter evals — Provider Fallback & Outage Routing (relift v3)
About OpenRouter
OpenRouter is a unified LLM routing layer that gives developers access to hundreds of models through a single OpenAI-compatible API. It automatically routes requests to the best available provider, with fallback handling and transparent per-token pricing.
Sample tests· showing 3 of 10
| # | Input | Expected behavior | Check |
|---|---|---|---|
| 01 | Production gateway sends model anthropic/claude-3.5-sonnet with default provider routing; primary Anthropic endpoint times out with 502; secondary providers remain healthy per GET /api/v1/models. | Router retries on an alternate eligible provider for the same model slug and only returns 502 after exhausting documented provider-level retries, preserving the OpenAI-compatible error envelope. | Pass / FailRoutingcritical |
| 02 | Compliance workload pins provider.order to a single EU host; allow_fallbacks explicitly false in request body to POST /api/v1/chat/completions. | No silent reroute to other providers; client receives failure once the pinned provider is exhausted, with error body indicating routing could not satisfy constraints. | Pass / FailRoutinghigh |
| 03 | Enterprise contract requires trying Azure first for data residency; order array set on every chat completion call. | States sequential preference per order list with failover to next provider on documented failure classes, not a parallel race unless sort settings imply otherwise. | Pass / FailRoutingmedium |
Rubric criteria
- Openrouter
- Ai Platform
- Provider Fallback Outage Routing
Recommended for
Works with
Related evals
Run this eval in your workspace
Connect your data, configure thresholds, and review results with your team.