Skip to main content
Back to Features
Incident management
Paid plans

One record per outage, from first alert to recovery

Each confirmed problem becomes an incident with its severity, duration and your team's notes, and closes on its own when the check passes again.

Detected and opened automatically
5 severity levels
Notes on every incident
3 ongoing incidents · auto-detected from your checks
IncidentSeverityStatusResourceAge
Domain suspendedCRITICALOngoingshop.acme.io2m
SSL expiringHIGHOngoingmail.acme.com6h
Domain expiringMEDIUMOngoinggetfound.io1d
Uptime downCRITICALResolvedapi.acme.com3d
3 ongoing incidents · domain suspended on shop.acme.io
On Free you still get the email alert when something breaks.Compare all plans

Every incident, classified and tracked

Each incident carries a status, a severity level, its type, how many times it has recurred, and how long it has been open, so the team sees what matters first.

SiteStatusLevelTypeDuration
shop.acme.ioOngoingHighSSL Check×21h 15m
acme.ioResolvedCriticalTimeout×61h 58m
blog.acme.devResolvedCriticalTimeout×106h
mail.acme.comResolvedMediumDomain expiration · 25 days4h

Incidents open automatically for uptime down, SSL check failures, SSL expiration, domain expiration, and domain suspension. Severity, occurrence count, and duration are tracked until the incident closes; you can add a description to any incident.

How WebPixie manages incidents

When a check confirms a problem, WebPixie opens an incident automatically. Incidents are detected for uptime going down, an SSL check failing, an SSL certificate approaching expiry, a domain approaching expiry, and a domain entering a suspended state, such as a registrar hold. Each incident records what triggered it, the affected resource, and a severity.

Incidents move through a full lifecycle: detection, notification, tracking, and closure. While an incident is open, WebPixie re-checks the affected monitor more frequently than its normal interval to catch recovery sooner and measure how long the outage lasts. When the underlying check recovers, for example a site comes back up, WebPixie closes the incident automatically and marks it resolved, so the board reflects the current state without manual cleanup.

Severity runs across five levels, from INFO to LOW, MEDIUM, HIGH, and CRITICAL. While an incident is open, repeated failures raise its occurrence count instead of sending new alerts, so you get a notification when it opens, when its severity changes significantly, and when it closes.

The full configuration options are in the incident management docs.

01

Incidents open automatically on confirmed failures

Uptime, SSL, and domain, with no manual setup

You do not create incidents by hand. WebPixie opens one when a check confirms a problem: uptime going down, an SSL check failing, an SSL certificate nearing expiry, a domain nearing expiry, or a domain entering a suspended state such as a registrar hold. Each incident captures the trigger, the affected resource, and a severity, so the response starts from a clear record.

02

Automatic closure keeps the board accurate

Incidents close when the check recovers

A site that comes back up should not leave a stale alert behind. While the incident is open, WebPixie re-checks that monitor more frequently than its normal interval, so a recovery is caught sooner and the outage duration is measured accurately. When the underlying check passes again, WebPixie closes the incident automatically, marks it resolved, and timestamps it, so the dashboard shows what is actually broken right now instead of a backlog you have to tidy by hand.

03

Five severity levels, with occurrence tracking

INFO to CRITICAL, recurrences counted

Not every incident deserves the same response. WebPixie assigns one of five severities, from INFO to CRITICAL, and counts how many times a problem recurs. Uptime, SSL check, and domain suspended incidents open at a fixed severity, while SSL and domain expiration incidents escalate through tiers as the deadline gets closer. While an incident is open, repeated failures raise its occurrence count instead of sending new alerts, so you get a notification when it opens, when its severity changes significantly, and when it closes.

04

Notifications routed to the right channel

Email, Slack, and webhook by plan

Incident creation and closure can notify your team by email on every plan, and through integrations such as Slack and webhooks on higher plans. You control notifications per resource, so a critical production incident and a low-priority staging one do not have to reach the same place.

05

A written record of what happened

A note on every incident

You can add a note to any incident: what broke, what you changed, who is looking at it. Resolved incidents keep their duration and note, so the next time the same problem opens, you can see what happened last time.

Incident tracking in one place

You get a notification when an incident opens, when its severity changes significantly, and when it closes.

Everything you need to monitor a website. In one workspace.

A quick look at other WebPixie features.

Why teams choose WebPixie for incident management

Less alert noise

Retry logic confirms failures before an incident opens. While an incident is open, repeated failures raise its occurrence count instead of sending new alerts, so you get a notification when it opens, when its severity changes significantly, and when it closes.

Your whole site in one workspace

