The check history is a log of every HTTP request PulseAPI has made to a monitor. It's the primary tool for diagnosing problems, understanding patterns, and reviewing past incidents.
How to Access Check History
- In the left sidebar, click Monitors.
- Click the monitor whose history you want to view.
- Scroll to the Check History section at the bottom of the monitor detail page.
What Each Row Shows
| Column |
Description |
| Time |
When the check was performed (in your configured timezone) |
| Status |
Up or Down — the overall result of the check |
| HTTP Status Code |
The status code returned by the endpoint (e.g., 200, 503) |
| Response Time |
How long the request took in milliseconds |
| Error |
If the check failed, a brief description of the failure reason |
| Type |
Whether the check was scheduled or manually triggered |
Common Error Messages
| Error |
Meaning |
Timeout |
The endpoint didn't respond within the configured timeout period |
Connection refused |
The server rejected the connection — likely down or firewall-blocked |
DNS resolution failed |
The hostname couldn't be resolved to an IP address |
SSL certificate expired |
The SSL certificate has expired |
SSL hostname mismatch |
The SSL cert doesn't cover this hostname |
HTTP error: 503 |
The server returned a Service Unavailable response |
HTTP error: 4xx |
The server returned a client error (the expected code didn't match) |
Filtering and Searching History
- Use the Status filter to show only failed checks, only successful checks, or all checks
- History is sorted by most recent first — scroll or paginate to see older entries
- How far back history is retained depends on your plan (7 days on Free, up to 365 days on Team)
Relating Check History to Incidents
When an incident exists for a monitor, you can often correlate the incident's start time with failing check history entries. The check history shows what the endpoint returned during the incident window, which helps diagnose the root cause.
Related Articles
Still have questions? Contact support.
Related Articles
Running a Manual Check
A manual check triggers an immediate on-demand HTTP request to your monitor's endpoint, outside of the normal scheduled interval. The result appears in your check history just like a scheduled check. When to Use a Manual Check After making a ...
Viewing Incident History
The Incidents page shows a full history of all incidents on your team — open, acknowledged, and resolved. This article explains how to navigate and filter the list. Opening the Incidents List In the left sidebar, click Incidents. Filtering Incidents ...
Check Intervals Explained
The check interval is how often PulseAPI sends a request to your monitor. This article explains what intervals are available, how your plan affects them, and how to choose the right interval for each monitor. What Is a Check Interval? Every monitor ...
Check Interval Limits by Plan
The fastest check interval available to you depends on your plan. This article explains what each plan supports and how to get faster checks. Minimum Intervals by Plan Plan Minimum Interval Available Options Free 60 seconds 60s only Starter 60 ...
Understanding Response Times
Every check PulseAPI performs records how long the HTTP request took. This article explains what response time means, what affects it, and how to interpret the data. What PulseAPI Measures Response time is measured from the moment PulseAPI initiates ...