Menu
Feature · Features
Multi-location monitoring without false public outages
Verify service health from multiple logical locations while primary/backup probe details remain admin-only.
- HTTP · DNS · TCP
- live checks
- 1 min
- Team cadence
- Real
- uptime history
- Public
- status page
Collapse primary and backup probes into one public location result.
Declare customer-visible downtime only after quorum rules are met.
Show backup-mode warnings to admins without alarming customers.
Coverage
Logical locations
Customers see country or region health. Administrators can still see whether a primary or backup probe produced the result.
Global probe network
30+ regionsAlerting
Quorum-based incidents
FTStatus should require more than one confirming signal before changing customer-facing status.
Status pages
Cleaner operations
Probe-provider problems become internal warnings rather than public downtime unless customer access is affected.
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
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.
Decide with confidence
Where multi-location monitoring without false public outages earns its place
A useful monitor is tied to a customer journey, an owner, and a response rule. The goal is not more checks; it is earlier detection with less noise.
Use this when
- Collapse primary and backup probes into one public location result.
- Declare customer-visible downtime only after quorum rules are met.
- Show backup-mode warnings to admins without alarming customers.
Set the boundary
- Start with one customer-facing service, verify the alert path, and publish only the service impact that customers need to understand.
- Keep server names, credentials, provider identifiers, and internal diagnosis out of public status updates.
- Pair uptime evidence with application logs or tracing when the question is why a service failed, not whether customers can reach it.
Product evidence
A real reliability workflow, not a promise deck.
FTStatus earns trust with a product you can inspect and a setup you can test before it becomes part of a customer-critical service.
View live demoA live public experience
Open a real FTStatus status page and inspect the same component, incident, maintenance, and subscription flow your customers will use.
A testable operating loop
Create a monitor, run the check, verify the alert path, publish customer-safe impact, and retain the incident timeline.
Honest capability boundaries
Live, operator-assisted, managed-only, and planned workflows are labelled so buyers can scope the service without hidden assumptions.
Before you choose
Questions buyers ask before setup.
Clear scope now prevents surprise costs, noisy alerts, and public status pages that expose the wrong detail later.
What does multi-location monitoring without false public outages cover?+
Verify service health from multiple logical locations while primary/backup probe details remain admin-only.
What should I configure first?+
Collapse primary and backup probes into one public location result. Then test the failure and recovery path before attaching the monitor to customer notifications.
Will technical details appear on the public status page?+
No. Public components describe the affected customer-facing service. Infrastructure details and investigation notes remain in the internal workflow.
Can Faciotech configure and maintain this for us?+
Yes. Managed monitoring can include scope design, monitor setup, alert tuning, status-page maintenance, and incident coordination when included in the agreed service.
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.