Server status checker

When the check says unreachable

Nine times out of ten it's not the game server, it's the road to it. In order of how often it turns out to be the cause:

1. The port isn't forwarded. Your router has to send traffic on that port to the machine running the server. This is the one, most of the time.
2. A firewall is blocking it. Windows Firewall, ufw, or your host's control panel. Opening the port in the server config does nothing if the OS drops it first.
3. The server is bound to localhost. If server-ip is set to127.0.0.1, only that machine can reach it. Leave it empty to listen on everything.
4. Wrong port. You changed it in the config and are testing the default, or the other way round.

Why it works for you and nobody else

Because you never leave your own network. Connecting to localhost or to your machine's local address skips your router and firewall entirely — the two things most likely to be the problem. A check from outside is the only one that tells you what your players see, and that's what this page does.

"Answering, but not the right game"

Something is listening on that port, but it isn't speaking the protocol we expect. Usually it means the port belongs to a different service, or you picked the wrong game above. For Bedrock, remember it's UDP on 19132 and not the Java port.

Do I need an account?

No. There's a daily limit per visitor and a captcha, which exists so nobody can point the checker at other people's networks to scan them. If you hit the limit it resets at midnight UTC.