Check any Java or Bedrock server: online or offline, players, MOTD, version and ping. When it is down, the checker tells you why it is offline and what to fix.
Hardware and tooling tuned specifically for Minecraft — not a generic VPS with a wiki page bolted on.
Every server runs in its own isolated container with the RAM and CPU of your plan reserved up front — a busy neighbor can never eat your ticks.
Snapshot your whole world in one click, stored off-server. Creeper took the base? Roll back just as fast.
Try it — hit install. Or see how modpack hosting works.
Console, backups, files, mods, sharing — all where your least technical friend can find them. Invite co-owners as operators or viewers.
Keep up to five saves on a single plan — survival, skyblock, a modded run — each with its own version, mods, and settings. Switch in one click; your join address never changes.
Turn on crossplay (Paper, Fabric, NeoForge) and friends on PC, console, and phone all spawn in the same world.
Minecraft runs your whole world on a single CPU core — per-core speed sets your TPS, not core count. Our Zen 4 Ryzen 7 7700 lands within 5% of AMD's Zen 4 flagship on that core and well ahead of the Zen 3 chips many hosts still sell, with every world on NVMe so chunks load as fast as you fly.
Yes, the newest 9950X is ~15% faster per core — we chart it anyway. Real numbers over marketing.
The checker does what the game's multiplayer screen does, from our server instead of your PC. For Java Edition it looks up the _minecraft._tcp SRV record for the name (the redirect many big networks use), resolves the address, opens a TCP connection on port 25565 (or the SRV port), and sends the Server List Ping handshake plus a status request. The server answers with a JSON blob: version, protocol number, players online and max, the MOTD as a chat component, and optionally a 64x64 icon. For Bedrock Edition there is no TCP handshake: it sends a RakNet "unconnected ping" over UDP 19132 and reads the pong, a semicolon-separated line with the edition, MOTD, protocol, version, player counts, world name and game mode. "Auto" runs both at once and reports each, so you do not have to know which edition a server is.
Every probe times out after 3 seconds and the whole check after 6. Private and local addresses (10.x, 192.168.x, 127.x, link-local) are refused before anything is sent. The latency shown is the TCP connect time (Java) or pong round trip (Bedrock) measured from our checker, so it is a health signal for the server, not the ping you will see in game.
| Field | Meaning | Where it comes from |
|---|---|---|
| Online / Offline | Whether a probe got a valid status reply | Any successful Java or Bedrock response |
| Players | Players online right now and the slot limit | players.online / players.max (Java), pong fields 5-6 (Bedrock) |
| MOTD | The server's message of the day, rendered with its colors | description (Java), pong fields 2 and 8 (Bedrock) |
| Version / protocol | Software and version name, plus the protocol number clients must speak | version.name / version.protocol (Java), pong fields 3-4 (Bedrock) |
| Resolved IP | The public IP the address currently points to | DNS A/AAAA lookup |
| SRV record | Where _minecraft._tcp.<name> redirects Java clients, if at all | DNS SRV lookup (Java, default port only) |
| Latency | Round trip from our checker to the server | TCP connect (Java) or UDP pong (Bedrock) |
A false offline almost always has one of these causes, and the diagnosis panel under the result names the one it found:
The reverse case, offline for everyone, usually comes down to the server process not running (connection refused) or the port not being forwarded (timeout). Both are covered step by step in how to port forward a Minecraft server and how to join a Minecraft server.
Java Edition listens on TCP 25565 by default (set by server-port in server.properties); Bedrock listens on UDP 19132 (and 19133 for IPv6, set in server.properties as server-port and server-portv6). A Geyser crossplay server usually exposes both on one address, which is why the checker probes both in Auto mode. Hosts that run many servers on one machine hand out a different port per server, so always paste the full host:port your panel shows. Need both editions on one address? See crossplay server hosting.
After a check, Copy link gives you a URL with the address and edition in the query string; opening it runs the check again, so it always shows the current state. Copy badge gives you a Markdown (or HTML) snippet for an SVG badge served from /api/tools/status/badge. Paste it into a README, a forum signature or your site: it reads "Online · 12/100 players" or "Offline" and re-checks at most every 30 seconds, sharing the same cached probe as this page so a popular badge never hammers your server.
If lag rather than downtime is your problem, start with how to fix Minecraft server lag.
Want an address that is always online and never changes?
Your SpawnFort server is live in about 30 seconds with its own public address, Java and Bedrock ready. Free for 2 days, no card.
Type the server address (and port, if it is not the default) into the checker above and press Check. It pings the server the same way the game does: a Server List Ping over TCP for Java and a RakNet ping over UDP for Bedrock. You get online/offline, the player count, MOTD, version and latency, and when it fails, the reason.
25565 is the default TCP port of a Minecraft Java Edition server. When you type an address without a port, the game (and this checker) uses 25565, unless a DNS SRV record redirects it. Bedrock Edition uses UDP 19132 instead.
Not directly. The F3 debug screen shows your frame rate and chunk info; your ping to the server is the signal bars next to the server in the multiplayer list, and on a server the Tab player list shows bars per player. The latency this checker reports is measured from our checker, not from your PC.
High ping is distance and network, not server RAM. Pick a host close to the players, use a wired connection, close downloads and streams, and avoid VPNs. If everyone lags at once and TPS drops, that is server lag, not ping: see the lag guide linked below.
Realms do not have a public address you can ping, so no checker (including this one) can test a Realm. Check Mojang's official status page or the in-game Realms screen. Any server with a normal address or IP can be checked here.
Usually one of four things: the address has an SRV record pointing elsewhere (we follow it, but only when you leave the port empty), you entered a Java server as Bedrock or vice versa, a custom port was left out, or a firewall allows the players' region but drops our checker. The diagnosis panel names the likely one.
No. The result is cached in memory for 30 seconds so the page and the badge share one probe, then it is gone. Nothing is written to a database or log.
A public address that never changes, backups every day, and a status your friends can trust. Live in about 30 seconds.