Feature · Features

Multi-location monitoring without false public outages

Verify service health from multiple logical locations while primary/backup probe details remain admin-only.

status.ftstatus.com
Live status board99.98% uptime
Marketing siteftstatus.com182ms
API gatewayapi.ftstatus.com96ms
Checkout servicedegraded · recovering+413ms
Auth & sessionsauth.ftstatus.com54ms
Background jobsworker poolOK
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+ regions
ACCAMSIADSIN

Alerting

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.

AAcme CloudAll systems operational
WebsiteOperational
APIOperational
PaymentsOperational
Email deliveryOperational

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.

1

Ingest probe results with primary/backup metadata.

2

Normalize results into logical locations.

3

Apply quorum and consecutive-failure rules before notifying.

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.

Start free