Requesty
Data/Reliability and ops

Provider error code distribution, April 2026

Provider error code distribution, April 2026

Status codes returned by upstream providers on failed responses (router- and gateway-level rejections excluded).

Auth / quotaClient errorServer errorGateway / timeoutNot found
429 (rate limit), 400 (bad request), and 403 (forbidden) account for ~95% of provider-returned errors. Real provider availability incidents (5xx) are under 5%.Source: Requesty production gateway. April 2026, status_code_origin = provider, successful = false.

Why do LLM provider requests fail? Among April 2026 requests on the Requesty gateway where the upstream provider returned a non-success response, 65.8% were 429 (rate limit), 19.4% were 400 (bad request: schema mismatches, oversized payloads), and 9.4% were 403 (forbidden). 5xx availability incidents (503, 502, 529, 500, 504, 520) summed to ~4.8%. Router- and gateway-level rejections are filtered out so the chart shows only what providers themselves emit when they fail.

Why it mattersProvider failures are dominated by rate-limiting under agentic load, not by genuine availability incidents. That changes the right mitigation: backoff plus a managed fallback chain absorbs the ~85% of failures that are 429 + 400 without provider changes; only the ~5% 5xx tail is irreducible. Designing retries on the assumption that "providers go down" misallocates engineering effort.

Period
Apr 2026
Updated
May 9, 2026
ID
status-codes-april-2026
§ 01

Key findings

  • 01429 (rate limit) is the dominant provider failure mode at 65.8%. Providers throttle agentic workloads aggressively.
  • 02400 (bad request) is second at 19.4%. Schema mismatches, unsupported parameters, oversized payloads.
  • 03403 (forbidden) at 9.4%. Provider-side authorization, region, or model-access denials.
  • 045xx total (503, 502, 529, 500, 504, 520) sums to ~4.8%. Real provider availability incidents are uncommon but not zero.
  • 05Codes that disappear under this filter (404 collapses from 29.8% to 0.2%, 402 from 17.8% to 0.07%) confirm those rejections are router-level model-not-found and billing checks, not provider failures.
§ 02

Data

Status codeDescriptionBucket% of rejections(percent)
429Too Many Requestsauth_quota65.83%
400Bad Requestclient_error19.40%
403Forbiddenauth_quota9.41%
503Service Unavailableserver_error2.19%
502Bad Gatewaygateway1.81%
529Site Overloadedserver_error0.52%
422Unprocessableclient_error0.24%
500Internal Serverserver_error0.21%
404Not Foundnot_found0.21%
402Payment Requiredauth_quota0.07%
504Gateway Timeoutgateway0.06%
401Unauthorizedauth_quota0.02%
520Cloudflare Unknownserver_error0.02%
499Client Closedclient_error0.01%
§ 03

Cite as

APA
Click to copy
BibTeX
Click to copy
ID: status-codes-april-2026·Updated May 9, 2026·Period Apr 2026