mojira.dev
WEB-7008

Increased Rate of HTTP 429 Errors in API Endpoints Since March 17 2024

I am a developer working on a custom Minecraft software that relies on the following Mojang API endpoints for player connections and plugin functionality:

  • GET: [https://api.mojang.com/users/profiles/minecraft/{username}|https://api.mojang.com/users/profiles/minecraft/Jcolesandwich]

  • POST: [https://api.mojang.com/profiles/minecraft]

Beginning March 17 2024, we have observed a significant increase in the frequency of HTTP 429 (Too Many Requests) errors. Approximately 6-7% of our requests are now returning these errors. This is particularly concerning as our current rate of requests is well below the expected rate limits; we make an average of only five UUID requests per hour.

Attached is a screenshot displaying the error rates over the relevant days. This documentation clearly shows the unusual increase in rate-limiting responses, which is affecting the stability of our software.

Questions:

  1. Is there a change in the rate-limiting policies on Mojang's APIs that could explain this increase in 429 errors?

  2. Could there be an issue with how rate limits are being enforced for these endpoints?

  3. What steps can be taken to resolve this issue, ensuring consistent access to the API at the current request rate?

We appreciate any guidance or solutions Mojang can provide to help us address this issue.

Attachments

Comments 3

Hi, first off could you try switching over to these two endpoints?

GET api.minecraftservices.com/minecraft/profile/lookup/name/{name}
POST api.minecraftservices.com/minecraft/profile/lookup/bulk/byname

Is your server deployed on a shared VPS? In some cases these will also share IPs which could cause you to hit rate limits without doing anything maliciously yourself.

We are currently utilizing a dedicated server from OVH. Additionally, we have attempted to utilize different external IP addresses for API requests in completely different subnets and have still encountered the issue.

 

We will attempt to utilize the API endpoints you have provided and see if it resolves the issue.

 

I’ll report back with my findings.

Since implementing the new API endpoint URLs, we haven’t experienced any API errors.

 

Due to the instability of the old endpoints Mojang should either disable them or make them more stable however.

 

I would still consider this as a valid bug/ticket until the old endpoints get fixed or removed.

Rhys B

(Unassigned)

API

Retrieved