Menu
Feature · Monitoring
Customer status pages for clear updates
Publish branded status pages with components, incident history, maintenance windows, subscribers, and customer-safe explanations.
- HTTP · DNS · TCP
- live checks
- 1 min
- Team cadence
- Real
- uptime history
- Public
- status page
Group public services into readable components.
Publish incidents and maintenance windows with impact notes.
Keep private infrastructure details out of public descriptions.
Monitor
Components
Components should describe customer-facing services such as website, client portal, API, or email notifications.
Response time · 24h
182 msAlerting
Incidents
Each incident has status updates, impacted components, and a resolution timeline.
Status pages
Subscribers
Customers can follow updates without repeatedly opening tickets.
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
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.