Incident management
PulseStack detects the incident, alerts the right channels, keeps an incident history, and posts updates to your public status page. Detect, alert, communicate, resolve, without you refreshing a dashboard.
Free plan needs no card. Paid plans include a 14-day trial and confirm every failure from multiple locations first.
Detected
checkout.api returned 503 from 3 of 3 locations
Alerted
Slack #ops, PagerDuty on-call, SMS to 2 engineers
Communicated
Update posted to status.acme.io, 214 subscribers notified
Resolved
Recovery confirmed, incident closed, duration 11m 27s
4 stages
Detect, alert, communicate, resolve
8 channels
Every alert route in one place
30s
Fastest check interval, Pro and above
30 days
Check history kept for review
The outage is only half the problem. The other half is the scramble around it.
A background job silently stops and no page fails, so the first alert is a customer email. By then the damage is done and the timeline is a guess.
One shared alias fires for every blip. Engineers mute it, and the one alert that mattered gets buried under noise nobody trusts.
Support has no status page to point to, so the same question lands twenty times while the team is still trying to diagnose the fault.
Once it is fixed there is nothing to review. No start time, no duration, no list of what fired. The post-mortem is built from memory.
A deploy takes the site down for five minutes, alerts fire, and everyone panics over downtime the team scheduled themselves.
Someone thinks it is back, someone else is not sure, and the incident stays open in three different heads instead of one system.
The full incident lifecycle runs on rails. You step in to fix the fault, PulseStack handles everything around it.
Monitors run on your interval and double-check each failure, confirming uptime checks from multiple locations. Once it is confirmed, an incident opens.
The channels you chose fire straight away. Route each monitor to different places so the right people get paged, not everyone.
Post an update and it lands on your public status page. On Pro and above your subscribers are notified automatically.
When the monitor recovers, PulseStack confirms it, sends the recovery alert with the total duration, and closes the incident into history.
A confirmed failure fans out to every channel you configured. Automatic re-checks and multi-location confirmation mean a single blip never wakes anyone, and recovery alerts go to the same channels.
Not just web pages. If a background job, an API, a service port, a certificate or a domain goes wrong, PulseStack treats it as an incident the same way.
Status codes, redirects, response time
Text present or missing on the page
Reachability of any host
A specific service port is open
JSON endpoints with custom headers
Cron and background jobs check in
09:16 Investigating
We are aware checkout is returning errors and are working on a fix. Next update in 15 minutes.
A public status page turns twenty support tickets into one page. Post an update as the incident evolves, run a maintenance window for planned work, and let subscribers get the news automatically on Pro and above.
Pick any combination for each monitor, and recovery alerts follow on the same channels. SMS is included on the Team and Enterprise plans and available as an add-on on Starter and Pro.
Route each monitor to PagerDuty or Slack, confirm failures from multiple locations, and keep a clean incident history for every review.
Point customers at a branded status page instead of answering the same ticket twenty times, and let subscribers self-serve the updates.
No on-call rota needed. Heartbeat monitors catch silent job failures and an SMS reaches you wherever you are on the Team plan.
| Stage | By hand | With PulseStack |
|---|---|---|
| Detect | Wait for a customer to email | Confirmed check on your interval |
| Alert | One shared alias for everything | Eight channels, routed per monitor |
| Communicate | Manual replies to each ticket | Status page, subscribers notified |
| Resolve | Closed in someone's head | Recovery confirmed and logged |
| Review | Rebuilt from memory | Timeline in incident history |
Schedule a maintenance window before you deploy and PulseStack suppresses alerts for the affected monitors and shows the window on your status page. No false pages, no customer panic, no incident that should never have opened.
When a monitor check fails, PulseStack confirms the failure from multiple locations before opening an incident automatically. Any of the 6 core monitor types - HTTP, Keyword, TCP Ping, Port, API and Heartbeat - can trigger detection, and every incident is recorded in your history.
PulseStack supports 8 native alert channels: email, SMS, Slack, Microsoft Teams, Discord, PagerDuty, Telegram and webhooks, and Zapier connects through webhooks. SMS and voice are available as an add-on and are included on the Team and Enterprise plans.
Yes. You can post updates to a public status page and schedule maintenance windows. Paid plans add custom domain and branding plus password protection, and on Pro and above your subscribers are notified of updates.
Detection speed depends on your check interval. The Free plan checks every 5 minutes, Starter checks every 60 seconds, and Pro, Team and Enterprise check every 30 seconds, so higher plans open incidents sooner.
Every incident is stored with its timeline and duration from open to resolve, giving you incident detection and history for post-incident reviews. Maintenance windows are kept separate so planned work never clutters your outage record.
No. The Free plan requires no card and includes email alerts and one status page. Every paid plan comes with a 14-day free trial that also needs no card, and annual billing saves 20%.
Detect, alert, communicate and resolve on one platform. Start free with no card, and add the faster intervals when you are ready.