Summary report Beta

GET /api/v1/monitors/{id}/summary

Uptime, downtime and response times for one period. Good for an SLA figure or a monthly report.

Needs an X-API-Key header whose owner has access to uptime monitoring in the app. The call counts once against your daily quota. See Monitoring API: getting started for authentication, rate limits and errors.

Query parameters

Name	Type	Description
`from` optional	string \| integer	Start of the window. Default: 7 days before `to`.
`to` optional	string \| integer	End of the window. Default: now. The window can be up to 1830 days.
`region` optional	string	One location code, such as `default`, `na` or `eu`. Filters only `checks`, `upChecks` and the response times. Uptime, downtime and outages always cover the monitor as a whole.

Request

Response

200 · application/json

{
"id": "mon_79ce3cf9c4fa56e98af4",
"from": "2026-08-01T00:00:00.000Z",
"to": "2026-09-01T00:00:00.000Z",
"uptimePct": 99.934,
"upSeconds": 2554740,
"downSeconds": 1680,
"unknownSeconds": 118380,
"maintenanceSeconds": 3600,
"outages": 2,
"mtbfSeconds": 1277370,
"avgResponseMs": 212,
"minResponseMs": 118,
"maxResponseMs": 1934,
"checks": 8527,
"upChecks": 8521,
"usage": { "used": 22, "dailyLimit": 100, "tier": "free" }
}

Response fields

Field	Type	Description
`uptimePct`	number \| null	Up time as a percentage of known time (up plus down), to three decimal places. `null` when the whole window is unknown.
`upSeconds`, `downSeconds`, `unknownSeconds`, `maintenanceSeconds`	integer	How the window splits. Together they add up to the length of the window (up to now).
`outages`	integer	Outages that overlap the window, not counting time that was unknown or maintenance. An outage that fell entirely inside maintenance isn't counted.
`mtbfSeconds`	integer \| null	Mean time between failures: `upSeconds` divided by `outages`. `null` with no outages.
`avgResponseMs`, `minResponseMs`, `maxResponseMs`	integer \| null	Response times of successful checks.
`checks`, `upChecks`	integer	Checks run in the window, and how many passed.

For windows longer than 92 days, the check counts and response times come from daily totals, plus today's checks.

Errors

Status	When
`400`	`from` or `to` isn't a valid time, `from` isn't before `to`, the window is too long, or `region` isn't a location code.
`401`	The API key is missing or invalid.
`403`	The key's owner doesn't have access to uptime monitoring, or the key isn't linked to a workspace.
`404`	No monitor with that id in your workspace.
`405`	The endpoint doesn't accept that method.
`429`	A rate limit or your daily quota was hit. Read `Retry-After`, in seconds.
`500`	Something went wrong on our side. Try again.
`503`	The API is temporarily unavailable. Try again shortly.

Errors are JSON: { "error": "message" }. See Monitoring API errors.

Reports: how the reports count time
Outages: each outage and a timeline
Performance: response times over time