Show customer-facing components such as website, portal, API, and notifications.
Menu
Product
Resources
Tools
PricingLog inFeature · Status pages
Example FTStatus customer status page
Preview how FTStatus presents service health, incidents, maintenance notices, subscribers, and customer-safe updates without depending on a live customer page.
HTTPDNSSSLAPI
Reliable visibility without exposing internal infrastructure.
Explain incidents and planned work in plain language.
Keep internal probes, hosts, server paths, and provider notes private.
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.
Operational summary
A public status page should answer the customer question first: is the service operating normally, degraded, under maintenance, or recovering?
Component structure
Group monitors into readable services such as Main website, Client portal, API, Mail delivery, and Support desk instead of exposing raw infrastructure.
Update workflow
Incident and maintenance updates should move through investigating, identified, monitoring, and resolved states with clear timestamps.
Setup workflow
From first check to customer-ready status.
Create customer-facing service components.
Attach confirmed monitors to each component.
Publish maintenance and incident updates only after the public wording is approved.
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.
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.