LiteLLM / LiteLLM

LiteLLM BudgetExceededError Phantom Redis Counter Inflation Blocks Production Users

Fix phantom BudgetExceededError caused by leaking Redis spend counters in LiteLLM proxy — real database spend near $0 but users blocked at budget limit Includes evidence for LiteLLM troubleshooting demand.

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

Category: LiteLLM
Error signature: Budget has been exceeded! EndUser=<id> Current cost: $52.19, Max budget: $50.0 — DB spend shows $0.001 while Redis counter reports $52 (BudgetExceededError HTTP 429)
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

Budget has been exceeded! EndUser=<id> Current cost: $52.19, Max budget: $50.0 — DB spend shows $0.001 while Redis counter reports $52 (BudgetExceededError HTTP 429) is a LiteLLM failure pattern reported for developers trying to fix phantom budgetexceedederror caused by leaking redis spend counters in litellm proxy — real database spend near $0 but users blocked at budget limit. 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 in BerriAI/litellm by nkhanpa-art (May 11, 2026). Reserve→finalize pipeline gap leaves orphaned budget reservations in Redis. With 4 replicas on EKS + Redis, ~6000+ end users hit intermittent 429 BudgetExceededError cycling every ~4 minutes. Cross-linked issue #28283 reports similar phantom inflation on v1.83.14-stable independent of the reservation feature. Official collaborator maltbae confirmed race condition hypothesis. Category: LiteLLM — proxy billing system bug affecting thousands of paying LLM proxy users.

Common causes

GitHub issue #27639 in BerriAI/litellm by nkhanpa-art (May 11, 2026). Reserve→finalize pipeline gap leaves orphaned budget reservations in Redis. With 4 replicas on EKS + Redis, ~6000+ end users hit intermittent 429 BudgetExceededError cycling every ~4 minutes. Cross-linked issue #28283 reports similar phantom inflation on v1.83.14-stable independent of the reservation feature. Official collaborator maltbae confirmed race condition hypothesis. Category: LiteLLM — proxy billing system bug affecting thousands of paying LLM proxy users.

Quick fixes

Confirm the exact error signature matches Budget has been exceeded! EndUser=<id> Current cost: $52.19, Max budget: $50.0 — DB spend shows $0.001 while Redis counter reports $52 (BudgetExceededError HTTP 429).
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 Budget has been exceeded! EndUser=<id> Current cost: $52.19, Max budget: $50.0 — DB spend shows $0.001 while Redis counter reports $52 (BudgetExceededError HTTP 429) 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 Budget has been exceeded! EndUser=<id> Current cost: $52.19, Max budget: $50.0 — DB spend shows $0.001 while Redis counter reports $52 (BudgetExceededError HTTP 429) mean in LiteLLM?

Budget has been exceeded! EndUser=<id> Current cost: $52.19, Max budget: $50.0 — DB spend shows $0.001 while Redis counter reports $52 (BudgetExceededError HTTP 429) indicates the workflow described by "LiteLLM BudgetExceededError Phantom Redis Counter Inflation Blocks Production Users" failed in a LiteLLM context. Start by confirming the exact signature and the component that emitted it.

What should I check first for Budget has been exceeded! EndUser=<id> Current cost: $52.19, Max budget: $50.0 — DB spend shows $0.001 while Redis counter reports $52 (BudgetExceededError HTTP 429)?

Check whether this cause matches your environment: GitHub issue #27639 in BerriAI/litellm by nkhanpa-art (May 11, 2026). Reserve→finalize pipeline gap leaves orphaned budget reservations in Redis. With 4 replicas on EKS + Redis, ~6000+ end users hit intermittent 429 BudgetExceededError cycling every ~4 minutes. Cross-linked issue #28283 reports similar phantom inflation on v1.83.14-stable independent of the reservation feature. Official collaborator maltbae confirmed race condition hypothesis. Category: LiteLLM — proxy billing system bug affecting thousands of paying LLM proxy users.

Is the Budget has been exceeded! EndUser=<id> Current cost: $52.19, Max budget: $50.0 — DB spend shows $0.001 while Redis counter reports $52 (BudgetExceededError HTTP 429) guidance source-backed?

The "LiteLLM BudgetExceededError Phantom Redis Counter Inflation Blocks Production Users" 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 Budget has been exceeded! EndUser=<id> Current cost: $52.19, Max budget: $50.0 — DB spend shows $0.001 while Redis counter reports $52 (BudgetExceededError HTTP 429)?

For "LiteLLM BudgetExceededError Phantom Redis Counter Inflation Blocks Production Users", 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 Budget has been exceeded! EndUser=<id> Current cost: $52.19, Max budget: $50.0 — DB spend shows $0.001 while Redis counter reports $52 (BudgetExceededError HTTP 429)?

For "LiteLLM BudgetExceededError Phantom Redis Counter Inflation Blocks Production Users", 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.