Skip to content

Live server utility

Server Status Checker

Check Java or Bedrock availability, player counts, version details and round-trip latency without leaving your browser.

Direct lookup

Check a server

Enter a public domain or IP. Java defaults to port 25565; Bedrock defaults to 19132.

Edition

Read the response

What the signals mean

Availability

Online means the server answered the selected Java or Bedrock protocol.

Players

Counts are reported by the server and may be hidden or capped by its configuration.

Latency

Lower round-trip time usually feels more responsive; distance and routing both matter.

Version

Match the reported game version and edition before attempting to join.

Join safely

Connect in Minecraft

  1. 1. Open Multiplayer and choose Add Server.
  2. 2. Paste the exact domain or IP shown by the network.
  3. 3. Confirm the correct edition and any custom port.
  4. 4. Save, refresh the list, then connect.

Before troubleshooting

  • Check maintenance notices on the server's official channels.
  • Verify version, allow-list requirements and resource packs.
  • Try the default port if the network does not publish a custom one.
  • Never share account credentials with unofficial status tools.

Read the public response

Separate reachability from playability

A successful status response proves that the queried endpoint answered. It does not guarantee that every player can join, authenticate, load the world, or avoid plugin and version conflicts.

Edition & scope note

Some networks proxy, filter, cache, or intentionally hide status fields. A failed public probe can also differ from connectivity inside the server's own network.

  1. 01

    Enter the published address

    Use the hostname and port players are expected to join, not an internal panel or private network address.

  2. 02

    Choose the correct edition

    Java and Bedrock use different protocols, defaults, and discovery behavior.

  3. 03

    Interpret the returned fields

    Review status, latency, version, MOTD, and published player data together instead of treating one green badge as a full health check.

Keep the workflow moving

Useful next steps

Browse all tools