06 / Reliability
Most failed requests still got served.
In week 45 (Nov 2 to 8, 2026), 86.5% of requests on a fallback policy whose first attempt hit a provider error were still served by another host on the Requesty gateway; 94.5% of those rescues served the same model.
A provider error only reaches your users when there is nowhere else to send the request. With a fallback policy, most failed first attempts were answered by the same model on another host.
Set up a fallback policy →- Value
- 86.5% of requests on a fallback policy whose first host returned a provider error
- Period
- Nov 2 to 8, 2026 (UTC)
- Compared with
- Oct 26 to Nov 1, 2026
- Source
- Requesty gateway, shares, rates, ranks and latency only

Share
Post this finding
When a request's first host failed on Requesty last week, a fallback policy still got it served 86.5% of the time (Nov 2 to 8). Latency policies: 82.5%. 94.5% of rescues served the same model from another host. requesty.ai/data/weekly/2026-w45/rescues

On desktop: copy the image, open X, paste. The text is filled in for you. On a phone, Share sends the image and text to the app in one go.
| Measure | Value |
|---|---|
| Served by another host | 86.5% |
| Still failed | 13.5% |
| Fallback policy | 86.5% |
| Latency policy | 82.5% |
| Same model served | 94.5% |
More from week 45
New charts every Monday
Follow by RSS →For agents
- Markdown
- /data/weekly/2026-w45/data.md
- Latest
- /data/weekly/latest.json
- llms.txt
- /data/weekly/llms.txt
# Any week URL returns Markdown when asked for it
curl -H "Accept: text/markdown" \
https://www.requesty.ai/data/weekly/2026-w45





