Uptime
Start free
Back to Uptime

Product example · Fictional data

From a failed check to an informed team.

Follow a Checkout API outage across three independent regions. This read-only example uses one-minute Pro checks and a two-region confirmation rule.

Example workspaceIllustrative data · Pro checks

INC-1042 · HTTP monitor

Checkout API

checkout.acme.dev

Confirmed outage

2 of 3 regions confirm the failure

Two consecutive failures per region. One-minute checks in this example.

  • VirginiaHTTP 503
  • FrankfurtHTTP 503
  • OregonHTTP 200
Team notifiedEmail deliveredSlack delivered

Incident timeline

Example times · UTC

  1. Investigation opened

    Virginia and Frankfurt return HTTP 503. One failed check starts an investigation; the team has not been alerted yet.

  2. Outage confirmed

    Both regions fail their next check. Two consecutive failures in two of three regions meet this monitor’s confirmation rules.

  3. Team notified

    Email and Slack delivery succeed. The alert includes the affected monitor and regional evidence.

  4. Customer update published

    An operator publishes a public update: “We are investigating errors affecting checkout. Our team is working to restore service.”

Evidence before interruption.

A single failed check opens an investigation. Repeated failures and regional agreement determine when an outage is confirmed. Thresholds are configurable for each monitor.

What happens after recovery?

When the affected regions meet the configured recovery threshold, the incident resolves. Connected destinations can receive recovery notifications, and customers can follow public updates.

View the customer status page
Start monitoring for free

10 monitors · Five-minute checks · No credit card