Monitoring

Incidents

Status pages

Maintenance

Team members

Integrations & API

N.

noc724 team

Packet response · dns-01 (UDP 53)

Last 30 days ⌄

1,600 ms

805 ms

10 ms

Apr 25, '23

May 5, '23

May 12, '23

May 19, '23

May 26, '23

≈ 12.8 ms

Average

⤒ 19.4 ms

Maximum

⦿ 0.0% Packet loss

UDP port monitoring
for services that fail
quietly.

UDP is connectionless, so most monitoring tools quietly ignore it. noc724 doesn't. Watch any UDP-based service, set a packet loss threshold, and validate responses with a keyword.

Advanced features for advanced users.

Confirmed failures, not false alarms

Send several packets per check and set how much loss you tolerate, so one dropped packet doesn't page anyone.

Several channels at once

Alert the on-call phone by SMS and the team chat on Telegram or Bale for the same incident, each with its own delay and repeat settings, so nobody misses a real outage.

Manage monitors through the API

Create, update and pause UDP monitors with noc724's REST API and your API keys.

Choose your preferred type of notifications

Get instant alerts by SMS, Telegram, Bale, Soroush Plus or webhook.

Response time monitoring

See UDP response times in a chart and spot a service that answers slower than usual.

Maintenance windows

Pause alerts while you restart or upgrade the service, without losing the history.

TelegramBaleSoroush PlusSMSWebhooksStatus pagesTelegramBaleSoroush PlusSMSWebhooksStatus pages
HTTP(S)PingTCP portsUDPDNS recordsCron jobsREST APIsMulti-step APIsSSL certificatesKeywordsHTTP(S)PingTCP portsUDPDNS recordsCron jobsREST APIsMulti-step APIsSSL certificatesKeywords

Monitor UDP services on any port.

Point a monitor at any host and UDP port: DNS, SNMP, NTP, SIP, RADIUS, game servers and other UDP services that return a response.

Monitoring

Incidents

Status pages

Maintenance

Team members

Integrations & API

N.

noc724 team

☐ 0 / 3Bulk actions ⌄All tags ⌄Search by name or urlDown first ⌄Filter

dns-01 (UDP 53)

UDP · Up 22 d

DNS ×PROD ×
↻ 5 min

99.990%

snmp-gw-01 (UDP 161)

UDP · Up 3 d

SNMP ×Network ×
↻ 5 min

99.847%

game-eu-01 (UDP 27015)

UDP · Down for 6 m

Game ×Critical ×
↻ 5 min

99.720%

UDP probe · dns-01 (Port 53)

→ SENT
dig @dns-01.company.ir example.com A
← RECEIVED
;; status: NOERROR example.com. 300 IN A 93.184.216.34
;; Query time: 12 ms

Send a custom payload.

Some services only answer when you ask correctly. Send a custom payload so DNS servers, game servers and SIP endpoints respond the way they're meant to.

Define your packet loss threshold.

Some packet loss is normal over UDP. Set how much loss is acceptable before a monitor counts as down, and get alerted on quality drops, not just total outages.

Monitoring

Incidents

Status pages

Maintenance

Team members

Integrations & API

N.

noc724 team

Packet loss threshold

50% lost

● 0%

Current loss

⤒ 50%

Down above

◷ 4

Packets per check

Assertions.

Monitor is up if all assertions pass

✓response containsNOERROR

✓packets answered4 of 4

✓packet lossbelow50%

Validate the response with a keyword.

A response doesn't guarantee health. Require a keyword in the reply to make sure the service returns the correct data, not just any data.

Set up UDP monitoring in
seconds.

Be the first to know when a UDP service stops answering. Reliable monitoring warns you before any significant trouble.

Benefits of
UDP Monitoring.

See what TCP checks can't

UDP monitoring gives you a way to check services that would otherwise fail quietly. For example, a DNS server can stop returning the expected answer while your website monitor still looks green.

Catch degraded service before a full outage

A service might still respond but lose enough packets to drop calls, lag games or fail lookups. With a packet loss threshold you catch quality drops before the service goes down.

Confirm the response is actually correct

Keyword checks confirm the response contains what you expect, so you're monitoring behaviour, not just activity.

