Incidents that open — and close — themselves.
A single blip isn't an outage. HeimPulse waits for a real pattern of failures before it tells your customers something's wrong, then clears it the moment the service is back.
Threshold-based detection
Set a failure count and a time window per service — say, 3 failures inside 5 minutes. Cross it, and an incident opens automatically. The service recovers, and it resolves itself. No dashboard babysitting.
per-service thresholds · auto-resolvePost it yourself
Already know what's going on — planned maintenance, a known bug, a vendor outage? Post the update directly instead of waiting for the automatic thresholds to catch up.
title · message · severityWhere it shows up
On your status page
Every incident — automatic or manual — appears on the status page for whichever service it's attached to, with its own timeline of updates.
In your dashboard
A running list you can filter by service or severity, so a busy status page doesn't mean a hard-to-scan history.
Tired of paging on every blip? See how thresholds fix that →
Set your own thresholds.
Free plan, no credit card, set up in a few minutes.