Skip to content

Add user + team based multi-instance rate limiting#10497

Merged
3 commits merged intomainfrom
litellm_dev_05_01_2025_p3
May 2, 2025
Merged

Add user + team based multi-instance rate limiting#10497
3 commits merged intomainfrom
litellm_dev_05_01_2025_p3

Conversation

@ghost
Copy link
Copy Markdown

@ghost ghost commented May 2, 2025

Title

Add user + team based multi-instance rate limiting

Relevant issues

Closes #10052

Pre-Submission checklist

Please complete all items before asking a LiteLLM maintainer to review your PR

  • I have Added testing in the tests/litellm/ directory, Adding at least 1 test is a hard requirement - see details
  • I have added a screenshot of my new test passing locally
  • My PR passes all unit tests on make test-unit
  • My PR's scope is as isolated as possible, it only solves 1 specific problem

Type

🆕 New Feature

Changes

@vercel
Copy link
Copy Markdown

vercel Bot commented May 2, 2025

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
litellm ✅ Ready (Inspect) Visit Preview 💬 Add feedback May 2, 2025 5:01am

@ghost ghost merged commit 132bdb1 into main May 2, 2025
31 of 44 checks passed
@ghost ghost deleted the litellm_dev_05_01_2025_p3 branch May 2, 2025 05:26
@harvardfly
Copy link
Copy Markdown

The latest version 1.68.0 seems to still have this issue, with the multi-instance rate limiting not working properly. @krrishdholakia

This pull request was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Issues with Key-Level Model Limits (TPM/RPM/Budget) Enforcement and Router Fallback (DB Mode, Enterprise)

1 participant