Updated 2026-09-29
Status is multi-region website and API monitoring with confirmed alerts: a probe failure can be verified from other regions before an incident opens, so a single flaky vantage point doesn't wake 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. Each account has one Owner. You can invite teammates as Admins or give them custom roles that you build from a list of permissions (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. You can give a check up to 20 tags to organize them; tags are also available to webhook templates.
Regions
HTTP, TCP, DNS, SSL and ping checks run from our probes and can run from several geographic regions rather than a single vantage point. How many regions a check uses is controlled by your plan and the check's confirmation settings. Heartbeat and domain-expiry checks are evaluated centrally, not from probes.
Confirmation
With confirmation set above 1, a single failed probe doesn't open 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. (Set it to 1 to be alerted on the first failure; heartbeat and domain checks always use 1.) This is what keeps you from getting notified 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 (Enterprise); push notifications are coming with our mobile apps. See the Alerting category.
Incidents
Every confirmed outage is recorded as an incident with a start time, an end time once it resolves, and its cause. From the Incidents page you can acknowledge an incident (so your team knows someone's on it), add internal notes that are never shown on a public status page, and post an update to the incident's timeline (visible on your status page, if the check is on one) without waiting for the next state change. From the same page you can also open an incident manually for something your checks didn't catch on their own.
Signing in and account security
Status doesn't use passwords. You sign in with a one-time code emailed to you, or with a passkey (Face ID, Touch ID, Windows Hello, or a security key) — no code needed. You can add stronger options in Settings → Security: an authenticator app (TOTP) as a second factor, with recovery codes generated when you turn it on in case you lose access to the app. Changing how you sign in (adding or removing a passkey, or turning two-factor on or off) asks you to verify it's you again first.
The dashboard, and the API
Day to day, the dashboard gives every new check the same starting defaults (so you're not reconfiguring the basics each time), lets you act on several checks at once with bulk actions (pause, resume, test now, or delete), and keeps an activity log of who changed what and when. Settings also sets the account timezone (used for reports, summaries and maintenance windows) and the alert channels new checks get by default.
On Enterprise, a scoped public API covers checks, results and uptime, incidents (read and acknowledge), alert channels (read and create) and maintenance windows. The reference is in the dashboard under API docs. See API keys and scopes.
Status pages, maintenance, and reports
Beyond monitoring and alerting, an account can also run public status pages (Professional and Enterprise), schedule maintenance windows that hold alerts during planned work, and view monthly uptime reports (every plan).
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.