Monitoring
Solutions
Resources
Free Tools
Pricing
Products / Server monitoring / UDP Server Monitoring
Any UDP port

UDP Server Monitoring

UDP has no handshake, so failures are easy to miss. Send a probe string to your UDP service and verify the reply to know it is really alive.

9 check locations1–120 min check interval8 alert channels10 monitors free
vpn.example.com:51820 · UDP
Probe sentping
String expectedmatched
Response time57 ms
Uptime (30 d)99.95%
Illustrative example of a check result.

Monitoring a protocol with no connection

UDP is used for DNS, VoIP, streaming, VPNs and games precisely because it is fast and connectionless. The catch: nothing tells you when a UDP service is down unless you ask it something and wait for an answer.

A UDP monitor sends a string you define and checks the reply, which is the only reliable way to prove a UDP service is responding.

What Upzilla checks

Every check is stored in a full log, so you can see exactly when and how something changed.

Send and expect

Define what to send and what a healthy reply contains.

Any UDP port

DNS 53, WireGuard, game servers, custom services.

Response time

Track latency of the reply.

Multiple locations

Verify reachability from several regions.

How it works

From sign-up to your first alert in a few minutes.

Enter host and port

Choose the UDP service.

Define the probe

A string to send and one to expect back.

Alerts

Be told when the reply stops arriving.

Settings you can control

Sensible defaults get you started; every option below can be tuned per monitor.

SettingWhat it does
Domain / IPThe server to monitor.
PortThe UDP port.
String to sendData to send to the server.
String to expectText the reply must contain.
FrequencyHow often the check runs: 1 to 120 minutes. The Free plan checks from every 15 minutes; Premium from every minute.
LocationsRun the check from one or several of 9 locations: Spain, France, United Kingdom, USA (New York, Los Angeles), Australia, Singapore, Japan and Germany.
NotificationsPick any of your pre-configured alert channels: e-mail, SMS, Telegram, Slack, Messenger, voice call, webhooks and more.
Status pageMake the statistics of this monitor public or private.
TagsGroup monitors with tags to keep large accounts tidy.
IP versionForce IPv4, IPv6, or let Upzilla use whichever is available.
Full setup guide in the documentation →

Common use cases

DNS servers

Check your own resolvers and authoritative servers.

VPN endpoints

Watch WireGuard or OpenVPN over UDP.

VoIP and streaming

Keep SIP and media endpoints healthy.

Game servers

Confirm players can reach the server.

Alerts where your team already is

Create as many notification methods as you like, even on the free plan.

Slack
Telegram
Telegram group
Facebook Messenger
Email
SMS
Voice call
Webhooks

Related monitors and tools

TCP Server MonitoringDNS MonitoringPing MonitoringSSH MonitoringTCP/UDP port numbers (free tool) →

Questions about udp server monitoring

Why is UDP harder to monitor?

With no connection there is no handshake to confirm. You have to send a probe and wait for a reply.

What if my service never replies?

Then a reply-based check is not possible. Consider a TCP or ping check on the same host.

Which ports are common?

DNS 53, NTP 123, SNMP 161, WireGuard 51820. See the port numbers list for more.

Can I test several locations?

Yes, choose any of the 9 locations.

Prove your UDP service is really answering

No card required. 10 monitors of any type, free.

Create free account →