Why Your Minecraft Bedrock Server Looks Offline (UDP 19132)

Your Bedrock server is running. Players are on it right now. You point an uptime monitor at it, and the monitor insists the server is down. You restart the process, open a ticket with your host, and start doubting the monitoring.

The server is fine. The check is asking the wrong question, in the wrong language, on the wrong transport.

Bedrock is not Java, and it is not TCP

The two Minecraft editions do not share a network protocol. Java Edition listens on TCP 25565, and a plain TCP connection to that port is a legitimate liveness test: the handshake either completes or it does not.

Bedrock Edition is built on RakNet, a protocol that runs over UDP, port 19132 by default. There is no TCP listener there at all. A TCP check on a perfectly healthy Bedrock server does not fail because the server is broken - it fails because nothing on the other end was ever going to answer a TCP SYN.

This is the single most common reason a Bedrock admin concludes that "uptime monitoring does not work for Bedrock". It works. It has to speak UDP.

Silence is not an answer

Switching the check to UDP is necessary but not sufficient. UDP has no handshake: you can send a packet into a black hole and never learn anything. A UDP check that reports "up" simply because nothing complained is not monitoring, it is wishful thinking - a firewalled port, a dead process and a wrong IP all look identical.

What makes a Bedrock check meaningful is that the server has something to say. RakNet defines an unconnected ping: send it, and a live server replies with a description of itself. No reply, no server. That reply is the only real evidence.

The packet that gets an answer

The ping is small and strict:

• 0x01 - the unconnected ping message id
• the current time, 8 bytes, big-endian
• the RakNet magic: the 16 bytes 00ffff00fefefefefdfdfdfd12345678
• a client GUID, 8 bytes

That magic constant is not decoration. It is how RakNet decides whether a datagram is worth looking at, and a ping without it is discarded without a word. We know this the unglamorous way: our own Bedrock checker was missing those 16 bytes and therefore reported every server on earth as offline, including servers with fourteen thousand people on them. From the outside the symptom is indistinguishable from a dead server, which is exactly what makes it worth writing down.

A live server answers with 0x1C, its own timestamp and GUID, the same magic, and then a semicolon-separated string. The useful part starts at byte 35:

MCPE;Hive Games;121;1.0;14029;100001;9155601167820068811;Survival

In order: edition, MOTD, protocol version, game version, players online, player slots, server GUID, level name, game mode. One UDP round trip tells you not only that the server is alive but how many people are on it and which version it is running.

What this means for monitoring

• Protocol: UDP. Not TCP. There is nothing listening on TCP 19132.
• Port: 19132 by default. If you run several worlds on one machine, each has its own port - monitor each one, because one crashed world will not affect the others' ports.
• A reply is the signal. Treat silence as down. On UDP that is the only honest reading.
• Watch the player count, not just the port. A server that answers with a full slot list and zero players for three days is technically up and practically dead.
• IPv6 matters more here than elsewhere. Bedrock clients on mobile networks frequently arrive over IPv6; if your server only answers on IPv4, a share of your players silently cannot connect while your monitor stays green.

Check yours right now

Our free Minecraft Bedrock server status checker sends exactly the ping described above and shows you the raw reply: version, protocol, game mode, level name, MOTD and the live player count. Enter the address without a port and it assumes 19132.

If the check comes back with data, the same page offers to put that exact address under continuous monitoring, already set to UDP on the right port, so you find out about a crash from an alert instead of from your Discord.

The short version

• Bedrock is RakNet over UDP 19132. Java is TCP 25565. They are different protocols, not two ports of one thing.
• A TCP check on Bedrock always fails, no matter how healthy the server is.
• Only a reply to an unconnected ping proves the server is alive.
• The reply carries the player count and version, so use it for more than up or down.