How to monitor a UDP service (game servers, NTP, VoIP) in Spot Downtime
A step-by-step guide to UDP monitoring: choose what to send, what the reply must contain, when to use hex, and how to read the result.
· 4 min read · By the Spot Downtime team
UDP has no handshake, so you can't tell an open port from a dead one by connecting. A UDP monitor sends a request your service answers and counts it as up only when the right reply comes back. (For why, see how to tell an open UDP port from a dead one.)
Step 1: create the monitor
- Open Monitors, click Add monitor and choose UDP port.
- In Host and port, enter the address, such as
game.example.com:27015. - In Send, enter the request your service answers (examples below).
- Optionally fill in Reply must contain. The match is exact and case-sensitive, anywhere in the reply.
- Tick Values are hex bytes for binary protocols.
- Pick how often to Check every, then click Add monitor.
Add a monitor
Host and port
time.example.com:123
Send
1b 00 00 00 00 00 00 00 …
Values are hex bytes
Yes
Check every
5 minutes
Step 2: pick what to send
| Service | Send | Hex? | Reply must contain |
|---|---|---|---|
| NTP (port 123) | 1b + 47 zero bytes (94 zeros) | Yes | Leave empty: any reply means it answers |
| Source game servers | ff ff ff ff 54 + "Source Engine Query" + 00 | Yes | ffffffff |
| Your own service | Its ping or status message | As needed | Text from its normal reply |
In hex, write two digits per byte. Spaces, colons and a leading 0x are ignored, so 0x1B:00:00 works. Requests and replies can be up to 1,024 bytes each.
Step 3: read the result
| Result | Means |
|---|---|
| Up | A reply came within 10 seconds and contained your text. The round trip goes on the response-time chart. |
| Port closed (ICMP port unreachable) | The host is up but nothing is listening. Restart the service. |
| No reply within 10s | Packets are being dropped, or the service is hung or ignoring the request. |
| Reply doesn't contain … | Something answered, but not what you expected. The alert shows the start of the reply. |
Tips
- Check near your players. On Starter and Pro, use Check from to pick Amsterdam, Singapore or several regions.
- Got a real protocol? Use its check. For a DNS server, a DNS monitor checks that real records come back, which says more than a raw reply.
- Test the alert with Send test under Alerts before you rely on it.
More in this series
Get new guides by email
Practical posts on monitoring, outages, error fixes and on-call, when they're published. No spam.
Keep reading
- How-to · Monitoring · APIsHow to configure gRPC health checkingLearn how to implement and configure gRPC health checking for reliable service discovery and load balancing: server status, Kubernetes probes, client-side health checks, Envoy, cloud load balancers and Consul.November 7, 2026 · 7 min read
- How-to · Servers · MonitoringHow to monitor CPU, memory and disk usage on a Linux serverCheck CPU, memory and disk on Linux with top, free and df, learn which numbers actually matter, pick sensible alert limits, and get alerted before a server runs out.November 4, 2026 · 8 min read