What people monitor over UDP.

One monitor type covers a home game server and a corporate VPN gateway. A few setups people run today:

Hobby and home labs.

  • Game servers (Minecraft, Valheim, CS2): check the server is reachable before your players tell you it isn't.
  • Home VPN (WireGuard): confirm the tunnel endpoint answers from outside your network.
  • DNS resolvers (Pi-hole, AdGuard Home): catch the moment name resolution stops and everything at home looks broken.
  • Media servers (Plex, Jellyfin): watch the discovery services your devices rely on to find the library.
  • Self-hosted voice chat (Mumble): monitor the voice port itself, not just the machine it runs on.

Businesses and teams.

  • Corporate VPN gateways (WireGuard, OpenVPN): catch a dead tunnel endpoint before remote staff report it.
  • VoIP infrastructure (SIP, RTP): spot the packet loss behind dropped calls and choppy audio.
  • DNS servers, internal or authoritative: verify lookups still return the answer you expect.
  • RADIUS authentication servers: know when logins stop working at the auth layer.
  • NTP servers: catch time drift at the source, before it breaks logs, certificates and auth.
  • SNMP endpoints: confirm the network devices your dashboards depend on still respond.
  • Syslog collectors: see when log delivery stops, instead of finding a silent gap later.
  • STUN/TURN servers: keep WebRTC calls connecting for users behind NAT.

Know more than
just up or down.

Multi-location checks, response time tracking, SSL and domain expiry alerts. The details that tell you what's really going on.

All you really care about
monitored in one place.

From websites and APIs to servers and cron jobs, noc724 watches every layer. Eight monitor types, one dashboard.

Build trust with
public status pages.

Be transparent. Share your uptime with the public and keep your customers informed about any planned (or unplanned) outages.

noc724

Monitoring

Incidents

Status pages

Maintenance

Team members

Integrations & API

Monitors.

☐ 0 / 5Bulk actions ⌄All tags ⌄

api.core-backend-v2

HTTP · Down for 42m

PROD ×Tehran ×Critical ×

www.client-eshop.ir

HTTP · Up 14d 2h

Client ×Shop ×SSL ×

db-replica-01 (Port 5432)

PORT · Paused 24d

Database ×Staging ×

mx.company-mail.ir

DNS · Paused 1h

Infra ×Mail ×

Invoice-Generator-Cron

HEARTBEAT · Up 5m 35s

Finance ×Backend ×

Invite team member

×

Phone number

We will text the invitation to this number. If there is no noc724 account behind it yet, they will be invited to create one.

+98 912 000 0000

Role

Editor ⌄
CancelSend invite

Add your team members
to keep them notified.

Invite your whole team to see your monitors, get alerted and work on incidents together. Choose from four levels of access: admin, editor, viewer and notify-only.

Catch every incident before it reaches your users.

Get notified the instant something breaks: by SMS, Telegram, Bale, Soroush Plus or webhook. Watch your whole stack from one place and pick the channels that reach your team fastest, so critical issues never sit unseen.

Monitors.

☐ 0 / 5Bulk actions ⌄All tags ⌄Search by name or urlDown first ⌄

api.core-backend-v2

HTTP · Down for 42m

PROD ×Tehran ×Critical ×
↻ 5 min95.420%

www.client-eshop.ir

HTTP · Up 14d 2h

Client ×Shop ×SSL ×
↻ 5 min99.987%

db-replica-01 (Port 5432)

PORT · Paused 24d

Database ×Staging ×
↻ 5 min99.987%

mx.company-mail.ir

DNS · Paused 1h

Infra ×Mail ×
↻ 5 min99.987%

Invoice-Generator-Cron

HEARTBEAT · Up 5m 35s

Finance ×Backend ×
↻ 5 min99.987%

NOC724

5 min

noc724

Down monitor detected!

Last 24 hours

95.420%

Frequently asked questions.

UDP monitoring sends packets to a UDP port on your host and checks that the service answers. Because UDP has no connection handshake, a reply (optionally containing an expected keyword) is the only proof the service is alive.

8

monitor types

15s

fastest checks

Get your FREE account now, 5 monitors included!

Start monitoring for free

No credit card required!