Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Automatically impose usage limit on clients which receive numerous 429 responses #553

Open
hburn7 opened this issue Dec 5, 2024 · 0 comments
Labels
project:API Items related to the API project proposal type:feature

Comments

@hburn7
Copy link
Collaborator

hburn7 commented Dec 5, 2024

If an API client continuously fails to abide by rate limits, block them from accessing the service.

Proposal

  • Block users from generating new clients if any of their clients is on 'cooldown'
  • Gradually increase the period by which a client cannot access the service should a 429 error be delivered (perhaps there's an in-memory dictionary containing ids of clients which are being ratelimited, and after 5 or so of these errors we start blocking access?)
    • i.e. 5 minutes of wait time, 10 minutes, 30 minutes, 60 minutes, etc. until their access is permanently revoked.

Questions

  • Is there already a defined standard for the process of blocking access to the service if abuse is detected?
@hburn7 hburn7 added type:feature proposal project:API Items related to the API project labels Dec 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
project:API Items related to the API project proposal type:feature
Projects
None yet
Development

No branches or pull requests

1 participant