Previous edition: Policy vs direct eventual success rate, Jan-Apr 2026
Policy vs direct eventual success rate, January to October 2026
Policy vs direct eventual success rate, January to October 2026
Routing policies retry a failed request on another provider. Direct requests have no fallback.
Policy (with fallback)Direct (single provider)
In October 2026, 97.8% of requests sent through a Requesty routing policy eventually succeeded, against 95.5% of direct requests.Source: Requesty production gateway, request-level eventual success (max(successful) across all attempts).
Do routing policies make LLM requests more reliable? In October 2026, 97.8% of requests sent through a Requesty routing policy eventually succeeded, against 95.5% of direct requests. The gap was widest in August at 7.8 points.
Why it mattersA policy retries a failed request on another provider. Direct requests have no fallback, so every upstream incident reaches the customer.
Period
Jan 2026 to Oct 2026
Updated
November 11, 2026
ID
policy-eventual-success-trend-jan-october-2026
§ 01
Key findings
- 01July: policy 98.3%, direct 96.8%.
- 02August: policy 97.8%, direct 90.0%.
- 03September: policy 98.3%, direct 90.4%.
- 04October: policy 97.8%, direct 95.5%.
§ 01b
Questions this answers
- Do LLM fallbacks improve reliability?
- How much more reliable are routing policies?
- What is the eventual success rate of LLM requests?
§ 02
Data
| Month | Policy - eventual success(percent) | Direct - eventual success(percent) |
|---|---|---|
| January | 97.50% | 94.91% |
| February | 98.72% | 97.60% |
| March | 98.55% | 87.62% |
| April | 99.25% | 86.16% |
| May | 98.60% | 96.44% |
| June | 98.14% | 95.26% |
| July | 98.30% | 96.77% |
| August | 97.79% | 90.03% |
| September | 98.28% | 90.38% |
| October | 97.80% | 95.52% |
§ 03
Cite as
APA
Click to copy
BibTeX
Click to copy
ID: policy-eventual-success-trend-jan-october-2026·Updated November 11, 2026·Period Jan 2026 to Oct 2026