Drag the artwork to explore. Use the arrow keys when it is focused.

Servers & CompetitiveJava Edition

Minecraft “Failed to Log In: Status 429”: What It Means and Every Fix

“Failed to log in: Status 429” (or “Too Many Requests”, “Failed to Get Minecraft Access”) stops you joining servers, signing in to the launcher or opening Realms. It is not a ban and it is usually not your PC. Here is what the error actually means, how to tell whether it is you or Mojang, and every fix that works, in the order worth trying.

5 min read

TL;DR: HTTP 429 means a server is rate-limiting you: too many requests came from your account or, far more often, from your IP address in a short time. In Minecraft Java it usually comes from Mojang’s session/authentication service when you join a server, from the launcher’s sign-in, or from Realms. Stop retrying for 15 to 60 minutes, check whether others are seeing it too, then try a different network. If the whole player base is hit at once, it is a Mojang-side incident and the only fix is to wait.

  • 429HTTP code for “Too Many Requests”
  • 15–60 minTypical wait before a rate limit clears
  • Per IPHow most limits are counted
  • Not a banYour account is not punished

Is it you or is it Mojang?

Check this first, because it decides everything else:

  • Look at who else is affected. Search X for “Minecraft 429” or “Minecraft login” sorted by Latest, and check @MojangSupport. If many players report it at the same time, it is an outage or a Mojang-side limit and nothing on your end will fix it.
  • Try a different server. If only one server fails, the 429 may come from that server’s own proxy or anti-bot protection, not from Mojang. Ask the server’s staff.
  • Try another account on the same network. If a friend on the same Wi-Fi also gets 429, your IP is limited, not your account.

Where a 429 can come from

Where you see it What is limiting you Most likely cause
Joining any server: “Failed to log in: Status 429” Mojang’s session service Shared or busy IP, rapid rejoins, or a Mojang-side incident
Launcher sign-in or “verifying ownership” Minecraft services API Repeated sign-in attempts, a third-party launcher retrying in a loop
Realms menu: “Realms (429)” Realms service Too many Realms requests from your IP, or Realms overload
One specific server only That server’s proxy or anti-bot Connection throttling on the server side
Downloading game files or modpacks Mojang’s download servers Many parallel downloads from one IP
The Minecraft Launcher sign-in screen with the Sign in with Microsoft button
The launcher sign-in goes through Microsoft first, then Xbox Live, then Minecraft’s own services; any of them can answer 429.

Every fix, in order

  1. Stop retrying and wait. Each retry can extend the limit. Close the game and launcher for 15 to 60 minutes. This alone fixes most cases.
  2. Switch networks. Most limits are per IP. Try a phone hotspot or another connection. If that works, your normal IP is the one being limited. This is common on school, university, office and dorm networks, behind carrier-grade NAT, and on VPNs where thousands of people share one address. ATLauncher users hitting 429 on game-file downloads reported the same hotspot workaround.
  3. Turn your VPN or proxy off (or switch to a different VPN server). Popular VPN exit IPs get rate-limited first.
  4. Restart your router if your provider gives you a new IP on reconnect.
  5. Sign out and back in once in the official launcher. In Prism, MultiMC or the Modrinth App, remove the account and add it again. Do it once, not ten times in a row.
  6. Close extra clients and tools. Several game instances, alt-account switchers, server-status bots or mods that query Mojang’s API in the background all count against the same limit.
  7. For Realms only: close the Realms screen, restart the game and wait before reopening it. Opening the Realms menu over and over is what triggers the limit.
  8. Still stuck after a day on a clean network? Contact Minecraft Help or file a report on the Mojang bug tracker. In January 2026 a login-429 bug that persisted for hours was confirmed and resolved there (WEB-8452).

For server owners

  • If your players report 429 only on your server, check your proxy (Velocity or BungeeCord) and anti-bot plugins for connection throttles, and raise them during launches or events.
  • Everything your server does against Mojang’s API comes from one IP: skin and head lookups, UUID fetches and session checks. Plugins that look up many player names at once can get your whole server rate-limited. Cache lookups and avoid bulk queries.
  • During a Mojang-side incident there is nothing to fix on your end; pin a short notice in your Discord so players stop retrying.

What not to do

  • Don’t download “429 fix” tools, launchers or mods. Outages are a favourite lure for Minecraft malware.
  • Don’t share your Microsoft login with anyone who promises to “unlock” your account. A 429 is never fixed by someone else signing in.
  • Don’t keep spamming Join or Sign in. It extends the limit.

Live status

When Minecraft’s login or multiplayer services go down for many players at once, we update this section with what is confirmed, what Mojang has said and when it is fixed. As of November 20, 2026 there is no widespread 429 incident: only isolated reports.

More on accounts and sign-in problems on our Microsoft account hub.

Related: Minecraft Discord Scams in 2026: How Fake Verification Links and Modpacks Steal Accounts

Sources 5

Did you enjoy this story?