Incident management for uptime, SSL, and domain alerts

WebPixie sends alerts after a scheduled check confirms an issue. The exact time-to-alert depends on your monitor's check interval, which can range from 30 seconds to 24 hours depending on your plan.

To reduce false-positive noise, network-related failures such as timeouts or connection errors go through up to 4 check attempts with exponential backoff. On paid plans, if all attempts fail, WebPixie also runs verification checks from other locations 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.

Email alerts fire on every plan, including Free. What Free doesn't get is Incident Management: an incident list, lifecycle tracking, incident reporting, and the ability to add a note - those start on Starter, alongside 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 workflows, route the webhook through a receiving service that provides them.

WebPixie helps manage incidents by turning confirmed monitoring failures into tracked incident records. Incident management covers the full lifecycle from detection to notification, tracking, and closure for events such as uptime down, SSL check failure, SSL expiration, domain expiration, and domain suspension. Each incident includes the affected resource, start time, severity, occurrence count, status, duration, and closure timing. Severity levels range from INFO to CRITICAL, which helps teams prioritize response instead of treating every alert the same way. When the underlying check recovers, the incident closes automatically and is marked resolved, 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, and pair incidents with uptime monitoring for availability workflows.

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 other 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.

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 closure for uptime checks, SSL check failures, SSL expiration, domain expiration, and domain suspension. The API integration 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. For alert routing and incident lifecycle details, see incident management.

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 route them through the policy your team already uses. WebPixie posts the same incident and SSL/domain events used across its webhook integrations to your endpoint. This works best when paired with incident management, because confirmed failures become tracked incidents before they are routed externally. Webhook availability depends on plan, so compare notification channels on the pricing page. For programmatic workflows around the same resources, see the API integration.

If your website goes down at night or on the weekend, WebPixie can still detect the outage and send alerts. Uptime monitoring 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 makes up to 4 check attempts with exponential backoff before treating the issue as confirmed. On paid plans, if all attempts fail, WebPixie also runs verification checks from other locations before opening an incident. When the failure is confirmed, WebPixie can open or update an incident through incident management 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.