Skip to content

chore: also reference error rate limit and Monolith rate limit #246

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.

Sign up for GitHub

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

Merged
fc-pinky merged 1 commit into from
Nov 18, 2025
Merged

chore: also reference error rate limit and Monolith rate limit #246

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 11 additions & 0 deletions docs/services/esi/rate-limiting.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -12,6 +12,17 @@ In most cases you should be fine with far less requests than the rate limit allo
Rate limiting isn't active on all routes yet.
Check the OpenAPI Specs or the HTTP response headers for up-to-date information.

!!! warning

For routes that do not have this new rate limiting enabled, there is still an older "error rate limit" active.
This allows at most 100 non-2xx/3xx responses per minute. After that, it will return 420s on all ESI routes, even those with the new rate limiting enabled.

!!! important

Some routes also have a rate limiter deep in EVE Server code.
This can also cause 429s to be returned, without the rate limiter headers indicating why.
We are working on deprecating these, but in the mean time, be aware this can be the case.

## Floating Window

A floating window is a mathematical approximation where tokens consumed by a request are released back to your bucket after the window size has passed.
Expand Down