Collapse primary and backup probes into one public location result.
Feature · Features
Multi-location monitoring without false public outages
Verify service health from multiple logical locations while primary/backup probe details remain admin-only.
HTTPDNSSSLAPI
Reliable visibility without exposing internal infrastructure.
Declare customer-visible downtime only after quorum rules are met.
Show backup-mode warnings to admins without alarming customers.
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.
Logical locations
Customers see country or region health. Administrators can still see whether a primary or backup probe produced the result.
Quorum-based incidents
FTStatus should require more than one confirming signal before changing customer-facing status.
Cleaner operations
Probe-provider problems become internal warnings rather than public downtime unless customer access is affected.
Setup workflow
From first check to customer-ready status.
Ingest probe results with primary/backup metadata.
Normalize results into logical locations.
Apply quorum and consecutive-failure rules before notifying.
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
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.