Browsing Check History
Last updated: 2026-05-03
The Check History page gives you a full, paginated log of every check your monitor has ever run, grouped by check cycle and filterable by outcome. You can open any event to see exactly which regions detected the problem, in what order, and how long it took to reach the confirmation quorum.
Opening Check History
There are two ways to reach it:
- From the Monitors list (compact view): Expand a monitor row, then click Checks in the top-right action bar, or open the ⋮ More menu and choose Check History.
- From the Monitors list (card view): Click the Checks button at the bottom of the card.
The direct URL is /user/monitors/<id>/checks.
The Checks Panel (Inline)
Inside the expanded compact row, the Checks section replaces the old fixed-size list with a filterable, paginated panel:
- All / UP / DOWN filter pills — narrow the list to just the outcome you care about; the selection resets when you collapse and re-expand the row.
- Load more button — fetches the next page of results. Appears only when older results exist.
- View all → button — opens the full Check History page.
Results are individual raw check results (one row per region per cycle). For the grouped, quorum-aware view see the full Check History page below.
The Check History Page
The full-page view groups results into check events — one row per monitoring cycle, rather than one row per raw result. This makes it easy to see the outcome of each cycle at a glance without noise from multi-region duplicates.
Columns
| Column | What it shows |
|---|---|
| Status | Overall outcome of the cycle: UP, DOWN, or PARTIAL |
| Time | Timestamp of the check cycle window |
| Regions | Coloured dot + flag + short name for every region that checked in this cycle |
| Avg Response | Average response time across all regions that cycle |
| Detection | For DOWN events only: how long it took from the first region detecting the failure to quorum being reached |
Status values
| Status | Meaning |
|---|---|
| UP | All regions in this cycle reported the service as reachable |
| DOWN | Enough regions reported failure to meet the confirmation quorum |
| PARTIAL | At least one region reported a failure but quorum was not reached — the global status was not changed to DOWN |
Filtering
Use the All / UP / DOWN / PARTIAL filter buttons in the card header to narrow the event list. The filter is applied server-side, so pagination works correctly even when filtering for rare outcomes like DOWN events across a long history.
Expanding a Check Event
Click any row to expand it and see the detection timeline: a per-region breakdown of that cycle, sorted by when each region completed its check.
Each timeline row shows:
- Region — flag emoji and display name
- Offset — how many milliseconds after the first region’s check this region completed (T+0 for the first, T+Nms for later confirmations)
- Response time — the measured latency from that region
- Details — error message for failed checks, or a “not confirmed (false positive)” note for regions that reported down but were not part of the confirming quorum
For confirmed DOWN events, a “Quorum confirmed in Xms” summary pill appears at the bottom of the timeline. This is the detection delay — the time between the first region detecting the failure and the system confirming the outage across enough regions to trigger an alert.
Enhanced Monitoring Banner
If a monitor is currently in adaptive post-incident mode, a blue banner appears at the top of the Check History page showing when enhanced 15-second checks will expire. During this window you will see a much higher density of check events in the list.
Infinite Scroll
The event list loads 20 events at a time. Scroll to the bottom to automatically load the next page. Loading stops when all events have been fetched, indicated by an “All events loaded.” message.
How Quorum Works
Each monitor is checked independently from every active region. A DOWN event is only confirmed — and an alert only sent — when a minimum number of regions (the quorum) all agree the service is unreachable within a ~20-second window. This prevents a single region experiencing a local network hiccup from triggering a false alert.
The PARTIAL status in check history represents cycles where one or more regions reported failure but the quorum was not met. These are recorded for transparency but do not change the monitor’s global status and do not trigger notifications.
For a deeper explanation of quorum and regional confirmation, see Understanding Per-Region Status and Graphs.