When trying to login in to Minecraft using any number of launchers, including the official Minecraft launcher, the login fails. When trying with the Modrinth launcher, a bit more detail is provided and I can see that the error is generated by an HTTP 429 response from the Minecraft API. I confirmed that the official Minecraft launcher generates the same error using Wireshark, where I observed that the Minecraft/Mojang API sent a TCP RST as well.
This issue began last weekend, around 1/11/2026, and has persisted almost the entire time since. I’ve waited hours, even overnight, and still come back to an HTTP 429 (too many requests) when trying to login. In the time since, I’ve only been able to log in twice, and both times I was logged out and ran in to login errors the next time.
I have tested on another computer, I’ve tested using my second Microsoft account (I own MC twice), I’ve restarted my modem and router. This is not something on my network, and I am certainly generating far below an amount of requests to warrant an HTTP 429 by attempting to login a few times every hour or so to check.
I also talked to my next door neighbor, who also owns Minecraft, and had him try to login to the Minecraft Launcher. Sure enough, it failed for him too. I then spoke to a friend that lives about 20 minutes away. Same thing. Another friend an hour away? Same thing.
Since this seems like a geographical/regional server issue, it may be helpful for you to know that this is up in the northeast USA (New Hampshire specifically). Three of the people who tested (including myself) have Xfinity as an ISP, while the fourth uses Fidium/Consolidated Communications fiber internet.
Steps to Reproduce the Issue:
Attempt to login to Minecraft Launcher (official and/or Modrinth)
Expected Result
Authentication is successful when Microsoft login is successful/complete.
Actual Result
Authentication fails while contacting api.minecraftservices.com with HTTP 429: Too Many Requests.
Additional
If you need additional information from me, please let me know. I redacted my username/info in uploaded screenshots, though, for privacy since the report is publicly viewable (IP address not redacted since its just my local IP)
Linked issues
relates to 2
Attachments
Comments 21
Alex Hawk
Here is what the Debug Information in Modrinth says:
Minecraft authentication error: Failed to deserialize response to JSON during step MinecraftEntitlements: expected value at line 1 column 1. Status Code: 429 Too Many Requests Body: <!DOCTYPE html PUBLIC '-//W3C//DTD XHTML 1.0 Transitional//EN' 'http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd'>
<html xmlns='http://www.w3.org/1999/xhtml'>
<head>
<meta content='text/html; charset=utf-8' http-equiv='content-type' />
<style type='text/css'>
body {
font-family: Arial;
margin-left: 40px;
}
img {
border: 0 none;
}
#content {
margin-left: auto;
margin-right: auto
}
#message h1 {
font-size: 24px;
font-weight: normal;
color: #000000;
margin: 34px 0px 0px 0px
}
#message h2 {
font-size: 20px;
font-weight: normal;
color: #000000;
margin: 34px 0px 0px 0px
}
#message p {
font-size: 16px;
color: #000000;
margin: 8px 0px 0px 0px
}
#message hr {
margin: 15px 0px
}
#errorref {
font-size: 11px;
color: #737373;
margin-top: 41px
}
</style>
<title>Service unavailable</title>
</head>
<body>
<div id='content'>
<div id='message'>
<h2>The request is blocked.</h2>
</div>
<div id='errorref'>
<span>20260117T033207Z-16768bb8878wf7q5hC1TEBxf3g000000081g000000002g2c </span>
</div>
</div>
</body>
</html>
I’ve been encountering the same problem.
HTTP 429 responses almost every time anyone in my house tries to log in, since around January 11th 2026.
No matter how long we wait, it keeps saying "too many requests."
I'm in Massachusetts, using FiOS.
If someone from outside the affected area joins my server (hosted at my house), the server will frequently dump an HTML document to the output, with an error saying it couldn't deserialize a JSON response (similar to what Alex sees in the Modrinth loader).
I continue to experience this error. I have a Minecraft server locally as well, and see occasional [14:21:53] [User Authenticator #1/ERROR]: Couldn't verify username because servers are unavailable logs now, too.
Thank you for reporting this issue. Our engineers have applied infrastructure changes which we believe have addressed this issue, so we will now mark this ticket as fixed.
Thanks for the update. If possible, could you try again and let us know if the issue persists?
In the meantime, you might also find some helpful troubleshooting steps here: Troubleshooting Minecraft Launcher issues