Monitoring built to tell you the truth

A deep look at Status: what each check type watches, how confirmation stops false alerts, how alerts reach you, and how you keep your users informed.

Seven check types, one dashboard

Point Status at anything that needs watching. Probe-based checks run on their own interval and report response time, not just up or down; heartbeat and domain checks track deadlines instead.

  • HTTP — status code, response keyword, and TLS verification, with custom headers and basic auth
  • TCP — connect to any port, optionally send a probe string and match the reply
  • DNS — resolve A, AAAA, CNAME, MX, TXT or NS records against a chosen resolver
  • SSL & domain — certificate validity and domain-registration expiry, tracked separately from uptime
  • Ping — ICMP echo with a configurable packet-loss threshold
  • Heartbeat — a dead-man's-switch URL your job calls in; miss the grace period and Status raises it

Confirmed by other regions before we notify you

With confirmation on, a single failed probe doesn't open an incident on its own: Status asks other regions to recheck first, so a local network blip doesn't turn into a false alert. You choose how many regions must agree (one means alert on the first failure).

  • Checks that run from probes can require confirmation from several distinct regions, up to your plan's limit
  • On first failure the check enters a pending state while other regions are asked to recheck
  • An incident only opens once enough distinct regions agree the check is down
  • If the fleet can't reach enough independent regions, Status degrades gracefully rather than staying silent

Email and fully-customizable webhooks

Wire each check to the channels that should hear about it, with thresholds tuned per check rather than one setting for the whole account.

  • Email alerts, verified before they can fire, and on Enterprise, webhooks to any URL you control
  • Ready-made payloads for Slack, Discord, Microsoft Teams, PagerDuty and Opsgenie, or your own template; custom headers per webhook; deliveries HMAC-SHA256 signed (on by default)
  • Per-check confirmation counts, re-alert intervals (Professional and Enterprise), and escalation to a second channel if unacknowledged (Enterprise)
  • Failed deliveries retry with backoff; a channel that keeps failing is disabled and you're emailed about it

Keep your users informed without the extra tooling

A hosted public status page for the checks you choose, with subscribers who find out the moment something changes. Status pages are included on Professional and Enterprise.

  • Optional password gate for status pages that shouldn't be fully public
  • Email subscribers with double opt-in, so you build a list you can actually notify
  • Scheduled maintenance shows up as a banner instead of an unexplained outage
  • Group checks into sections with 90-day uptime bars, your logo and a light or dark theme
  • A JSON version of every page for your own tooling

Work incidents as a team

Every outage is recorded as an incident your team can pick up, annotate and communicate about.

  • Acknowledge an incident so the team knows it's handled; this stops re-alerts and escalation
  • Internal notes that never appear publicly
  • Public updates (Investigating, Identified, Monitoring, Resolved) that post to your status page
  • Open an incident by hand for problems your checks didn't catch

Your team, with the right access

Give each person only what they need, and keep a record of what changed.

  • Owner and Admin roles, Member and Viewer presets, and custom roles built from permissions
  • Seats per plan (1 / 3 / 20), extra seats as an add-on
  • Passwordless sign-in with emailed codes or passkeys; optional authenticator-app 2FA with recovery codes
  • An activity log of who changed what, and support access you switch on and off

Planned work doesn't have to notify anyone

Schedule a window over one check, several, or your whole account. Alerts are held for the duration, and your status page can show the window instead of an outage.

  • Pin a window to specific checks or apply it account-wide
  • Alerts are held for the window's span by default; if a check is still down when the window closes, you're alerted then
  • Three switches per window: hold alerts, show on the status page, notify subscribers
  • Windows can recur daily, weekly or monthly
  • Optionally surface the window as a banner on your public status page

Numbers you can hand to a customer or a boss

Monthly uptime reports turn your monitoring data into something you can share or drop straight into an SLA email — no spreadsheet required.

  • Monthly uptime per check on every plan, in the dashboard and with your summary emails
  • Past months available back to your plan's retention window — the latest month on Starter and Professional, about 3 months on Enterprise
  • CSV and PDF downloads on Professional and Enterprise

Secrets protected, webhooks guarded

The details that let you point Status at internal endpoints and webhook receivers without worrying about what's sitting behind them.

  • Basic-auth credentials and custom webhook headers are encrypted at rest (AES-256-GCM)
  • Webhook destinations are checked for private, loopback and metadata addresses — at save time and on every delivery and redirect
  • Webhook deliveries can be HMAC-SHA256 signed (on by default) so your receiver can verify they came from Status
  • API keys and probe tokens are stored as one-way hashes, never in recoverable form
  • On Enterprise, a scoped public API and API keys for reading results, managing checks, listing and adding alert channels, or scheduling maintenance windows from your own tooling

Built for anyone who can't afford to be the last to know

From a single site to a fleet of services across teams.

SaaS & API teams

Watch every service and dependency your product relies on, and notify the right on-call engineer with a webhook into your existing tools (Enterprise).

Agencies managing client sites

Give clients their own status pages while keeping every check across every client in one account. White-label pages (no "Powered by" footer) and up to five pages are on Enterprise.

Internal ops & SRE teams

Use heartbeat checks as a dead-man's-switch for cron jobs and background workers, alongside HTTP and TCP checks for everything else.

Ready to know the moment something breaks?

We're launching soon. Optional multi-region confirmation keeps one flaky vantage point from sending you an alert.

Coming Soon