Menu
Feature · Status communication
Service components for public status pages
Turn raw monitors into customer-readable services so status pages explain impact without revealing internal infrastructure.
- HTTP · DNS · TCP
- live checks
- 1 min
- Team cadence
- Real
- uptime history
- Public
- status page
Group checks by customer-facing workflow, not by server hostname.
Show operational, degraded, maintenance, and outage states clearly.
Keep private control panels, origins, ports, paths, and provider IDs internal.
Monitor
Component naming
Use names customers understand: Main website, Client portal, API, Email notifications, Support desk, or Billing portal.
Response time · 24h
182 msStatus pages
Monitor mapping
A component can represent one critical check or a group of checks when the public impact is the same.
Coverage
Public boundary
Components should describe what users experience. Internal diagnosis, probe nodes, and server topology belong in admin notes.
Global probe network
30+ regionsLooks 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.