Website Monitoring for DevOps Teams

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.

Yes, WebPixie can monitor multiple websites, APIs, services, and HTTP endpoints across your infrastructure. Uptime monitoring supports HTTP and HTTPS checks with custom methods, headers, expected status codes, authentication, and body keyword validation, so each endpoint can have rules that match its purpose. You can monitor production sites, status endpoints, landing pages, API health routes, staging URLs, and other reachable services in the same workspace. Capacity is plan-based: site limits are Free (3 sites), Starter (10 sites), Pro (50 sites), Enterprise (unlimited), and uptime check limits are Free (5), Starter (20), Pro (50), Enterprise (unlimited). Use workspace management to organize services by team, environment, client, or product area, and configure notifications per resource. You can compare all limits on the pricing page.

Monitoring intervals are plan-based, with current minimums set as: Free (15 minutes), Starter (5 minutes), Pro (1 minute), Enterprise (30 seconds). You can also configure longer intervals up to 24 hours for lower-priority monitors, so a critical API health endpoint can run more often than a low-risk marketing page. In uptime monitoring, the interval affects how quickly WebPixie can detect a failure before retry logic confirms the issue and opens an incident. Faster intervals are useful for customer-facing applications, checkout flows, authentication services, and status endpoints where even short downtime matters. Slower intervals may be enough for informational pages or non-critical internal tools. Check intervals, uptime check limits, and monitoring locations vary by tier, so compare the details on the pricing page. Confirmed failures can then flow into incident management and your configured notification channels.

WebPixie confirms a failure before it alerts you. When an uptime 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 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.

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 or other service can alert the right channel without flooding everyone. Confirmed failures originate in incident management, 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.