We see 429 errors on this URL, even when limit is not reached. We get the too many requests error, 5 seconds later there is no error and 5 more seconds the connection is blocked with the error again.
Comments 7
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.
Even with only 1 request made in last 10 minutes, you can get 429 error. You can use bulk api to get up to 10 names at once, but this is global error with api going for at least couple of days.
I seem to be able to see this API point now without issue. Can you see if the error still occurs for you? And if so please can you attach a video showcasing it?
This 429 error I didn't see today, but there were some time outs or different errors. It may not happen today, but maybe it will happen again.
?