api_reporter
- api_reporter
- JIRAUSER761370
- America/Los_Angeles
- Yes
- No
WEB-6638The rate-limit on https://api.mojang.com/ is currently 10 requests per minute (absolute time, not relative to the last request). A lot of applications that rely on the API having a limit of 600 requests per 10 minutes are having issues. The rate-limit was normal 3 days ago, but has unexpectedly dropped since then.
The https://sessionserver.mojang.com/ subdomain appears to be unaffected.
The rate-limit on https://api.mojang.com/ is currently 10 requests per minute
(absolute time, not relative to the last request). A lot of applications that rely on the API having a limit of 600 requests per 10 minutes are having issues.The rate-limit was normal 3 days ago, but has unexpectedly dropped since then.The https://sessionserver.mojang.com/ subdomain appears to be unaffected.
The rate-limit on https://api.mojang.com/ is currently 10 requests per minute. A lot of applications that rely on the API having a limit of 600 requests per 10 minutes are having issues.
- The rate-limit was normal 3 days ago, but has unexpectedly dropped since then
- The https://sessionserver.mojang.com/ subdomain appears to be unaffected
[URGENT] Rate Limit Decreased
The rate limit used to be 600 requests per 10 minutes. The issue started 2 days ago and has caused problems in numerous applications.
The rate limit is now 60 requests per minute. I guess this can be marked as resolved now?
I'd like to add a little more information to this issue.
The bug seems to occur when many requests are made in a short period of time, even when less than 60 (the expected rate limit) requests were made. For example, a leaderboard project trying to get 50 usernames from their UUID, with fast internet and 0 delays added to the code, causes an unexpected 429 status code.
The second rate limit is similar to this old issue.