Last updated: March 2026
What Is a Minecraft Server Status Checker?
A Minecraft server status checker is a tool that queries any Minecraft Java Edition server to determine if it is online and retrieve its public information. It uses the Server List Ping (SLP) protocol to fetch the server's version, player count, MOTD (message of the day), favicon, and latency, giving you a complete snapshot of the server's current state without needing to open your Minecraft client.
What Information Can You Get from a Server Status Check?
When you check a Minecraft server's status, the SLP protocol returns several pieces of information. Here is what each field means and why it matters:
Online/Offline Status
The most basic check. If the server responds to the SLP request, it is online. If the connection times out or is refused, the server is offline or unreachable. This is the first thing players see in the multiplayer menu.
Server Version
Shows which Minecraft version the server is running (e.g., 1.21.4, Paper 1.21.4). This tells players whether their client version is compatible. Servers using ViaVersion may show a version range instead of a single version number.
Player Count
Displays the current number of online players and the maximum player limit (e.g., 15/100). This gives you a quick sense of server activity and capacity. Some servers also include a sample of online player names in the hover tooltip.
MOTD (Message of the Day)
The server's welcome message displayed in the server list. Server owners use this to communicate their server's theme, current events, or announcements. It supports Minecraft color codes and formatting. Create yours with our MOTD Generator.
Server Favicon
A 64x64 pixel image that appears next to the server in the multiplayer list. It acts as your server's logo and is the first visual element players notice. The favicon is encoded as a base64 PNG in the SLP response.
Ping Latency
The round-trip time in milliseconds between the checker and the server. Our tool measures this from Singapore, so the latency reflects what Southeast Asian players experience. Use our dedicated Ping Tester for more detailed latency analysis.
How the Minecraft Server List Ping Protocol Works
The Server List Ping (SLP) protocol is how Minecraft clients and tools like this one retrieve server information. Understanding how it works helps you troubleshoot connectivity issues and understand what data is being exchanged.
The process starts with a TCP connection to the server's port (default 25565). The client sends a Handshake packet specifying the protocol version and the server address, followed by a Status Request packet. The server responds with a JSON payload containing the version info, player data, description (MOTD), and favicon. A separate Ping/Pong exchange measures latency by timing a round-trip packet.
This entire exchange happens without authentication or joining the server. It does not count as a player connection, does not trigger join events in plugins, and has minimal impact on server performance. The SLP protocol has been part of Minecraft since version 1.7 and remains the standard method for querying server information in Java Edition.
Why Server Monitoring Matters for Server Owners
If you run a Minecraft server, monitoring its status is not optional. Downtime directly impacts player retention, community trust, and your server's reputation on server listing sites.
- Player retention: Players who encounter an offline server more than twice are likely to find a different server. Regular monitoring lets you catch outages within minutes, not hours. The faster you respond, the fewer players you lose.
- Uptime tracking: Server listing sites like Minecraft Server List rank servers partly by uptime. Consistent downtime pushes your server down in rankings, reducing visibility and new player acquisition.
- Performance baselines: Regular status checks help you establish what "normal" looks like. If your player count suddenly drops or your MOTD shows incorrectly, you know something changed that needs investigation.
- Post-update verification: After updating server software, plugins, or configuration files, a quick status check confirms everything is running correctly. Use our Config Generator to create optimized configs and verify they load properly with a status check.
Common Server Status Issues and Fixes
When your status check returns unexpected results, here are the most common issues and how to resolve them:
| Issue | Likely Cause | Fix |
|---|---|---|
| Server shows offline | Server process not running, wrong address/port | Check server console, verify address and port number |
| Connection refused | Port not open, server crashed | Check firewall rules, verify port forwarding, restart server |
| Connection timed out | Firewall blocking, wrong IP, server overloaded | Check firewall, verify IP address, check server resource usage |
| Outdated client | Version mismatch between client and server | Update your client or use ViaVersion plugin on the server |
| MOTD not showing | Broken color codes in server.properties | Use our MOTD Generator to create valid MOTD codes |
If your server is online but showing high latency in the status check, the issue is network-related, not server-related. Check our Ping Tester for detailed latency diagnostics, and read our guide to reducing Minecraft lag for optimization tips.
How to Set Up Server Monitoring
While this tool is great for on-demand checks, you should also set up automated monitoring that alerts you when your server goes down. Here are the most popular approaches:
- UptimeRobot (free): Create a TCP monitor pointing to your server's IP and port. Set the check interval to 5 minutes. UptimeRobot can send alerts via email, Discord webhook, Slack, or SMS when your server goes offline. The free plan supports up to 50 monitors.
- Discord webhooks: Use a bot like MCStatus Bot or Crafty Controller to post server status updates directly in your Discord server. Players can see at a glance whether the server is up and how many people are online.
- Pterodactyl panel alerts: If your hosting provider uses Pterodactyl (like CraftRift does), you can configure crash detection and automatic restarts. The panel monitors the server process and can restart it automatically if it crashes, minimizing downtime.
- Custom scripts: For advanced users, a simple cron job that pings your server every minute and sends a Discord notification on failure takes about 10 lines of code. This gives you the fastest possible detection time.
Combining automated monitoring with regular manual checks using this tool gives you comprehensive coverage. The automated system catches outages instantly, while manual checks let you verify the full server information display.
Frequently Asked Questions
Why does my server show as offline even though it is running?
There are several common causes. Your firewall may be blocking incoming connections on port 25565 (or your custom port). If you are using a proxy like BungeeCord or Velocity, the backend servers may not respond to external pings. Double-check that your server address and port are correct, that port forwarding is configured properly on your router (for self-hosted servers), and that your hosting provider's firewall allows inbound TCP traffic on your server port.
What does 'connection refused' mean?
A 'connection refused' error means the server's IP address is reachable, but nothing is listening on the specified port. This usually happens when the server process has crashed or has not finished starting up. It can also occur if you are using the wrong port number. Check your server console for errors, verify the port in your server.properties file, and make sure the Java process is actually running.
Can I check Bedrock Edition servers with this tool?
This tool currently supports Minecraft Java Edition servers only. Java Edition uses the Server List Ping (SLP) protocol over TCP on port 25565 by default. Bedrock Edition uses a completely different protocol (RakNet) over UDP on port 19132. Bedrock status checking requires a separate implementation. If you run a crossplay server with GeyserMC, the Java port will still work with this tool.
How often should I monitor my server status?
For production servers with active players, monitoring every 1-5 minutes is standard. This ensures you catch outages quickly before players notice. Services like UptimeRobot offer free monitoring with 5-minute intervals and can alert you via Discord, email, or SMS when your server goes down. For smaller servers, checking every 15-30 minutes is usually sufficient.
Why is the player count different from what I see in-game?
The player count shown by status checkers comes from the Server List Ping protocol, which reports the numbers your server broadcasts. Some plugins like ViaVersion, BungeeCord, or vanish plugins can cause discrepancies. Vanished players are still counted in the protocol response but are invisible in-game. BungeeCord networks may show the total network player count rather than the count for a specific backend server.