Incident history

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

Overview

DomainDash logs every incident with a full timeline, from the moment the problem was first detected through to when it was resolved. Use it to investigate something recent, prove a pattern, or put together a report for your team or a client. The one exception: DomainDash removes a resolved incident that lasted under 10 minutes and has no notes from your team.

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, which is later than the first failed check. Confirmation filters out false positives, so the "opened at" time marks when DomainDash confirmed the problem.

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. 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, unless they lasted under 10 minutes and have no notes from your team. That helps with:

• 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. DomainDash has detected a problem and is running more checks to confirm it. Confirming incidents don't send notifications. They appear in your incidents list, and the Confirming filter tab shows only those.
2. Open. Enough checks in a row have confirmed the problem. Urgent incidents alert you at this point, and the incident appears prominently in your dashboard.
3. Recovering. Checks are passing again, and DomainDash is running more checks to confirm the recovery. If a check fails during this stage, the incident goes back to open.
4. Resolved. The incident has had as many passing checks in a row as it took to confirm it. DomainDash closes it with a resolved timestamp.

If the next check passes while an incident is still confirming, DomainDash removes it, so your history holds only confirmed incidents. See How incidents work for how many checks each kind of problem needs.

Incidents are automatic

You can't manually create, edit, or close incidents. Check data drives them, so an open incident 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