Take a dashboard tour
Start with the overview
The dashboard is the first page you see after signing in. Think of it as a morning briefing: it summarizes what is healthy, what needs attention, and what changed recently.
The dashboard at a glance
The overview prioritizes current health, recent activity, and items that need attention.
Good morning
Here is what needs your attention.
Online
12
Open incidents
0
30-day uptime
99.98%
The dashboard is not intended to contain every technical detail. Select a monitor or incident when you need to investigate further.
Understand the main numbers
| Dashboard item | What it answers | When to act |
|---|---|---|
| Operational monitors | How many services are currently healthy? | No action is normally needed |
| Degraded or down | Is anything currently failing or unstable? | Open the affected monitor |
| Open incidents | Has Uptime confirmed a problem? | Open the incident and follow the response timeline |
| Uptime percentage | How consistently was the service available? | Compare the period and investigate repeated gaps |
| Response time | How quickly did the service answer? | Look for sustained changes, not one isolated slow check |
What the activity bars mean
Each small bar represents a period of recent monitor activity. The number of days shown comes from Settings → Preferences, and the same preference is used on both the dashboard and monitor list.
- Green means checks were healthy for that period.
- Red means confirmed failed observations occurred.
- A neutral or muted segment can represent maintenance or missing history.
- A short red segment is evidence of a brief event; open the monitor to see its exact time and cause.
Do not estimate an outage duration only from the width of a bar. The monitor detail chart and event row use exact timestamps.
Use the left navigation
Monitors
See every service you watch. Search and filter the list, group monitors into projects, pause or resume checks, and open a monitor’s detailed history.
Incidents
See investigations, confirmed outages, acknowledgments, updates, and resolutions. This is where your team coordinates an unexpected service problem.
Maintenance
Plan work that may affect a monitored service. Scheduled windows keep planned activity visually distinct from unexpected downtime.
Alerts
Control monitor alert behavior and review grouped notification delivery. Use this page when a notification was delayed, skipped, retried, or failed.
Status pages
Create customer-facing pages that translate internal monitors into familiar product components such as Dashboard, API, or Checkout.
Reports
Review longer-term availability and performance. Reports help answer trend questions; the dashboard answers what is happening now.
Team
Invite teammates, choose roles, and configure each member’s email notification preferences.
Settings
Manage your profile, workspace, appearance, monitoring defaults, integrations, billing, and dashboard preferences.
Open a monitor for details
Select any monitor name to open its detail page. This page combines current configuration and historical evidence.
You will find:
- the current health state and latest check;
- an uptime and performance chart with selectable time ranges;
- an events row for incidents and maintenance;
- regional comparison;
- check history with filters and pagination;
- monitor metadata and configuration.
Hover over chart events for a short explanation. Select an incident when you need the full activity timeline.
Choose the right time range
Short ranges such as 1h, 6h, and 12h are useful during a current investigation. Longer ranges such as 7d, 30d, and 90d reveal trends.
Changing the range does not change how often checks run. It changes only the history shown in the chart.
For performance:
- Average shows the general level;
- Median shows a typical response with less influence from unusual spikes;
- p95 shows the slower experience near the edge of normal behavior.
If those terms are unfamiliar, start with average. Use p95 when investigating whether a minority of visitors may be seeing slow responses.
Switch organizations safely
If your account belongs to more than one organization, confirm the selected workspace before creating or changing a monitor. Monitors, incidents, team membership, integrations, and billing belong to the selected organization.
The organization selector changes the workspace context; it does not copy resources between organizations.
Recommended first-day checklist
- Create one website monitor.
- Confirm every selected region has reported.
- Invite at least one teammate if somebody else helps respond.
- Review notification preferences.
- Add planned work to the maintenance calendar.
- Create a draft status page if customers need public updates.