--- title: "Incident Management & Alert Tracking | WebPixie" description: "Automatically detect uptime, SSL, and domain incidents with 5 severity levels and occurrence history. Centralize alert tracking to improve reliability." canonical: "https://webpixie.io/features/incident-management" source_path: "/features/incident-management" lang: "en" generated_by: "scripts/generate-md.mjs" --- [Back to Features](/features.md) Incident management # Incident management for uptime, SSL, and domain alerts WebPixie opens an incident automatically when a check confirms a problem, tracks it through resolution, and counts recurrences, across five severity levels. [Get started](https://app.webpixie.io/app?lang=en&utm_source=website&utm_medium=website_link&utm_campaign=features_incident_management&utm_content=hero_cta) Auto-detected and resolved 5 severity levels Starter and above Incident management is available on Starter and above. [Compare all plans](/pricing.md) ### 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. ## 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, and a domain approaching expiry. Each incident records what triggered it, the affected resource, and a severity. Incidents move through a full lifecycle: detection, notification, tracking, and resolution. When the underlying issue clears, for example a site comes back up, WebPixie resolves the incident automatically, so the board reflects the current state without manual cleanup. Severity runs across five levels, from INFO to LOW, MEDIUM, HIGH, and CRITICAL. Recurring problems are tracked with an occurrence count, so a flapping endpoint shows as one incident with many occurrences instead of a flood of duplicates. 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, or a domain nearing expiry. Each incident captures the trigger, the affected resource, and a severity, so the response starts from a clear record. 02 ### Auto-resolution keeps the board accurate Incidents close when the issue clears A site that comes back up should not leave a stale alert behind. When the underlying check passes again, WebPixie resolves the incident automatically 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. A flapping endpoint becomes one incident with a rising occurrence count, not a stream of duplicate alerts. 04 ### Route notifications to the right channel Email, Slack, and webhook by plan Incident creation and resolution can notify your team through email on every plan, Slack on Starter and above, and webhooks on Pro and above. You control notifications per resource, so a critical production incident and a low-priority staging one do not have to reach the same place. ### Centralize your incident tracking Available on Starter and above. Compare plans to find the right fit. [Get started](https://app.webpixie.io/app?lang=en&utm_source=website&utm_medium=website_link&utm_campaign=features_incident_management&utm_content=mid_cta) ## Everything you need to monitor a website. In one workspace. A quick look at other WebPixie features. Incidents Track failures from detection to resolution in one place. Currently viewing [Uptime](/features/uptime-monitoring.md) Catch downtime first with multi-region and keyword checks. Learn more [Domain](/features/domain-monitoring.md) Never be caught off guard by a domain renewal or transfer. Learn more [DNS](/features/dns-monitoring.md) Spot unexpected DNS and DNSSEC changes with daily checks. Learn more [SSL](/features/ssl-monitoring.md) Get warned 15 days before certificates expire, with daily SSL checks. Learn more [Certificates](/features/certificates-manager.md) See every certificate and its expiry in one place. Learn more [Link Crawler](/features/link-crawler.md) Find broken links before your visitors do. Learn more [Main Page Analyzer](/features/main-page-analyzer.md) Find what slows down or breaks your homepage. Learn more [Indexability](/features/indexability-checker.md) Check whether search and AI engines can access your content. Learn more [API](/features/api-integration.md) Automate monitoring with the GraphQL and REST API. Learn more [Workspaces](/features/workspace-management.md) Organize monitoring and bring your team into one workspace. Learn more ## Why teams choose WebPixie for incident management ### Less alert noise Retry logic confirms failures before an incident opens, and recurrences are grouped into one incident, so you get signal instead of a flood. ### Your whole site in one workspace Incidents sit next to uptime, SSL, DNS, domain, and link health, with one dashboard across all of them. ### Automatic from detection to resolution Incidents open on confirmed failures and close when the issue clears, with a timestamped history you can review. ### Frequently Asked Questions Common questions about incident management. ### How quickly will I be notified of issues? WebPixie sends alerts within seconds of detecting an issue. The exact time-to-alert depends on your check interval. On the Pro plan with 60-second checks, you know about an outage within 60 to 90 seconds of it starting. On Enterprise with 30-second checks, within 30 to 60 seconds. On the free plan with 15-minute checks, the worst-case detection window is 15 minutes. To prevent false-positive noise, WebPixie retries failures caused by network problems such as timeouts or connection errors up to 4 times with exponential backoff before opening an incident. This helps confirm a real outage versus a flaky network, so you don't get woken at 3am for a routing flicker in one region. [Alerts](/features/incident-management.md) route through email (every plan), Slack (Starter and above), and webhooks (Pro and above). Webhooks integrate with PagerDuty, Opsgenie, or any incident management tool you already use. For SMS or voice escalation, route the webhook through a service like PagerDuty. ### How does WebPixie help with incident management? WebPixie helps manage incidents by turning confirmed monitoring failures into tracked incident records. [Incident management](/features/incident-management.md) covers the full lifecycle from detection to notification, tracking, and resolution for events such as uptime down, SSL check failure, SSL expiration, and domain expiration. Each incident includes the affected resource, start time, severity, occurrence count, status, duration, and resolution timing. Severity levels range from INFO to CRITICAL, which helps teams prioritize response instead of treating every alert the same way. Incidents can auto-resolve when the underlying issue clears, so history stays accurate without manual cleanup. Notifications can be sent through email, Slack, or webhooks depending on your plan, and per-resource notification controls help route alerts to the right people. You can compare incident and notification availability on the [pricing page](/pricing.md), and pair incidents with [uptime monitoring](/features/uptime-monitoring.md) for availability workflows. ### How do you determine if a site is down? 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](/features/uptime-monitoring.md) 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 retries the failed check up to 4 times with exponential backoff before opening an incident, which reduces false positives. Failures from deterministic conditions, such as an unexpected status code or a missing keyword, are confirmed without extra retries. If the issue is confirmed, WebPixie creates or updates an [incident](/features/incident-management.md) and sends notifications through the channels available on your plan. Check intervals and location limits are plan-based, and you can compare them on the [pricing page](/pricing.md). ### What webhook integrations are supported? WebPixie supports custom webhooks that send monitoring events to any HTTPS endpoint you configure. Webhooks are useful for tools such as PagerDuty, Opsgenie, incident management platforms, CI/CD automation, internal dashboards, and custom notification systems. Supported event flows include incident creation and resolution for uptime checks, SSL check failures, SSL expiration, and domain expiration. The [API integration](/features/api-integration.md) works alongside webhooks, so teams can receive event-driven callbacks and then query or update resources programmatically. Slack is available as a native notification channel on eligible plans, while webhooks let you connect to systems beyond built-in integrations. Webhook availability depends on plan, so compare notification channels on the [pricing page](/pricing.md). For alert routing and incident lifecycle details, see [incident management](/features/incident-management.md). ### Does WebPixie integrate with PagerDuty? Yes, WebPixie can integrate with PagerDuty through custom webhooks on Pro and higher plans. Webhooks send monitoring events to an HTTPS endpoint you configure, so PagerDuty can receive alert-routing events from WebPixie and trigger the escalation policy your team already uses. Supported webhook event flows include incident creation and resolution for uptime checks, SSL check failures, SSL expiration, and domain expiration. This works best when paired with [incident management](/features/incident-management.md), because confirmed failures become tracked incidents before they are routed externally. Webhook availability depends on plan, so compare notification channels on the [pricing page](/pricing.md). For programmatic workflows around the same resources, see the [API integration](/features/api-integration.md). ### What happens if my website goes down at night or on the weekend? If your website goes down at night or on the weekend, WebPixie can still detect the outage and send alerts. [Uptime monitoring](/features/uptime-monitoring.md) runs on the interval available for your plan and checks your configured response rules, such as status code, timeout, authentication, headers, or body keyword expectations. To reduce false positives from network-related problems such as timeouts or connection errors, WebPixie retries the failed check up to 4 times with exponential backoff before treating the issue as confirmed. When the failure is confirmed, WebPixie can open or update an incident through [incident management](/features/incident-management.md) and notify the channels available on your plan, such as email, Slack, or webhook. This helps the right person respond even outside office hours. Check intervals, locations, and notification options vary by plan, so compare coverage on the [pricing page](/pricing.md). ### Does WebPixie send SMS alerts? WebPixie does not send SMS alerts directly, but you can route alerts through webhooks to SMS-capable incident tools. For example, teams can send WebPixie webhook events to PagerDuty, Opsgenie, or a similar alerting platform, then let that tool handle SMS, phone, or mobile push escalation. WebPixie’s own notification channels include email on all plans, Slack on Starter and higher plans, and webhooks on Pro and higher plans. Confirmed monitoring failures can create incidents through [incident management](/features/incident-management.md), then webhook delivery can pass those events to your escalation stack. Compare channel availability on the [pricing page](/pricing.md). For webhook-driven automation details, see [API integration](/features/api-integration.md). ### Is there a mobile app? WebPixie does not currently provide a dedicated mobile app for iOS or Android. For mobile incident awareness, teams usually use email alerts, Slack notifications, or webhook-triggered notifications through tools such as PagerDuty, Opsgenie, or internal mobile workflows. Slack notifications are available on Starter and higher plans, while webhooks are available on Pro and higher plans. This means your team can still receive mobile push notifications through the tools already used for on-call response. Alerts can be driven by confirmed incidents from [incident management](/features/incident-management.md), and webhook or API-based workflows can be planned around the [API integration](/features/api-integration.md). For plan availability, review the [pricing page](/pricing.md). ### How does team collaboration work? Team collaboration in WebPixie is managed through workspaces, invitations, roles, and per-resource notifications. [Workspace management](/features/workspace-management.md) supports Owner, Admin, and User roles: Owners have full control including billing, Admins can manage sites, monitors, and incidents, and Users have read-only access to monitoring data and reports. You can invite teammates by email, assign the right role for each workspace, and keep clients or internal teams separated by project. Configuration changes are tracked in an audit trail, including monitor creation, notification updates, invitations, and role changes. Teams can collaborate on [incident management](/features/incident-management.md) by sharing incident history, status, severity, affected resources, and resolution timing. User limits depend on your plan, so compare team capacity on the [pricing page](/pricing.md). ### How do outage alerts help reduce SEO risk? WebPixie alerts you when a monitored page becomes unreachable or fails the conditions you configured. No monitoring tool can guarantee that a search engine has not attempted to crawl during an outage, but fast detection helps reduce the duration and SEO risk of availability problems. [Uptime monitoring](/features/uptime-monitoring.md) checks for timeouts, connection failures, unexpected status codes, redirects, and missing expected content, then uses retry logic to reduce false positives before opening an incident. Alerts are sent by email on every plan, with Slack and webhooks available on eligible plans, so the right team can act quickly. Confirmed outages can be tracked through [incident management](/features/incident-management.md), including severity, affected resource, and resolution timing. For search-specific risk, combine outage alerts with the [Indexability Checker](/features/indexability-checker.md) to catch crawl-blocking configuration problems. ### How does WebPixie avoid false-positive alerts? WebPixie confirms a failure before it alerts you. When an [uptime](/features/uptime-monitoring.md) check hits a network-related failure such as a timeout or a connection error, WebPixie retries it up to four times with exponential backoff, so a brief blip does not open an incident. Failures that are not network-related, like an unexpected status code, open an incident without retrying, because they reflect a real response from the server. You also control what counts as up: an accepted status-code list, keyword checks for content that must or must not appear, and a configurable request timeout all shape the verdict. When a failure is confirmed, it flows into [incident management](/features/incident-management.md) with a severity and a type, and resolves automatically when checks recover. This keeps alert noise down without hiding genuine outages, and per-plan check intervals are on the [pricing page](/pricing.md). ### Where can WebPixie send alerts (Slack, webhooks, PagerDuty)? WebPixie delivers notifications by email on every plan, with Slack and webhooks available on higher tiers. Email goes out on incident creation and resolution and on SSL and domain expiration events, with templates in English and Turkish. Slack notifications are available from Starter, and outgoing webhooks from Pro, which is how you connect tools like PagerDuty or Opsgenie: WebPixie posts the event to a webhook URL and your receiving tool routes it onward. Notifications are controlled per resource, so each [uptime monitor](/features/uptime-monitoring.md) or other service can alert the right channel without flooding everyone. Confirmed failures originate in [incident management](/features/incident-management.md), so the same incident that opens in WebPixie is the one that reaches your channel, and it clears when the issue resolves. WebPixie does not send SMS or voice alerts and does not run on-call escalation chains. Channel availability by plan is on the [pricing page](/pricing.md). Show more FAQs [See all FAQs](/resources/faq.md) ### Ready to track incidents in one place? Auto-detected, auto-resolved, with five severity levels. [Get started](https://app.webpixie.io/app?lang=en&utm_source=website&utm_medium=website_link&utm_campaign=features_incident_management&utm_content=bottom_cta) [See all features](/features.md) ## Source Attribution This file is automatically generated by WebPixie AI and summarizes publicly available content from WebPixie pages. Authoritative details should always be verified from the original URLs.