Hours of day report Beta
GET /api/v1/monitors/{id}/hours-of-day
The average response time at each hour of the day, across the whole window. Use it to spot a site that slows down at busy times.
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 92 days. |
region optional | string | One location code. |
utcOffsetMinutes optional | integer | Shifts the hours into your local time, from -840 to 840. For example, 60 for British Summer Time. Default 0 (UTC). |
Request
Response
200 · application/json
- {
- "id": "mon_79ce3cf9c4fa56e98af4",
- "from": "2026-09-10T09:31:00.000Z",
- "to": "2026-09-17T09:31:00.000Z",
- "utcOffsetMinutes": 60,
- "hours": [
- { "hour": 0, "checks": 28, "avgResponseMs": 176 },
- { "hour": 1, "checks": 28, "avgResponseMs": 171 },
- …
- { "hour": 23, "checks": 28, "avgResponseMs": 190 }
- ],
- "usage": { "used": 25, "dailyLimit": 100, "tier": "free" }
- }
hours always has 24 rows, from hour 0 to 23 in the offset you asked for. checks counts every check in that hour; avgResponseMs uses successful checks only and is null when there were none. An offset outside the allowed range is brought back to the nearest limit, and the response shows the offset that was used.
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.
Related
- Reports: how the reports count time
- Performance: response times over time
- Probes: response times per location