Incident history

Review what went wrong, when, and for how long.

Overview

Every incident DomainDash creates is logged with a full timeline, from the moment the problem was first detected through to when it was resolved. This gives you a reliable record of your site's issues over time, whether you need to investigate a recent outage, spot recurring patterns, or put together a report for your team or stakeholders.

What information is captured

Each incident in your history includes:

• Incident type: what went wrong (for example, "site is down", "security certificate has expired", or "domain routing is failing")
• Severity: how urgent the problem was, from P0 (most critical) to P3 (least urgent)
• Status: whether the incident is still open or has been resolved
• Opened at: the exact time DomainDash confirmed the problem and raised the incident
• Resolved at: when the problem went away and the incident was automatically closed (if it has been resolved)
• Duration: how long the incident lasted, calculated from when it was opened to when it was resolved. If it's still ongoing, this shows how long it's been open so far.
• Affected site: which site the incident belongs to

How duration is calculated

DomainDash calculates duration from the moment an incident is confirmed and opened, not from the very first failed check. This is because the confirmation process filters out false positives, so the "opened at" timestamp represents when the problem was definitively real.

For incidents that lasted less than a minute, you'll see "less than a minute". Longer incidents show the duration in minutes, hours, or days depending on how long they lasted.

Viewing your incidents

Incidents are visible in two places:

On the site detail page

Each site's detail page shows any active incidents as an alert banner at the top of the page. This gives you immediate visibility of ongoing problems when you open a site.

In your incident history

Your incident history shows all incidents, both open and resolved, across all your sites. Filter by status to focus on what's currently happening or review past issues.

Resolved incidents stay in your history so you can always go back and check what happened. This is useful for:

• Spotting patterns. If the same site keeps going down at the same time each week, you might have a scheduled process that's causing problems.
• Measuring reliability. Track how often incidents occur and how long they take to resolve.
• Reporting. Share incident timelines with your team, clients, or hosting provider to help them investigate.

Incident lifecycle

Every incident follows the same lifecycle:

1. Confirming. A problem has been detected but not yet confirmed. DomainDash is running additional checks to make sure it's real. Confirming incidents are deliberately kept quiet until confirmed, so you won't see them prominently in your history.
2. Open. The problem has been confirmed by multiple checks. This is when you get notified and the incident appears prominently in your dashboard.
3. Resolved. The problem has gone away and DomainDash has confirmed recovery. The incident is closed with a resolved timestamp.

Incidents that never make it past the confirming stage (because the problem resolved itself before enough checks confirmed it) are discarded. This means your history only contains genuine, confirmed incidents, not transient blips.

Incidents are automatic

You can't manually create, edit, or close incidents. They're driven entirely by monitoring data, which keeps your incident history accurate and tamper-proof. If an incident is open, it means DomainDash is still detecting the problem.

Related

• How incidents work for detection, severity levels, and auto-resolution explained
• Notification channels for how and when you're notified about incidents