Hi, there have been some issues with Captch that should now have been resolved. Can you try again and also add the bug id to the title of your support ticket so that we can search for that? That is "WEB-6674".
Looking at metrics and testing myself I can see that the API is not down. But clearly you got a 500 response. Is this still a problem for you? It's hard to see why without more information. But you can't share any privacy/identifiable information here as this is public. You would have to open a support case with our support.
Yes, there was a bug that set the rate limit to low. It has now been set to 60/min. Marked it as resolved.
Ok I will close this for now. If the problem arises again. Please open a new bug. Thanks!
This should now be fixed.
Hi, thanks for reporting this issue. Are you still experiencing this problem?
Thanks for the report. We are working on a fix for this.
Hi, we did revert a change this morning to make it so the bigger loss of heads and textures are fixed again. We are aware of this bug and are working to solve it with an upcoming change.
Hi, we have tested this and there are no general problem with emails made up off numbers. You should contact support to see if there are a suppression or problem with delivery to your specific email. You can reach out to them with this form: https://help.minecraft.net/hc/en-us/requests/new?ticket_form_id=360001225811
Closing this bug.
Had a graphical designer look at this and this is intended. So this will be closed as works as intended.
Is this still a problem?
This should be fixed now.
Please contact support if this is still a problem: https://help.minecraft.net/hc/en-us/requests/new
Please contact Mojang support. if this is still a problem.
Closing as invalid.
This should be fixed now.
Please report a support case with your IP here: https://help.minecraft.net/hc/en-us/requests/new
This was because we had some problems with backend servers at this time. That has been resolved. if you still have problems with this, please report a support case: https://help.minecraft.net/hc/en-us/requests/new
There was a minor fix on that API to make it so that a parse error of the xtoken does not become a 500 but rather a 401. Your app needs to be registered also but that should give a 403 if that were detected. So I think you are still having problems with the xsts token.