How to Check if a Minecraft Server Is Online Before You Join

The fastest way to confirm a server is up is to look at its live player count and ping before you touch a single setting — if a number and a latency reading come back, the server is answering and the box is online. That player count next to every server on the homepage monthly rankings and the full server list isn't a stored value someone typed in; it's a live status ping, the exact same lightweight handshake your own Minecraft client runs to fill in the Multiplayer screen. So before you start swapping ports or rewriting an IP, read what's already on the screen. Most of the time it's already telling you whether the problem is the server, your version, or your network — and those three need completely different fixes.

The status ping is how every "is it online" tool works

When the Multiplayer list shows a server's player count and signal bars, it isn't logging you in. It's doing a separate, much smaller exchange called a Server List Ping. Your client opens a connection, sends a Handshake packet with the "Next state" field set to 1 (status), then a Status Request, then a Ping Request. The server answers with a Status Response and a Pong, and the connection closes. No world loads, no character spawns — it's just a quick "are you there, and what are you running" knock on the door.

The Status Response comes back as a small JSON blob, and it's the same thing every "is it online" site reads. It carries a version object (with a name and a protocol number), a players object (online, max, and an optional sample of names), a description (the MOTD text you see under the server name), and an optional favicon icon. If a server returns that JSON, it is up. The player count on the rankings, the signal bars in your client, and a third-party checker are all reading the same reply — they just present it differently.

This is why the live list on this site behaves like a real-time up/down board rather than a static directory. The same status ping populates every view: the version filters (dotted paths only — the hyphenated /servers/version/26-2 404s), the country filters, and each tag list. Whatever slice you're looking at, the number you see was pulled live.

Reading the signal bars and the player count

In your own Multiplayer screen, the signal bars are a measurement of how long that status ping took to come back. The vanilla Java thresholds are:

• 5 bars — under 150 ms
• 4 bars — under 300 ms
• 3 bars — under 600 ms
• 2 bars — under 1000 ms
• 1 bar — 1000 ms or more
• The red "no connection" X icon — a negative or unknown ping, meaning the server never answered

So full green bars plus a player count is the clean "online and reachable from where you're sitting" reading. The red X is the one that actually means trouble: no status response came back at all. Heavily modded launchers sometimes draw the indicator a little differently, but the underlying rule holds everywhere — no status response means the no-connection icon, and a response means bars.

The order of operations I'd actually use:

1. Check the live player count and ping on the rankings or full list. A number and a latency reading mean it's up right now.
2. Cross-check in your in-client Multiplayer screen. Full bars and a player count confirm it; the red X means it didn't answer for you specifically.
3. If those disagree, paste the address into a third-party checker like mcsrvstat.us or mcstatus.io, which runs the same ping from its own servers.
4. Only when all of those come back with no response should you treat the server as offline and stop editing settings.

Online but on the wrong version is not "down"

Here's the case people misread constantly. A server can answer the status ping perfectly — show a real player count, a real MOTD — and still refuse to let you in because it's running a different version than your client. When that happens, the Multiplayer list renders the version name in red, and hovering the bars or the version text shows you the version the server expects. The server is reachable. It's just rejecting your login because the protocols don't match.

Client and server have to share the identical network protocol to connect, and a newer client is not backward-compatible with an older server. On this site's version scheme, 26.2 "Chaos Cubed" is protocol 776 and 26.1 is protocol 775. If your client is on 26.2 and the server is still on 26.1, joining throws Outdated server! I'm still on <version> (sometimes shown as Could not connect: Outdated server!). The reverse — your client behind the server — gives Outdated client! Please use <version>. Neither of those is a network problem, and neither means the server is offline.

The tell is simple: a visible player count sitting next to a red version name means the box is up and answering. The only thing that needs to change is your client version, not your IP, your port, or your router. And since ViaVersion-style multi-version bridging is something the owner installs on their end, a player can't add it to someone else's server — if the version is mismatched and the owner hasn't bridged it, you match the server's version or you wait. There's a fuller walkthrough of that exact symptom in why a server shows offline on server lists.

When the ping really does fail

If every check above comes back empty — no player count, no bars, a red X, and a checker that reports no response — then the server is genuinely down or unreachable, and the error you get on a join attempt tells you which.

• Connection refused: no further information (the full form is io.netty.channel.AbstractChannel$AnnotatedConnectException: Connection refused: no further information) means a machine was reached, but nothing is accepting on that Minecraft port. The server process is down, still booting, or you've got the wrong port. This is almost always something on the server's side.
• Connection timed out: no further information means nothing replied at all. The server is fully offline, or a network, DNS, or firewall block sits somewhere between you and it.

Either error sits on the server or network side, not your client, so resist the urge to start editing version settings to fix them. The timeout case in particular has its own set of culprits, walked through in fixing connection timed out.

FAQ

Does a third-party checker's ping tell me my own latency?

No, and mcstatus.io is upfront about this — the latency it reports is measured from its own host, not your connection, so it's irrelevant to how the server will feel for you. Use a checker to confirm three things only: up or down, the player count, and the version the server is on. For your actual latency, read the signal bars in your own Multiplayer screen, since those are measured from your machine.

How do I check a Bedrock server, and does the port matter?

Bedrock uses a different status ping than Java — it runs over UDP/RakNet on default port 19132, versus Java's TCP 25565 — so a Java-only checker often can't read a Bedrock-only server and vice versa. mcsrvstat.us and mcstatus.io both handle either edition. When you enter an address anywhere, the form is host:port, with the port optional if the server uses the default; a custom Java port looks like 123.45.67.89:25565.

A server I know is popular shows zero players and no response — is it really down?

Probably, but not certainly. An owner can hide or customize the status reply with an MOTD plugin, or disable the status ping entirely, in which case a blank or odd response doesn't strictly mean offline. That's the exception, though — for the overwhelming majority of public servers the ping is reliable, so a consistent no-response across your client and two checkers is safe to read as down.

Can a checker show me the actual player names online?

Sometimes. The Status Response includes an optional sample list of player names inside the players object, and many servers return a handful there. If the owner has set enable-query=true on the server, checkers like mcsrvstat.us can pull richer detail beyond the basic status reply, including a fuller player list and plugin information. If sample comes back empty, the server simply chose not to publish names, which is common and not a sign of anything wrong.