Authentication servers are down in Minecraft: what it means and how to check

Seeing "Authentication servers are down" in Minecraft usually means the game or the server could not confirm your Minecraft account during login. The public server may still be online. The server list may still show a MOTD and player count. The failure happens later, when you try to join.

The quickest check is simple: test the Minecraft server address, then test whether the problem affects more than one server. Use the Minecraft server status checker to see whether the server itself is online, reachable, and responding with the right edition, version, players, MOTD, and latency.

If the server is online but login still fails for many players, the issue is probably authentication, account session, or server owner configuration. ServerBuddy checks public Minecraft server addresses. It does not log into your Microsoft account or verify your personal session token.

Last reviewed: June 2026. Written for Java Edition online-mode behavior, public server status checks, and ServerBuddy's status checker.

Quick fix order

1. Restart Minecraft and the launcher.
2. Log out of your Microsoft account, then log back in.
3. Try joining a different online Java server.
4. Ask another player to test the same server.
5. Check whether the target server is online with ServerBuddy.
6. If you own the server, check online-mode, outbound HTTPS, proxy settings, and server logs.
7. Do not change public servers to offline mode just to bypass the error.

What does "authentication servers are down" mean in Minecraft?

"Authentication servers are down" means Minecraft could not complete the account verification step needed to join an online server.

On a normal public Java server, the server checks that the player is using a valid Minecraft account. That check is controlled by online-mode=true on the server. When the check fails, Minecraft may show an authentication error before the world loads.

This is different from a server being offline. A server can answer the multiplayer server list ping and still reject joins during authentication. That is why you may see the server MOTD, player count, and ping bars, then get kicked when you click Join Server.

Quick diagnosis table

First, check whether the server itself is online

Start with the server address. This separates "the Minecraft server is unreachable" from "the server is reachable but login authentication failed."

Open the Minecraft server status checker, paste the exact address players use, and run a check.

Use the same format players enter in Minecraft:

Do not paste a website URL:

A good status check can show the server's edition, protocol, version, player count, MOTD, icon, latency, and whether the server is already listed on ServerBuddy.

How to read the status checker result

If ServerBuddy shows the server as online, the public server address is responding. That does not guarantee you can join, but it means the server is not simply dead or unreachable.

If the status checker says the server is offline, work through the Minecraft server offline troubleshooting guide. If the server is online but players still get the authentication error, keep reading.

Why a server can look online but reject login

Minecraft has more than one step before you join a world. The multiplayer list check is the light check. It asks the server for public information such as MOTD, version, and player count.

The join process is different. On online-mode Java servers, Minecraft checks the player's account session before letting them in. If that check fails, you can see an authentication error even though the server card looked normal a few seconds earlier.

That is why players often say, "The server is up, but I still cannot join." Both can be true.

How to check if Minecraft authentication is the real problem

Use a comparison test. Do not rely on one server.

1. Join a different public Java server that usually works for you.
2. Ask a friend on a different network to join the same server.
3. Ask whether players already online can stay connected.
4. Check whether new joins fail while existing players remain online.
5. Look for a spike in reports from other players, but treat community reports as a signal, not proof.
6. Test the target server with the Minecraft server status checker.

If many players cannot join any online-mode Java server, waiting is usually the right move. If only one server fails, the server owner should check logs and configuration.

Fixes for players

Most player-side fixes are about clearing a stale session or proving the problem is not your connection.

Restart Minecraft and the launcher

Close Minecraft fully. Close the launcher too. Then reopen the launcher and start the game again. This fixes the common "Invalid session" pattern, where your game is still running with an old token.

Sign out and sign back in

If restarting does not help, sign out of your Microsoft account in the launcher, then sign back in. Do not just close the window. Use the account sign-out option so the launcher has to refresh your session.

Check your computer clock

A wrong system date or time can break secure login flows. Make sure your device uses automatic time and time zone settings, then restart the launcher.

Test without a VPN or proxy

If the problem started after enabling a VPN, proxy, school network, or work network, test once from a normal home or mobile connection. This does not mean VPNs always break Minecraft. It means they add another layer. When troubleshooting, remove that layer for one test.

Try another server

If one server fails but several other servers work, your account is probably fine. The issue is likely server-specific.

Browse the Minecraft server list or the Java Minecraft servers list and test a server that shows online. If you are not sure where the IP goes, use the how to join a Minecraft server guide.

Do not enter your password into random auth checkers

No public website needs your Microsoft password to check whether Minecraft authentication is down. A status checker should only need a public server address. If a site asks for your account password, leave.

Fixes for server owners

If you run the server and players report "Authentication servers are down," check the server logs first. Look for messages around login, session verification, proxy forwarding, secure profile checks, or failed connections to Minecraft session services.

Keep online-mode enabled on public servers

For a public Java server, keep this setting unless you fully understand the risk:

Turning online-mode=false can let unauthenticated names join. On public servers, that can create identity, griefing, impersonation, ban bypass, and permission problems. Do not switch to offline mode as a quick fix for a temporary outage.

Check outbound HTTPS from the server host

An online-mode server needs to reach Minecraft session services during login. If your host blocks outbound HTTPS, DNS, or required network routes, the server may be running but unable to verify players.

• host firewall rules
• cloud firewall rules
• DNS resolution from the server machine
• outbound TCP 443
• proxy container networking
• recent host security changes

Do not confuse enable-status with authentication

This setting controls whether the server appears in the multiplayer server list:

It is useful for server lists and status tools, but it is not the same as account authentication. A server can have enable-status=true and still fail joins. A server can also hide status and still allow joins. For public listing, keep it enabled so tools and players can check the server before connecting.

You can use the server.properties generator to review these settings before restarting.

Check proxy forwarding

If you use Velocity, BungeeCord, Waterfall, Geyser, or another proxy setup, authentication may fail at the proxy layer rather than the backend server.

• Is the proxy the public entry point?
• Is the backend supposed to run behind the proxy only?
• Is player forwarding configured on both sides?
• Did you change online-mode on the wrong layer?
• Are Java and Bedrock connections handled by different listeners?
• Are new players failing while existing players remain connected?

Do not randomly flip online-mode values across proxy and backend servers. Follow the documentation for your proxy stack.

Check secure profile errors separately

Newer Java servers may also reject players because of signed profile or chat-related checks. That is not always the same as "authentication servers are down." If logs mention unsigned profiles, secure profile, public keys, or chat session validation, inspect those settings separately.

Authentication error vs common connection errors

If the error is really a network or address problem, use the Minecraft server offline troubleshooting guide. If the error happens after the server appears online, authentication or account session checks are more likely.

What not to do

• Do not delete your world, reset your server, or reinstall Minecraft as a first step.
• Do not change DNS records unless the server address itself fails.
• Do not open random ports just because players mention authentication.
• Do not set a public server to offline mode unless you know exactly how your proxy, permissions, bans, and player identity system work.
• Do not use cracked launchers or third-party login tools as a fix.

How to know it is fixed

If the server is online but nobody new can join, keep your troubleshooting focused on login authentication, account sessions, proxy forwarding, and outbound access from the server host.