Failed Checks & Error Analysis

Understand health scores, error timelines, and backoff behavior

The failed checks view provides detailed error analysis tools to help you understand why your domain is failing checks, how often it happens, and what patterns exist.

Error Health Dashboard

At the top of the failed checks view, a health dashboard provides an at-a-glance summary:

Health Score

A numeric score from 0 to 100 reflecting your domain's error health over the last 7 days. A score of 100 means no errors detected.

Weekly Trend

Positive trend (arrow up) — Fewer errors this week than last week
Negative trend (arrow down) — More errors this week
No change — Error rate is stable

A visual timeline showing error counts per day over the past 7 days. Each day shows the error count and total checks run. This helps you spot patterns — for example, errors that only occur at certain times or on specific days.

Error Categories

A grid showing error type breakdowns with counts, categorized by type. This tells you whether failures are due to timeouts, SSL errors, connection refused, server errors, etc.

When your domain is currently experiencing issues, an active incident banner appears showing:

Started at — When the incident began
Duration — How long it has been ongoing
Checks failed — Total number of failed checks in this incident
Latest error — Most recent error details including response code, error message, region, and timestamp
Affected regions — Which monitoring regions are seeing failures

You can acknowledge an active incident to indicate you're aware of the issue.

Filtering Failed Checks

Response Code Filter

Filter by specific HTTP status codes observed in failures. Only codes that actually appear in your failed checks are shown. Common codes include:

0 — Connection Failed (no HTTP response received)
408 — Request Timeout
500 — Internal Server Error
502 — Bad Gateway
503 — Service Unavailable
504 — Gateway Timeout

Region Filter

Filter by the monitoring region where the failure occurred. Each region is shown with its flag for quick identification. This helps determine whether failures are global or regional.

Incident Grouping

Failed checks are automatically grouped into incidents based on these rules:

Pings with the same error code (or same error message if the code is null) are grouped together
Pings must occur within 5 minutes of each other to be part of the same incident
An incident is marked as ongoing if the most recent failure was within the last 10 minutes
Incidents are displayed in reverse chronological order (newest first)

This grouping prevents a single outage from appearing as dozens of individual failures — instead, you see it as one incident with details.

Individual Failed Check Details

Each failed ping includes:

Response Code — HTTP status code received (or null if no response)
Response Time — How long before the check failed (in ms)
Checked At — Timestamp of the check
Region — Which monitoring region ran the check
Error Message — Description of what went wrong
Redirect Details — Whether a redirect was involved, redirect count, initial response code, and final URL

Backoff Behavior

When a domain consistently fails checks, Domain Pilot implements a backoff strategy to avoid excessive checking:

Consecutive failures are tracked — each successive failure increments the counter
Backoff levels increase with more consecutive failures
Check intervals become longer at higher backoff levels
Current check interval (in minutes) is shown on the domain

Extended Downtime Pause

If a domain has been down for an extended period, monitoring may be paused to conserve resources. The domain shows a monitoring_paused status with a reason and timestamp. Monitoring automatically resumes when you manually trigger a check or update the domain's monitoring settings.

Running a Manual Check

Click the Run Check button to trigger an immediate uptime check. This sends a check request, updates results in real time via WebSocket, and refreshes the failed checks data. Use this to verify a fix or get a fresh status after making changes.

Healthy State

When your domain has a health score of 100 and no recent failures, the failed checks view shows a success state with a checkmark and "No Errors Detected" message.