Pulse AI automatically analyzes incidents and generates a summary of likely causes and recommended next steps. This article explains how it works, which plans include it, and how to use it.
What Pulse AI Analyzes
When an incident is created, Pulse AI examines:
- The check history leading up to the failure (status codes, response times, error messages)
- The incident's characteristics (severity, start time, affected monitor)
- Historical patterns for this monitor (response time baselines, past incidents)
From this data, Pulse AI generates:
- A plain-language summary of what likely happened
- Possible root causes to investigate
- Recommended next steps to diagnose and resolve the incident
Plan Availability and Limits
| Plan |
Pulse AI Access |
Daily Limit |
Monthly Limit |
| Free |
Not available |
— |
— |
| Starter |
Available |
25/day |
500/month |
| Professional |
Available |
100/day |
2,000/month |
| Team |
Available |
Unlimited |
Unlimited |
Limits reset at midnight UTC (daily) and on the 1st of each month (monthly).
How Analysis Works
Pulse AI analysis runs automatically: approximately 30 seconds after an incident is created, PulseAPI queues an analysis job. The analysis usually completes within 30–60 seconds of being queued.
On the incident detail page, you'll see the Pulse AI section with one of these states:
- Pending — analysis has been queued and will run shortly
- Analyzing — analysis is in progress
- Completed — analysis is ready to view
- Failed — analysis failed; you can retry manually
The page polls for updates every few seconds — you don't need to refresh.
Manually Triggering Analysis
If an incident was created before Pulse AI was available on your plan, or if auto-analysis was skipped or failed, you can trigger it manually:
- Open the incident detail page.
- Scroll to the Pulse AI Analysis section.
- Click Analyze (or Retry if a previous attempt failed).
The analysis runs and the result appears within about a minute.
Note: Manual analysis uses one quota unit from your daily and monthly limits.
Reading the Analysis
The analysis appears as a formatted text block. It typically includes:
- What happened — a plain-language description of the failure pattern
- Likely causes — ranked list of possible root causes based on the data
- Recommended actions — specific steps to investigate and resolve the incident
The analysis is a starting point for your investigation, not a definitive diagnosis. Always verify the AI's suggestions against your own knowledge of the system.
Related Articles
Still have questions? Contact support.
Related Articles
What Is an Incident?
An incident is PulseAPI's record of a problem with one of your monitors. This article explains what triggers an incident, what information it contains, and how it relates to alert rules. What Creates an Incident Incidents are created automatically — ...
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 ...
Pulse AI Limits by Plan
Pulse AI analyses are rate-limited on Starter and Professional plans. This article explains the limits, how they reset, and what happens when you reach them. Limits by Plan Plan Pulse AI Daily Limit Monthly Limit Free Not available — — Starter ...
Resolving an Incident
Resolving an incident closes it — the problem is fixed and the endpoint is healthy. Incidents can be resolved automatically by PulseAPI or manually by a team member. Prerequisites: You must be a team Owner, Admin, or Member to resolve incidents. ...
Acknowledging an Incident
Acknowledging an incident tells your team that someone is aware of the problem and actively working on it. It moves the incident from Open to Acknowledged status. Prerequisites: You must be a team Owner, Admin, or Member to acknowledge incidents. ...