Tracked incidents sit in the same workspace as uptime, SSL, DNS, domain, and link health signals, so response context stays together.

Automatic from detection to closure

Incidents open on confirmed failures and close when the underlying check recovers, with a timestamped resolved history you can review.

Frequently Asked Questions

Common questions about incident management.

WebPixie notices an outage on the next scheduled check, so the check interval you set for each monitor decides how quickly a failure is seen. The interval can be anything from 30 seconds to 24 hours, depending on your plan. Check options such as the method, headers, status codes, keywords and authentication are available on every plan. After a failing check, a timeout or connection error is retried in place and, on paid plans, verified from the monitor's other selected locations, which adds a short delay but keeps blips from paging you. A wrong status code or a keyword mismatch counts as down on the first check. The notification goes out as soon as the failure is confirmed, and the open incident is then re-checked more often so recovery is seen sooner. Endpoints that page people work best with a short interval, while low-risk pages can stay on a longer one. You can see how checks are confirmed under uptime monitoring and the interval for each plan on the pricing page.

An incident opens when an uptime check confirms a site or endpoint is down, when the SSL check fails, when a certificate or domain gets close to expiry, and when a domain is suspended. Each incident records its type, severity, start time and duration, and it closes on its own once the problem clears. SSL and domain expiry incidents also raise their severity as the date gets closer. Other results, such as DNS changes, broken links, sitemap signals and security header findings, stay in the dashboard as findings with fix guidance and do not open incidents. The Incident Management page shows how alerts and incidents work together, and the Uptime Monitoring and Domain Monitoring pages explain what each check covers.

On paid plans, WebPixie confirms the failure, opens one incident, sends one notification and closes the incident on its own when the endpoint recovers. For a timeout or connection error, the check is first retried in place, with up to 4 attempts in total, then verified from the monitor's other selected locations; a wrong status code or a keyword mismatch counts as down right away. The confirmed failure becomes an incident with its type, severity, start time and duration, and your team is notified by email and, depending on the plan, in Slack or through a webhook. While the incident is open, WebPixie re-checks the endpoint more often than its normal interval, so recovery is seen sooner and the outage length is measured accurately. When a check passes, the incident is marked resolved and a second notification goes out. Uptime incidents are always Critical, while SSL and domain expiry incidents start lower and move up in severity as the date gets closer. The incident record, with the notes your team adds, gives you the timeline for the postmortem. On the Free plan, you still get the email alert, but there is no incident list or history. You can see how checks work under uptime monitoring and the full lifecycle in the incidents docs.

WebPixie marks a site as down when an uptime check fails the response rules configured for that monitor. A failure can come from a timeout, connection error, unexpected HTTP status code, missing body keyword, or another expected condition that does not match. Uptime monitoring supports custom HTTP methods, headers, expected status codes, authentication, and keyword validation, so “down” can mean more than a simple 500 error. For network-related failures such as timeouts or connection errors, WebPixie makes up to 4 check attempts with exponential backoff before confirming the failure. On paid plans, if all attempts still fail, WebPixie also runs verification checks from the monitor’s other selected locations before opening an incident, which reduces false positives further. Failures from deterministic conditions, such as an unexpected status code or a missing keyword, open an incident on the first failed check without retry. If the issue is confirmed, WebPixie creates or updates an incident and sends notifications through the channels available on your plan. Check intervals and location availability are plan-based, and you can compare them on the pricing page.

Yes. Alerts go out by email on every plan, in Slack from Starter and through outgoing webhooks from Pro, and a webhook is how you forward incidents to the on-call tool you already use. WebPixie sends a notification when an uptime, SSL or domain incident opens, when its severity changes significantly and when it closes, with email templates in English and Turkish. The same incident that opens in WebPixie is the one your channel receives, and it closes on its own when checks pass again. WebPixie detects and records the incident; your on-call tool decides who gets paged and how. Notifications are switched on or off per resource, so low-priority uptime monitors can stay quiet while production endpoints alert. By default, email goes to every member of the workspace. The channels included in each plan are on the pricing page.

Yes, through webhooks: WebPixie posts incident and SSL/domain events to PagerDuty, and webhooks are available on higher plans. Webhooks send monitoring events to an HTTPS endpoint you configure, so PagerDuty can receive alert-routing events from WebPixie and route them through the policy your team already uses. This works best when paired with incident management, because confirmed failures become tracked incidents before they are routed externally. Webhook availability depends on plan, and you can compare notification channels on the pricing page. Programmatic workflows around the same resources are covered by the API integration.

Ready to track incidents in one place?

Detected, opened, and closed automatically, with five severity levels.