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. You get a reliable record of your sites' incidents over time, ready when you need to investigate something recent, prove a pattern, or put a credible report in front of your team or a client without piecing it together from memory.

Plan availability

Incidents is available on Pro and Business. See the plan comparison.

Full incident history with detailed timelines is part of the Incidents feature. On plans without it, you'll see how many incidents have been recorded, but the full details need an upgrade.

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 urgent) to P3 (least urgent)
• Status: where the incident is in its lifecycle: confirming, open, recovering, or 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. Click the banner to open the full incident detail page, where you can see the timeline and post updates for your team.

In your incidents list

Your incidents list shows all incidents, both open and resolved, across all your sites. Each row in the table shows the affected site (with its favicon and domain), what type of incident it is, the severity, current status, when it was opened, and how long it lasted.

At the top of the list, status filter tabs let you narrow down to a specific state: All, Open, Confirming, Recovering, or Resolved. There's also a search field to find incidents by domain name.

If you navigate to the incidents list from a specific site, a site filter banner appears showing which site you're viewing incidents for, with a "Show all" button to clear the filter and see incidents across all sites.

Click any row to open the full incident detail page with the complete timeline and team updates.

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 don't trigger notifications. They still appear in your incidents list; use the Confirming filter tab if you want to see only the ones still being verified.
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. Recovering. Checks are passing again, but DomainDash is running additional checks to confirm the recovery is genuine. If a check fails during this stage, the incident goes back to open.
4. Resolved. The problem has gone away and DomainDash has confirmed recovery through multiple consecutive healthy checks. 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. So your history holds only genuine, confirmed incidents, not transient blips, and any pattern you spot in it is one you can act on with confidence.

Incidents are automatic

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

Related

• Incident detail page to see the full timeline and post updates during an incident
• How incidents work for detection, severity levels, and recovery confirmation
• Notification channels for how and when you're notified about incidents