Menu
Feature · Status communication
Subscriber notifications for incidents and maintenance
Let customers follow service updates by email or configured channels so support teams can reduce repeat tickets during incidents.
- HTTP · DNS · TCP
- live checks
- 1 min
- Team cadence
- Real
- uptime history
- Public
- status page
Collect subscribers from the public status page where the workspace allows it.
Send incident, maintenance, and recovery notices only for affected components.
Respect verification, unsubscribe, and workspace access rules.
Status pages
Customer-controlled updates
Subscribers choose to receive updates for the services they care about instead of relying on ad hoc ticket replies.
Alerting
Verified delivery path
Email subscription flows should verify ownership, handle unsubscribes, and avoid exposing subscriber lists publicly.
Coverage
Incident fit
Subscriber notifications work best when public components, severity, and incident states are already mapped to customer impact.
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.