Updated 2026-06-08
Status is multi-region website and API monitoring with confirmed alerts: a probe failure is verified from other regions before an incident opens, so a single flaky vantage point never wakes you up for nothing. Everything in the product builds on a handful of concepts.
Accounts
An account is your organization's workspace — its checks, alert channels, status pages, billing, and team all live under one account. You can invite teammates with different roles (see Invite your team and choose roles).
Checks
A check is one monitored target: a URL, a host and port, a DNS record, a certificate, a domain registration, or an inbound heartbeat. Status supports seven check types — HTTP, TCP, DNS, SSL, domain, ping, and heartbeat — each with its own configuration. See the Checks category for a page per type.
Regions
Checks run from multiple geographic probe regions rather than a single vantage point. How many regions a check uses is controlled by your plan and the check's confirmation settings.
Confirmation
A single failed probe never opens an incident by itself. Before a check is marked down, other regions are asked to independently re-check it; an incident only opens once enough distinct regions agree. This is what keeps you from getting paged over one region's network blip. Full detail in How multi-region confirmation works.
Alerts
When a check goes down (or recovers, or a certificate is about to expire), Status notifies the alert channels attached to it — email or webhook. See the Alerting category.
Status pages, maintenance, and reports
Beyond monitoring and alerting, an account can also run public status pages, schedule maintenance windows that suppress alerts during planned work, and export monthly uptime reports as CSV or PDF.
If you only read one more article, make it How multi-region confirmation works — it's the feature that makes Status's alerts trustworthy instead of noisy.