Read monitor results and history

Current health comes first

Open Monitors, then select a monitor. The state near the monitor name answers what Uptime currently knows.

The health summary explains the current state. The row beneath it shows the check cadence, configured probe regions, and latest check age, with a shortcut to certificate details. A Check overdue notice means the displayed result is older than expected.

A failed check is not always an outage

A check is one attempt from one location. An incident is a higher-confidence conclusion based on the thresholds and regions you selected.

One check can fail because of a temporary network route, a slow reply, a changed keyword, or a local provider issue. Uptime keeps that evidence visible without automatically treating every failure as customer-wide downtime.

Read the availability bars

On the monitor detail page, availability appears beneath the response chart. Select the strip, or focus it and press Enter, to read the intervals and their states. Green means operational, red means downtime, and gray means no data. Missing intervals do not inherit the last known state.

The preference under Settings → Preferences controls how many days appear on the separate dashboard and monitor-list history strips.

The strip is a summary, not a stopwatch. For the exact start and end of an event, use the detailed chart or open the incident.

Use the performance chart

Use the Reporting window selector above Performance to update the uptime, average response, chart, availability timeline, and regional summaries together. Latest response remains the most recent individual check. Changing the chart metric or toggling regional lines does not change the summary's average response.

Choose a range that matches your question:

• 1h, 6h, or 12h for something happening today;
• 24h or 7d for recent patterns;
• 30d or 90d for trends and reporting.

The chart uses larger time buckets for longer ranges so it remains fast. That means a short event may appear as a narrow marker rather than a wide colored block.

Average, median, and p95

• Average adds all response times and divides by the number of checks.
• Median is the middle result and represents a typical check.
• p95 is slower than most results and helps reveal poor experiences hidden by an average.

Start with average. Compare median and p95 when the chart looks stable but some users still report slowness.

Understand the Events row

The Events row aligns operational context with the chart.

• An incident marker identifies unexpected confirmed impact.
• A maintenance marker identifies planned work.
• Hovering an event shows its title, state, and exact time.
• Selecting an incident opens its complete history.

Maintenance can also appear as a neutral chart overlay to show which response-time data occurred during planned work. It should never use the same visual treatment as an unexpected outage.

Compare regions

Regional comparison shows whether one location behaved differently. If US East failed but US West and Europe passed, the service may have a local route or edge problem rather than a worldwide outage.

The Probe regions list sits below the full-width chart. Each row shows the latest result and its age, uptime, and average response for the reporting window. Search by region name, filter by Up, Down, or Pending, or sort by response time. Failed and pending regions appear first by default. Results are paginated in groups of eight so adding probes does not create an endless stack of cards. The arrow on a region opens its filtered check history.

Use Compare regions to search for and overlay up to four regional lines. The All regions line continues to include every configured region. Use Previous period to compare with the preceding time window.

Local impact can still be real. Use the evidence to describe the affected audience accurately instead of assuming either “everything is down” or “nothing is wrong.”

Open the check log

The check log is the most detailed evidence view. Filter it by time, status, and region rather than scrolling through every observation.

Each row can include:

• when the check ran;
• which region ran it;
• whether it passed;
• how long it took;
• the protocol result;
• a safe failure explanation.

Use the check log when you need to answer “what exactly failed?” Use the incident timeline when you need to answer “what did our team do about it?”

Use Compare carefully

The optional previous-period comparison places the preceding equivalent range beside the current one. For example, comparing seven days uses the seven days immediately before the current range.

Compare is useful for questions such as:

• Is response time slower than last week?
• Did a deployment change normal performance?
• Is the current pattern unusual?

It does not compare two arbitrary dates and it does not change incident calculations.

A simple investigation routine

Continue with Troubleshoot a failed check or Respond to an incident.