MTTA Targets and How to Hit Them
Mean time to acknowledge. Targets and the techniques.
Standard MTTA targets
Sev 1: under 5 minutes. Customer-impacting incidents need someone responding fast. Pager goes off; on-call acknowledges.
Sev 2: under 15 minutes. Significant but not critical. Time to acknowledge is forgiving but bounded.
Sev 3: under 1 hour. Issues worth knowing about, not worth waking someone for. Daytime business hours.
Measuring MTTA accurately
Time from page sent to acknowledged. Not from incident detected to acknowledged; that conflates detection time with response time.
Per-engineer view shows individual responsiveness. Per-shift view shows rotation health. Per-service view shows alert quality.
Outliers matter more than averages. A median MTTA of 3 minutes hides the case where 1% of pages took 30 minutes to acknowledge.
How to hit the targets
Reliable paging. Multiple channels (phone, app, SMS). Test quarterly with synthetic pages.
Backup on-call with explicit escalation. If primary doesn't acknowledge in 5 minutes, secondary gets paged.
Tooling that minimises friction. One-click acknowledge from the app, terminal, or chat.
Reading the trends
MTTA trending up means responsiveness is degrading. Causes: paging tool issues, on-call burnout, rotation understaffing.
MTTA trending down is good but watch for over-eager acks (acknowledging without action). Track time-to-action separately.
Per-time-of-day shows shift quality. Night shifts often have higher MTTA than day; that's expected. Pattern-of-life matters.
When MTTA is consistently bad
Investigate paging tool reliability first. Lost pages produce missed acknowledgements. The tool is the floor.
Then rotation health. Burnout, understaffing, on-call fatigue. Survey the rotation; act on findings.
Then process. Are pages going to the right person? Are they properly classified? The MTTA target may be reachable with better routing.