Feature · Features

UDP monitoring for supported services

Check UDP-based services when there is a clear request, response, and timeout rule that can be validated safely from outside the network.

HTTPDNSSSLAPI

Reliable visibility without exposing internal infrastructure.

Use UDP checks only for services with a reliable external response pattern.

Pair UDP results with DNS, TCP, or HTTP checks when customer impact depends on more than one signal.

Keep ports, hostnames, and provider-specific details out of public status copy.

Watch the signal

Track the public evidence customers actually experience.

Measure the trend

Keep response, uptime, and incident context close to the decision.

Route the response

Alert the right people and publish customer-safe updates when needed.

What it checks

UDP monitoring is useful for supported services where FTStatus can send a defined probe and evaluate a bounded response without exposing internal service details.

How alerts work

Because UDP is connectionless, alert rules should use conservative timeout, retry, and location confirmation settings before changing customer-facing status.

What customers see

Public pages should describe the affected customer-facing service, not raw ports, probe payloads, or provider configuration.

Setup workflow

From first check to customer-ready status.

1

Define the UDP service, expected response, timeout, and safe public component name.

2

Confirm the check from more than one logical monitoring location.

3

Attach confirmed failures to alert routes and status-page impact only when customer-facing service is affected.

Safe for public status pages

  • Website and application availability
  • API health endpoint status
  • DNS and SSL issues affecting customer access
  • Maintenance windows and incident timelines
  • High-level region coverage

Internal operations only

  • SSH, admin panels, databases, queues, and backups
  • Server names, origin IPs, provider IDs, and ports
  • Firewall rules, file paths, and secret-related config
  • Primary or backup probe node details
  • Customer-specific private control panels

Related pages

Continue building the monitoring workflow.

Back to overview

Ready to set up the right monitors?

Start with critical customer-facing services, then add status pages, alert routes, and managed help as reliability becomes more important.

Start monitoring