Start with HTTP and DNS checks.
Resource · Resources
FTStatus help center
Practical setup guidance for monitors, status pages, incidents, subscribers, and alert routing.
HTTPDNSSSLAPI
Reliable visibility without exposing internal infrastructure.
Attach customer-facing services to status-page components.
Document alert routes and maintenance windows before they are needed.
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.
Getting started
Create one workspace, one public page, and a short list of critical monitors before adding integrations.
Operational setup
Define owners, escalation paths, customer-facing component names, and maintenance procedures.
Admin safety
Keep infrastructure-specific details out of public pages and retain them in internal admin notes.
Related pages
Continue building the monitoring workflow.
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.