Incidents

All technical issues and outages that occur in WebPixie are centrally managed through the Incidents page.

All errors detected during uptime, SSL, and domain checks are collected in this area and presented to the user through a single panel.

This allows all issues in the system to be:

tracked from one place
filtered
analyzed
documented by adding notes

Some features and limits mentioned on this page vary by plan. Visit our Pricing page to review the plans.

On the Free plan, you still receive email alerts for these events, but you don't get the incident list, lifecycle tracking, reporting, or the ability to add notes described below.

Incident Creation

When WebPixie detects a problem during checks, it automatically creates an incident.

Example situations:

website is inaccessible
HTTP status code returns an error (e.g., 500)
the SSL certificate fails validation (untrusted, expired, self-signed, or hostname mismatch)
SSL certificate is about to expire
domain expiration is approaching
domain enters a suspended state (e.g., registrar hold or post-expiry deletion)

When a problem occurs, the incident:

👉 starts as Ongoing

When the underlying check passes again, the incident:

👉 automatically transitions to Resolved

WebPixie only detects and reflects this recovery — it doesn't fix the underlying website, SSL, or domain issue itself. The status transition happens automatically, without requiring you to manually close the incident.

Incidents Page

The Incidents page is the main screen where all incidents are listed.

From this screen, you can:

list all incidents
filter them
review their details
add notes or descriptions

Filtering

The Incidents page offers various filters to make analyzing incidents easier:

Status filter: All / Resolved / Ongoing
Category filter: Domain / SSL / Uptime
Type filter: Status Code, Timeout, SSL Expiration, Request, etc.
Severity filter: Critical, High, Medium, Low, Info
Site filter: Used to view incidents for a specific site

These filters help users quickly perform meaningful analysis within large datasets.

Incident List

Each incident is displayed as a row in the list and includes the following information:

Status: Indicates whether the incident is active (ongoing) or resolved
Site: The website associated with the incident
Details: Shows the type and reason for the incident (e.g., Status Code 500, Timeout, SSL Expiration)
Incident Start: The start time and duration of the incident
Retry Count: Shows how many times the problem has recurred
Description: A note field that can be added by the user

Incident Types

Incidents can be generated from different types of checks.

Example incident types:

Status Code
Timeout
SSL Check
SSL Expiration
Domain Expiration
Domain Suspended
Connection
Keyword Match
Too many redirects
Unexpected

This structure allows WebPixie to consolidate various problem types within a single system.

Incident Severity Levels

Each incident is classified by its level of importance:

Critical → Critical issue, requires immediate action
High → High-priority problem
Medium → Moderate impact
Low → Low priority
Info → Informational only

This classification makes it easier for teams to prioritize their response.

Uptime, SSL Check, and Domain Suspended incidents always open at a fixed severity (Critical, High, and Critical respectively). Only SSL Expiration and Domain Expiration incidents escalate through severity tiers as the expiry date approaches.

Incident Descriptions

A description can be added and updated for each incident.

This field allows you to:

document the cause of the problem
note the actions taken
facilitate team communication

It plays an important role, especially when analyzing past incidents.