Read the current state
The dashboard brings together monitors, groups, and Nexus Points for your selected organization. Start with affected services, then open a monitor to inspect its recent checks and incident history.
| Signal | How to use it |
|---|---|
| UP | The latest recorded check passed its configured conditions. |
| DOWN | A check or aggregate condition failed. Open its details to find the reason. |
| PENDING or unknown | There is not yet a usable result or evaluation. Do not treat it as healthy. |
| Paused | Monitoring has been deliberately paused. An old successful result is not a new check. |
| DEGRADED on a Nexus Point | A non-critical condition failed while critical conditions passed. |
A result describes an observation at its recorded time. If the timestamp is old, investigate missing checks before relying on the status color.
Organize the workspace
Assign a group name when creating or editing a monitor to collect related endpoints, such as production services or a customer-facing application. Add tags to describe environment, ownership, or purpose. Use the dashboard's available search, filters, and view controls to narrow the list, then open a group for its service detail view.
Groups organize resources; Nexus Points evaluate dependency conditions. Use a group to browse your API monitors and a Nexus Point to decide whether the API service is usable.
Investigate a result
Open the monitor and inspect its recent check history, latency, HTTP status when available, and error message. Compare failures with incident and maintenance times. With multiple monitoring locations, review the location results rather than assuming every region observed the same failure.
Latency measures the probe's check, not every part of a customer's browser experience. HTTP success also depends on configured keyword checks and other monitor options.
Uptime and display preferences
Use the available 24-hour, 7-day, and 30-day uptime periods to compare recent service behavior. A young monitor cannot provide a full month of collected observations. Missing observations are not proof of uptime.
In Settings → Preferences, choose your display timezone, ping-history length, default uptime period, and theme. These are personal preferences. The product tour can also be started again here.
Pro organizations can export data for analysis; see exports and backups.