Skip to content

The account-wide uptime report

View as Markdown

The uptime report (/sites/uptime) shows every monitor on your account side by side: uptime for a period, and a feed of incidents across all of them. It is the page to open when someone asks “how did everything do this week?”. The full guide to the report’s tabs, filters and exports is Uptime reports; this page covers what matters for incidents.

  1. Open the uptime report (/sites/uptime).
  2. Choose a Period: 6 hours, 1 day, 7 days, 14 days, 30 days or 90 days.
  3. Narrow it with Filters - a task name or URL, Type and Tags; Reset clears them.
  4. Open the Incidents tab. It lists incidents for the monitors and period in view, split into Current (ongoing) and Resolved, each with its monitor, Started and Ended times, check count and a Maintenance marker when it happened inside a maintenance window. Times are shown in your local time.
  5. Click an incident (Open incident details) for its timeline, errors, snapshot and note.

The other tabs are Overview, Monitors, Analytics and Map.

From a monitor’s row, Reset Stats permanently deletes that monitor’s uptime spans and counters (“This permanently deletes all uptime spans and counters. The action cannot be undone.”). Use it only when the history is meaningless - for example after pointing a monitor at a completely different site. API: POST /monitor/{monitorId}/reset-stats (a job; requires an Idempotency-Key).

Report view Operation MCP tool
Uptime per monitor for a period GET /monitor/result/summary?monitor=...&from=...&to=... (rows in monitor-id order; no sort - rank them yourself) get_uptime_summary
One combined figure for the account GET /monitor/result/summary?groupBy=account&from=...&to=... (at most 30 days) get_uptime_summary(monitor="", groupBy="account", ...)
Incidents across monitors GET /monitor/incident?from=...&to=... (filter state=open for current ones) list_incidents
One incident in detail GET /monitor/incident/{id}?expand=recheck get_incident

A step-by-step recipe for a period summary is in Reading results and incidents.