What Periscope tracks
Periscope calculates MTTR by finding failure-to-success deployment pairs for the same service. The dashboard shows:- Percentiles — p50, p75, and p95 recovery times (in minutes)
- Average recovery time
- Individual incidents showing the failed deployment, the recovery deployment, and the time between them
DORA benchmarks
| Level | Benchmark |
|---|---|
| Elite | Less than 1 hour |
| High | Less than 1 day |
| Medium | 1 day to 1 week |
| Low | More than 1 week |
How it works
Periscope identifies recovery events by pairing failed deployments with the next successful deployment for the same service. The recovery time is measured between these two events. Percentiles are computed across all incidents in the selected time range.Interpreting the data
- Low MTTR means your team can quickly detect and fix production issues. This often comes from good monitoring, automated rollback, and small deployment batches.
- High MTTR suggests problems with incident detection, slow CI/CD pipelines for hotfixes, or complex rollback procedures.
- Large gap between p50 and p95 means most incidents are resolved quickly but some take much longer — investigate those outliers.
- Decreasing MTTR is a sign of improving operational maturity, even if change failure rate stays constant.
Reducing MTTR
- Implement automated rollback on health check failures
- Ensure your CI/CD pipeline supports fast hotfix deployments
- Use feature flags to disable problematic features without redeploying
- Invest in monitoring and alerting to reduce detection time
- Keep deployments small so the blast radius is limited and the fix is easier to identify
MCP tool
Query MTTR from your AI coding assistant:Change failure rate
CFR measures how often failures happen. MTTR measures how fast you recover.