The account-wide uptime report
The Uptime report page gives you an account-wide view of how your monitors have been doing, instead of checking each monitor’s own stats page one at a time.
Where to find it
Section titled “Where to find it”Open Uptime report from the sidebar (/uptime-report). It covers every monitor on your account for the
time range you select, or a subset you narrow it to.
Overview
Section titled “Overview”The Overview tab shows account-wide charts and summary numbers built from the monitors in scope over the period you’re looking at: an uptime trend, response-time series, and total check/down counts. Uptime is computed as up time divided by (total time minus time spent in maintenance) - a monitor in a maintenance window doesn’t count against or for the percentage.
Incidents
Section titled “Incidents”The Incidents tab lists confirmed down episodes (incidents) across your account in one feed, instead of paging through each monitor individually. Use this when you want to answer “what went down, and when” for the account as a whole rather than for one specific monitor.
Choosing a time range and scope
Section titled “Choosing a time range and scope”Both tabs work over a time range you pick, and can be narrowed to a subset of your monitors (for example, by tag or type) rather than always showing everything.
Do it with the API or MCP
Section titled “Do it with the API or MCP”The same figures the Overview tab shows are GET /monitor/result/summary?groupBy=account (one aggregate row
over your resolved fleet) or groupBy=monitor (one row per monitor) for a window you name with from/to
(Unix seconds); add bucket=day (or hour/week/month) to get a time series instead of one total, and
sla=99.9 to get an SLA-target comparison alongside the raw uptime percentage. The Incidents tab is
GET /monitor/incident?expand=monitor,recheck narrowed the same way.
An MCP client uses get_uptime_summary (uptime/response-time figures, with the same groupBy/bucket/sla
options) and list_incidents (the incident feed, filterable by monitor, state and severity) - both are the
building blocks for a natural-language summary like “how did my sites do last week”: call get_uptime_summary
for the headline numbers and list_incidents for what actually went wrong. The tool requires monitor: for the
account-wide figure pass monitor="" with groupBy="account". Rows come back in monitor-id order, so “worst
first” is a sort you do yourself - see
Sort a summary, worst first.
GET /monitor/result/summary?groupBy=account&from=1758000000&to=1758604800