Concepts

Understand uptime monitoring, latency vs response time, uptime calculations, and the design decisions behind FTStatus.

An honest map of every FTStatus check — what is actually verified, the customer impact, and whether each capability is live, operator-assisted, or planned.

A deep dive into uptime monitoring concepts, architecture, and best practices

Three words that look interchangeable but aren't — what each one means in FTStatus and how they fit together.

What a private location is, when to use one, how it talks to FTStatus, and how it differs from a public probe.

How FTStatus separates detecting a problem (incidents) from communicating it (status reports and maintenance windows), and how report updates drive your status page.

Understanding how to communicate effectively during incidents and build user trust through transparency.

Understand how FTStatus calculates uptime — absolute (duration or requests) and manual modes — and choose which values to share on your status page.

Why and how to manage monitoring configuration as code for GitOps workflows

Deep dive into the difference between latency and response time, and why both matter for monitoring