# LLM API Error Fixes

TL;DR: llmping publishes developer-focused fix pages for high-intent LLM API errors.

- [OpenAI API Error 429: Rate Limit or Quota Exceeded](/errors/openai/429/): OpenAI API 429 usually means your request is being rate limited, your quota is exhausted, or your project has hit a per-minute token/request cap.
- [Anthropic API 529: Overloaded Error](/errors/anthropic/529/): Anthropic API 529 means the provider is overloaded or temporarily unable to serve your request at normal capacity.
- [OpenAI API 401: Invalid API Key](/errors/openai/401/): OpenAI API 401 means the API key is missing, malformed, revoked, or not valid for the project you are calling from.
- [OpenAI API 403: Forbidden or Model Access Denied](/errors/openai/403/): OpenAI API 403 means the key is recognized but the account, project, model, region, or policy does not allow the requested operation.
- [Gemini API Fetch Failed: Network, CORS, or Endpoint Issue](/errors/gemini/fetch-failed/): Gemini API fetch failed usually means your runtime could not complete the HTTP request because of network, CORS, DNS, endpoint, or key placement problems.
- [Claude API ECONNRESET: Connection Reset During Request](/errors/claude/econnreset/): Claude API ECONNRESET means the TCP connection was closed unexpectedly by a peer, proxy, runtime, or network path before the response completed.
- [OpenRouter 402: Insufficient Credits](/errors/openrouter/402/): OpenRouter 402 means the request cannot be billed because the account lacks credits, has a payment issue, or is blocked by spend controls.
