View Uptime Monitor Response Log History

This endpoint allows you to fetch a chronological list of individual HTTP responses logged during uptime monitoring for a specific resource, identified by its unique id. The log entries include precise response metadata—such as timestamp (checked_at), response time in milliseconds, HTTP status code, response headers, and whether the response was considered up and approved from the monitoring location.

This log history provides critical visibility into how a resource behaved over time from specific regions. It’s designed to help SREs, DevOps engineers, and monitoring analysts diagnose transient issues, verify downtime claims, review HTTP performance at specific points, and ensure SLA compliance.

You can optionally narrow the scope of the response by using query parameters such as start_date and end_date to define a time range, and limit to restrict the number of results. Each response object includes granular network-level data that is crucial for analyzing uptime reliability and service responsiveness at a per-request level.

Recommended Use Cases:
  • Reviewing detailed uptime behavior during incident post-mortems.
  • Auditing resource availability over a specific reporting period.
  • Cross-verifying with synthetic test results or external monitoring data.

Authorization: Bearer YOUR_TOKEN

Path Parameters
  • id string
    The unique ID of the uptime monitor. Example: '6635f9cd-5dc2-4deb-93ad-7088c7b51f59'
Query Parameters
  • start_date (optional) string
    Start date to retrieve logs from. Format: 'YYYY-MM-DDTHH:mm:ssZ'. Example: '2025-07-06T21:37:01Z'
  • end_date (optional) string
  • limit (optional) positive integer
ResponseThis section is used to view the possible HTTP response codes returned by the API. These codes indicate the status of a request, such as 201 (Created), 401 (Unauthorized), 409 (Conflict), or 422 (Unprocessable Entity).