The customer dashboard provides a quick account-wide view. Its first group counts current monitor configurations and states. Its second group summarizes recent reliability.
These values answer different questions. Monitor-state counts describe what the dashboard believes now, while reliability values summarize results collected over time.
Monitor-state metrics
| Metric | What it counts |
|---|---|
| Monitors | Current, non-archived monitors in the dashboard, including paused monitors |
| Up | Active monitors whose latest confirmed status is Up |
| Down | Active monitors whose latest confirmed status is Down |
| Paused | Monitors for which checks are intentionally disabled |
Archived monitors appear under Archived Monitors and are not included in the dashboard total. Deleted monitors are removed.
An active monitor can be Unknown while it waits for enough information from its first check. Unknown does not have a separate metric card, so the Monitors value can temporarily be greater than Up + Down + Paused.
The Up and Down cards count monitors, not individual check records. Open Detailed Logs when you need to count or inspect individual successful and failed checks.
Availability
Availability is the percentage of successful scheduled check results across the account's seven-day dashboard window. It is displayed to three decimal places.
The dashboard combines check counts rather than averaging each monitor's displayed percentage. A monitor checked every minute contributes more results than one checked every hour. See Understand availability percentage before using this value in a report or service commitment.
The value displays - when there are no current dashboard monitors or no check results in the window.
Incidents
Incidents counts confirmed availability incidents that began during the seven-day dashboard window. It does not count every failed check, slow-response event, SSL warning, or domain-expiry warning.
One isolated failed check can lower Availability without opening an incident because an incident requires the configured consecutive-failure and regional-confirmation conditions.
Last incident
Last incident shows the elapsed time since the most recent confirmed availability incident recorded for the account.
This value is not limited to seven days. It is valid for the Incidents card to show 0 while Last incident shows an older time such as 12 days. The first value counts incidents inside the current window; the second identifies the latest known incident even when it began earlier.
No incidents means no previous incident time is available. No data means the dashboard cannot calculate the reliability group because there are no applicable monitor checks.
Active Incidents
The Active Incidents section appears only when one or more current active monitors are Down. It stays hidden when there are no current outages, preventing an empty incident panel from taking up dashboard space.
Select an affected monitor to review its incident history, diagnostics, alerts, and checks around the incident.
Dashboard health message
The message above the metrics uses the same current monitor states:
- All monitored sites are healthy means no active monitor is currently Down.
- Monitors need attention means at least one active monitor is Down.
- Paused monitors are mentioned separately and are not described as healthy.
- With no monitors, the dashboard prompts you to create the first monitor.
When values update
The dashboard requests fresh data approximately every 60 seconds while the page is visible and online. It updates existing monitor cards without intentionally rebuilding the whole list. Temporary request failures use a longer retry delay.
The Last update indicator reflects the newest monitoring or dashboard data in the loaded snapshot. It is highlighted as stale after 10 minutes. A browser may briefly display a private cached snapshot while it requests the newest version.