Sign In

MTTR Report

The Mean Time to Resolution (MTTR) report shows how quickly your team resolves incidents. Use this data to identify bottlenecks and improve response times.

What is MTTR?

Mean Time to Resolution measures the average time from when an incident is created until it’s marked as resolved. Lower MTTR means faster incident resolution and less downtime.

Report Sections

Overall Statistics

The report displays three key metrics:

  • Average MTTR - Mean resolution time across all incidents
  • Median MTTR - The middle value, less affected by outliers
  • 95th Percentile - Resolution time for 95% of incidents

MTTR by Severity

See resolution times broken down by incident severity:

  • SEV-1 (Critical)
  • SEV-2 (High)
  • SEV-3 (Medium)
  • SEV-4 (Low)

This helps identify if critical incidents are being prioritized appropriately.

A line chart shows how MTTR changes over the last 30 days. Use this to:

  • Spot trends in resolution times
  • Identify specific days with issues
  • Track improvements over time

Incident Volume

A stacked bar chart displays incident counts by severity level over time. This helps correlate resolution times with incident volume.

Detailed Data Table

The table shows:

  • Date
  • Incident count
  • Average MTTR
  • Median MTTR
  • 95th percentile

Sort by any column to find patterns.

Using the Report

Exporting Data

Click Export to download a CSV file containing:

  • Overall statistics
  • Daily MTTR values
  • Severity breakdowns
  • All data from the detailed table

Interpreting Results

Good indicators:

  • Consistent or decreasing MTTR trend
  • Lower resolution times for higher severity incidents
  • Small gap between average and median (fewer outliers)

Areas for improvement:

  • Increasing MTTR trend
  • High severity incidents taking longer than low severity
  • Large gap between median and 95th percentile

Best Practices

Regular Monitoring

  • Review MTTR weekly to catch trends early
  • Compare current performance to previous periods
  • Set team goals for improvement

Deep Analysis

  • Export data to identify patterns
  • Correlate with other metrics like incident volume
  • Review outliers to understand delays

Taking Action

  • Use insights to improve processes
  • Update runbooks for common incidents
  • Provide training where needed
  • Celebrate improvements with the team