Menu
Feature · Features
UDP monitoring (planned)
Planned capability — not yet available to create. UDP-based service checks are on the FTStatus roadmap for cases with a clear request, response, and timeout rule that can be validated safely from outside the network.
- HTTP · DNS · TCP
- live checks
- 1 min
- Team cadence
- Real
- uptime history
- Public
- status page
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.
Monitor
What it checks
Planned — not yet available to create. When shipped, UDP monitoring will be useful for supported services where FTStatus can send a defined probe and evaluate a bounded response without exposing internal service details.
Response time · 24h
182 msAlerting
How alerts work
Because UDP is connectionless, alert rules should use conservative timeout, retry, and location confirmation settings before changing customer-facing status.
Status pages
What customers see
Public pages should describe the affected customer-facing service, not raw ports, probe payloads, or provider configuration.
Looks right either way
Light or dark, your status page stays on-brand.
Match what your customers expect with a clean light or dark public page — same components, same clarity.
Last 90 days · 99.98% uptime
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
Setup workflow
From first check to customer-ready status.
Define the UDP service, expected response, timeout, and safe public component name.
Confirm the check from more than one logical monitoring location.
Attach confirmed failures to alert routes and status-page impact only when customer-facing service is affected.
Related pages
Continue building the monitoring workflow.
Set up monitoring your customers can trust.
Start free with the checks that matter — sites, APIs, DNS, and hosted services — then add status pages and alert routing as you grow. No credit card, and local Faciotech support when you need it.