LiteLLM / LiteLLM

LiteLLM 1.82.1 OpenRouter Model IDs No Longer Working

After upgrading to LiteLLM 1.82.1, previously working OpenRouter model IDs throw 404 errors. Users proxying through LiteLLM proxy lose access to OpenRouter models and need quick workaround to restore routing to healthy deployments. Includes evidence for LiteLLM troubleshooting demand.

Source-backed Last updated June 10, 2026 3 sources Needs local verification

Category: LiteLLM
Error signature: litellm.CallFailed: Error code: 404 — OpenRouter model IDs stopped working after LiteLLM upgrade to v1.82.1
Quick fix: Check the build output, project root, and deployment platform configuration before redeploying.
Updated: June 10, 2026
Verification status: Source-backed
Evidence: 3 public source URLs

Before you change production

This page includes public source URLs in the imported troubleshooting record. Compare those references with your version and environment before applying changes.

Reproduce the smallest failing action and save non-secret logs before changing configuration.
Check versions for LiteLLM, related SDKs, package managers, CI runners, and hosting providers.
Change one setting or dependency at a time, then rerun the same failing command or request.
Avoid destructive commands, credential rotation, billing changes, or security relaxations without a rollback plan.

What this error means

litellm.CallFailed: Error code: 404 — OpenRouter model IDs stopped working after LiteLLM upgrade to v1.82.1 is a LiteLLM failure pattern reported for developers trying to after upgrading to litellm 1.82.1, previously working openrouter model ids throw 404 errors. users proxying through litellm proxy lose access to openrouter models and need quick workaround to restore routing to healthy deployments.. Based on the imported evidence, treat this as a tool-specific troubleshooting page rather than a generic API error.

Why this happens

GitHub issue #22667 on BerriAI/litellm: 'LiteLLM 1.82.1 OpenRouter Model IDs no longer working'. Regression introduced in v1.82.1 breaking proxy routes to OpenRouter. Related: issue #24795 'OpenRouter model selected from Admin UI list fails Test Connect with is not a valid model ID'. Also issue #27362 'APIConnectionError hardcoded in cooldown_handlers.py prevents failover to healthy deployments'. These are all regression-style bugs affecting paying users who route production traffic through LiteLLM. Category: LiteLLM.

Common causes

GitHub issue #22667 on BerriAI/litellm: 'LiteLLM 1.82.1 OpenRouter Model IDs no longer working'. Regression introduced in v1.82.1 breaking proxy routes to OpenRouter. Related: issue #24795 'OpenRouter model selected from Admin UI list fails Test Connect with is not a valid model ID'. Also issue #27362 'APIConnectionError hardcoded in cooldown_handlers.py prevents failover to healthy deployments'. These are all regression-style bugs affecting paying users who route production traffic through LiteLLM. Category: LiteLLM.

Quick fixes

Confirm the exact error signature matches litellm.CallFailed: Error code: 404 — OpenRouter model IDs stopped working after LiteLLM upgrade to v1.82.1.
Check the LiteLLM account, local tool state, and provider configuration involved in the failing workflow.
Check the build output, project root, and deployment platform configuration before redeploying.

Platform/tool-specific checks

Verify the command, editor, extension, or API client that produced the error.
Compare local settings with CI, deployment, or editor-level settings when the error appears in only one environment.
Avoid deleting credentials, local model data, or project settings until the failing scope is clear.

Step-by-step troubleshooting

Capture the exact error message and the command, editor action, or request that triggered it.
Check whether the failure is account/auth, quota/rate, model/provider, local runtime, or deployment configuration.
Review the source evidence below and compare it with your environment.
Apply one change at a time and rerun the smallest failing action.
Keep the working fix documented for the team or deployment environment.

How to prevent it

Keep provider/tool configuration documented.
Record non-secret diagnostics such as tool version, provider name, model name, and command path.
Add a lightweight check before CI or production workflows depend on the tool.

Diagnostic flow for this page

Match litellm.CallFailed: Error code: 404 — OpenRouter model IDs stopped working after LiteLLM upgrade to v1.82.1 exactly before applying the quick fix.
Compare the failing environment with LiteLLM versions, account scope, provider settings, and deployment context.
Check the listed common causes in order, starting with the cause that best matches your logs.
Use the evidence status below to decide whether to confirm against public sources or official documentation.
Apply one reversible change, rerun the smallest failing action, and keep rollback notes.

FAQ

What does litellm.CallFailed: Error code: 404 — OpenRouter model IDs stopped working after LiteLLM upgrade to v1.82.1 mean in LiteLLM?

litellm.CallFailed: Error code: 404 — OpenRouter model IDs stopped working after LiteLLM upgrade to v1.82.1 indicates the workflow described by "LiteLLM 1.82.1 OpenRouter Model IDs No Longer Working" failed in a LiteLLM context. Start by confirming the exact signature and the component that emitted it.

What should I check first for litellm.CallFailed: Error code: 404 — OpenRouter model IDs stopped working after LiteLLM upgrade to v1.82.1?

Check whether this cause matches your environment: GitHub issue #22667 on BerriAI/litellm: 'LiteLLM 1.82.1 OpenRouter Model IDs no longer working'. Regression introduced in v1.82.1 breaking proxy routes to OpenRouter. Related: issue #24795 'OpenRouter model selected from Admin UI list fails Test Connect with is not a valid model ID'. Also issue #27362 'APIConnectionError hardcoded in cooldown_handlers.py prevents failover to healthy deployments'. These are all regression-style bugs affecting paying users who route production traffic through LiteLLM. Category: LiteLLM.

Is the litellm.CallFailed: Error code: 404 — OpenRouter model IDs stopped working after LiteLLM upgrade to v1.82.1 guidance source-backed?

The "LiteLLM 1.82.1 OpenRouter Model IDs No Longer Working" page is labeled source-backed. It has 3 public source URLs from github.com, so use that evidence status when deciding how much additional verification you need.

When should I avoid the quick fix for litellm.CallFailed: Error code: 404 — OpenRouter model IDs stopped working after LiteLLM upgrade to v1.82.1?

For "LiteLLM 1.82.1 OpenRouter Model IDs No Longer Working", avoid applying "Check the build output, project root, and deployment platform configuration before redeploying." when the error text differs, the affected version or provider is different, or the change would touch credentials, billing, DNS, production deploy settings, or irreversible data.

What should I collect before debugging litellm.CallFailed: Error code: 404 — OpenRouter model IDs stopped working after LiteLLM upgrade to v1.82.1?

For "LiteLLM 1.82.1 OpenRouter Model IDs No Longer Working", collect the failing LiteLLM command or request, non-secret configuration, versions, timestamps, request IDs when available, and the smallest reproduction that still triggers the signature.