LiteLLM / LiteLLM

LiteLLM Router-Side Rate-Limit Errors Mislabelled as Vendor Rate Limit Instead of litellm_rate_limit

Fix LiteLLM rate-limit categorization so router-side deployment throttling is properly labelled for correct dashboard attribution and alerting routing Includes evidence for LiteLLM troubleshooting demand.

Source-backed Last updated May 22, 2026 1 source Needs local verification

Category: LiteLLM
Error signature: Deployment over defined rpm limit / Deployment over defined tpm limit — dashboard/callbacks attribute these to upstream vendor (VENDOR_RATE_LIMIT) instead of LiteLLM router (LITELLM_RATE_LIMIT)
Quick fix: Reduce request pressure, check quota or plan limits, and retry with backoff instead of immediate repeated requests.
Updated: May 22, 2026
Verification status: Source-backed
Evidence: 1 public source URL

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

Deployment over defined rpm limit / Deployment over defined tpm limit — dashboard/callbacks attribute these to upstream vendor (VENDOR_RATE_LIMIT) instead of LiteLLM router (LITELLM_RATE_LIMIT) is a LiteLLM failure pattern reported for developers trying to fix litellm rate-limit categorization so router-side deployment throttling is properly labelled for correct dashboard attribution and alerting routing. Based on the imported evidence, treat this as a tool-specific troubleshooting page rather than a generic API error.

Why this happens

GitHub PR #27708 in BerriAI/litellm identifies that PR #27687 made RateLimitError default category be VENDOR_RATE_LIMIT, causing router-side raises in lowest_tpm_rpm_v2.py (5 instances) and model_rate_limit_check.py (4 instances) to silently misattribute themselves as vendor errors. This breaks dashboards and callback-based alerting that rely on error categories to split litellm-side vs. vendor-side throttles. All 9 raises previously emitted category=vendor_rate_limit; fix makes them emit litellm_rate_limit with correct rate_limit_type. Impacts enterprise LiteLLM proxy operators monitoring rate limits. Category mapping: LiteLLM (proxy/routing layer error affecting commercial deployments).

Common causes

GitHub PR #27708 in BerriAI/litellm identifies that PR #27687 made RateLimitError default category be VENDOR_RATE_LIMIT, causing router-side raises in lowest_tpm_rpm_v2.py (5 instances) and model_rate_limit_check.py (4 instances) to silently misattribute themselves as vendor errors. This breaks dashboards and callback-based alerting that rely on error categories to split litellm-side vs. vendor-side throttles. All 9 raises previously emitted category=vendor_rate_limit; fix makes them emit litellm_rate_limit with correct rate_limit_type. Impacts enterprise LiteLLM proxy operators monitoring rate limits. Category mapping: LiteLLM (proxy/routing layer error affecting commercial deployments).

Quick fixes

Confirm the exact error signature matches Deployment over defined rpm limit / Deployment over defined tpm limit — dashboard/callbacks attribute these to upstream vendor (VENDOR_RATE_LIMIT) instead of LiteLLM router (LITELLM_RATE_LIMIT).
Check the LiteLLM account, local tool state, and provider configuration involved in the failing workflow.
Reduce request pressure, check quota or plan limits, and retry with backoff instead of immediate repeated requests.

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 Deployment over defined rpm limit / Deployment over defined tpm limit — dashboard/callbacks attribute these to upstream vendor (VENDOR_RATE_LIMIT) instead of LiteLLM router (LITELLM_RATE_LIMIT) 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 Deployment over defined rpm limit / Deployment over defined tpm limit — dashboard/callbacks attribute these to upstream vendor (VENDOR_RATE_LIMIT) instead of LiteLLM router (LITELLM_RATE_LIMIT) mean in LiteLLM?

Deployment over defined rpm limit / Deployment over defined tpm limit — dashboard/callbacks attribute these to upstream vendor (VENDOR_RATE_LIMIT) instead of LiteLLM router (LITELLM_RATE_LIMIT) indicates the workflow described by "LiteLLM Router-Side Rate-Limit Errors Mislabelled as Vendor Rate Limit Instead of litellm_rate_limit" failed in a LiteLLM context. Start by confirming the exact signature and the component that emitted it.

What should I check first for Deployment over defined rpm limit / Deployment over defined tpm limit — dashboard/callbacks attribute these to upstream vendor (VENDOR_RATE_LIMIT) instead of LiteLLM router (LITELLM_RATE_LIMIT)?

Check whether this cause matches your environment: GitHub PR #27708 in BerriAI/litellm identifies that PR #27687 made RateLimitError default category be VENDOR_RATE_LIMIT, causing router-side raises in lowest_tpm_rpm_v2.py (5 instances) and model_rate_limit_check.py (4 instances) to silently misattribute themselves as vendor errors. This breaks dashboards and callback-based alerting that rely on error categories to split litellm-side vs. vendor-side throttles. All 9 raises previously emitted category=vendor_rate_limit; fix makes them emit litellm_rate_limit with correct rate_limit_type. Impacts enterprise LiteLLM proxy operators monitoring rate limits. Category mapping: LiteLLM (proxy/routing layer error affecting commercial deployments).

Is the Deployment over defined rpm limit / Deployment over defined tpm limit — dashboard/callbacks attribute these to upstream vendor (VENDOR_RATE_LIMIT) instead of LiteLLM router (LITELLM_RATE_LIMIT) guidance source-backed?

The "LiteLLM Router-Side Rate-Limit Errors Mislabelled as Vendor Rate Limit Instead of litellm_rate_limit" page is labeled source-backed. It has 1 public source URL from github.com, so use that evidence status when deciding how much additional verification you need.

When should I avoid the quick fix for Deployment over defined rpm limit / Deployment over defined tpm limit — dashboard/callbacks attribute these to upstream vendor (VENDOR_RATE_LIMIT) instead of LiteLLM router (LITELLM_RATE_LIMIT)?

For "LiteLLM Router-Side Rate-Limit Errors Mislabelled as Vendor Rate Limit Instead of litellm_rate_limit", avoid applying "Reduce request pressure, check quota or plan limits, and retry with backoff instead of immediate repeated requests." 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 Deployment over defined rpm limit / Deployment over defined tpm limit — dashboard/callbacks attribute these to upstream vendor (VENDOR_RATE_LIMIT) instead of LiteLLM router (LITELLM_RATE_LIMIT)?

For "LiteLLM Router-Side Rate-Limit Errors Mislabelled as Vendor Rate Limit Instead of litellm_rate_limit", 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.