Incident management for uptime, SSL, and domain alerts

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

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

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