LiteLLM / LiteLLM

LiteLLM reserve_budget_for_request() Leaks Redis Spend Counters Causing Phantom BudgetExceededError

Fix phantom BudgetExceededError in LiteLLM proxy caused by Redis spend counter leaks; end users randomly blocked despite being within budget limits Includes evidence for LiteLLM troubleshooting demand.

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

Category: LiteLLM
Error signature: BudgetExceededError (HTTP 429): "Budget has been exceeded! EndUser=<id> Current cost: <inflated>, Max budget: 50.0" — DB spend shows $0.001 while Redis counter reports $50+ after ~4 min of normal traffic
Quick fix: Compare the failing environment with a known working setup, then change one configuration value at a time.
Updated: May 20, 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

BudgetExceededError (HTTP 429): "Budget has been exceeded! EndUser=<id> Current cost: <inflated>, Max budget: 50.0" — DB spend shows $0.001 while Redis counter reports $50+ after ~4 min of normal traffic is a LiteLLM failure pattern reported for developers trying to fix phantom budgetexceedederror in litellm proxy caused by redis spend counter leaks; end users randomly blocked despite being within budget limits. Based on the imported evidence, treat this as a tool-specific troubleshooting page rather than a generic API error.

Why this happens

GitHub Issue #27639 (BerriAI/litellm) opened May 11 2026 by nkhanpa-art, 5+ comments still open. Production deployment with 6000+ end users, 4 replicas on Kubernetes EKS, Redis cache enabled. Bug introduced in v1.83.10 dev branch. root cause: reserve_budget_for_request() atomically increments Redis counter but _finalize_budget_reservation() fails silently on error path leaving phantom reservations. Multiple confirmations of same issue by devdev999 (Litellm contributor), maltbae provided detailed race condition analysis and workaround, psarma89 cross-linked related issue #28283 showing same symptom independent of reservation feature.

Common causes

GitHub Issue #27639 (BerriAI/litellm) opened May 11 2026 by nkhanpa-art, 5+ comments still open. Production deployment with 6000+ end users, 4 replicas on Kubernetes EKS, Redis cache enabled. Bug introduced in v1.83.10 dev branch. root cause: reserve_budget_for_request() atomically increments Redis counter but _finalize_budget_reservation() fails silently on error path leaving phantom reservations. Multiple confirmations of same issue by devdev999 (Litellm contributor), maltbae provided detailed race condition analysis and workaround, psarma89 cross-linked related issue #28283 showing same symptom independent of reservation feature.

Quick fixes

Confirm the exact error signature matches BudgetExceededError (HTTP 429): "Budget has been exceeded! EndUser=<id> Current cost: <inflated>, Max budget: 50.0" — DB spend shows $0.001 while Redis counter reports $50+ after ~4 min of normal traffic.
Check the LiteLLM account, local tool state, and provider configuration involved in the failing workflow.
Compare the failing environment with a known working setup, then change one configuration value at a time.

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 BudgetExceededError (HTTP 429): "Budget has been exceeded! EndUser=<id> Current cost: <inflated>, Max budget: 50.0" — DB spend shows $0.001 while Redis counter reports $50+ after ~4 min of normal traffic 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 BudgetExceededError (HTTP 429): "Budget has been exceeded! EndUser=<id> Current cost: <inflated>, Max budget: 50.0" — DB spend shows $0.001 while Redis counter reports $50+ after ~4 min of normal traffic mean in LiteLLM?

BudgetExceededError (HTTP 429): "Budget has been exceeded! EndUser=<id> Current cost: <inflated>, Max budget: 50.0" — DB spend shows $0.001 while Redis counter reports $50+ after ~4 min of normal traffic indicates the workflow described by "LiteLLM reserve_budget_for_request() Leaks Redis Spend Counters Causing Phantom BudgetExceededError" failed in a LiteLLM context. Start by confirming the exact signature and the component that emitted it.

What should I check first for BudgetExceededError (HTTP 429): "Budget has been exceeded! EndUser=<id> Current cost: <inflated>, Max budget: 50.0" — DB spend shows $0.001 while Redis counter reports $50+ after ~4 min of normal traffic?

Check whether this cause matches your environment: GitHub Issue #27639 (BerriAI/litellm) opened May 11 2026 by nkhanpa-art, 5+ comments still open. Production deployment with 6000+ end users, 4 replicas on Kubernetes EKS, Redis cache enabled. Bug introduced in v1.83.10 dev branch. root cause: reserve_budget_for_request() atomically increments Redis counter but _finalize_budget_reservation() fails silently on error path leaving phantom reservations. Multiple confirmations of same issue by devdev999 (Litellm contributor), maltbae provided detailed race condition analysis and workaround, psarma89 cross-linked related issue #28283 showing same symptom independent of reservation feature.

Is the BudgetExceededError (HTTP 429): "Budget has been exceeded! EndUser=<id> Current cost: <inflated>, Max budget: 50.0" — DB spend shows $0.001 while Redis counter reports $50+ after ~4 min of normal traffic guidance source-backed?

The "LiteLLM reserve_budget_for_request() Leaks Redis Spend Counters Causing Phantom BudgetExceededError" 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 BudgetExceededError (HTTP 429): "Budget has been exceeded! EndUser=<id> Current cost: <inflated>, Max budget: 50.0" — DB spend shows $0.001 while Redis counter reports $50+ after ~4 min of normal traffic?

For "LiteLLM reserve_budget_for_request() Leaks Redis Spend Counters Causing Phantom BudgetExceededError", avoid applying "Compare the failing environment with a known working setup, then change one configuration value at a time." 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 BudgetExceededError (HTTP 429): "Budget has been exceeded! EndUser=<id> Current cost: <inflated>, Max budget: 50.0" — DB spend shows $0.001 while Redis counter reports $50+ after ~4 min of normal traffic?

For "LiteLLM reserve_budget_for_request() Leaks Redis Spend Counters Causing Phantom BudgetExceededError", 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.