Skip to main content
MTTA stands for mean time to acknowledge: the average time between an alert being created and a responder acknowledging that they are handling it. It is calculated by dividing the total time-to-acknowledgment across a set of alerts or incidents by their count. MTTA measures how quickly a team reacts to problems, making it the standard health check for paging, on-call, and escalation systems.

​
How do you calculate MTTA?

The clock starts when the alert or incident is created and stops when a human acknowledges it — typically by tapping “acknowledge” in a paging app, claiming the incident in Slack, or otherwise signaling “I’ve got this.” Acknowledgment is not resolution; it just means someone is on it.

​
Worked example

An on-call team receives five pages in a week:
  • Alert 1: acknowledged after 2 minutes
  • Alert 2: acknowledged after 4 minutes
  • Alert 3: acknowledged after 1 minute
  • Alert 4: acknowledged after 15 minutes (escalated to a secondary responder)
  • Alert 5: acknowledged after 3 minutes
Total = 2 + 4 + 1 + 15 + 3 = 25 minutes. MTTA = 25 / 5 = 5 minutes. Notice how one missed page (alert 4) doubles the average. That sensitivity is a feature: MTTA surfaces escalation problems that a median would smooth over. Tracking both, plus the count of alerts that escalated past the primary on-call, gives the fullest picture.

​
Why does MTTA matter?

MTTA is a direct read on the health of your paging and escalation setup. Everything it measures happens before anyone has debugged anything, so a bad MTTA almost always points to a process or tooling problem rather than a hard technical one:
  • Notification rules. Are pages reaching people on channels they actually notice, with sensible retry behavior?
  • Escalation policies. When the primary doesn’t respond, how quickly does the page move to the next person? Long escalation timeouts inflate MTTA on every missed page.
  • Alert quality. Teams drowning in noisy, non-actionable alerts start ignoring pages. A creeping MTTA is often the first measurable symptom of alert fatigue.
  • Schedule coverage. Gaps or misconfigured handoffs in on-call schedules show up as outlier acknowledgment times at specific hours.
MTTA is also the first segment of MTTR: every minute an alert sits unacknowledged is a minute added to total resolution time before diagnosis even begins.

​
What is a good MTTA?

For urgent, page-worthy alerts, most teams aim for acknowledgment within a few minutes — fast enough that escalation to a backup responder rarely triggers. But the right target depends on alert urgency (a low-priority ticket queue doesn’t need a 5-minute acknowledgment), business hours versus overnight coverage, and whether your escalation timeouts are 5 minutes or 30. Set targets per urgency level, and judge yourself against your own trend rather than someone else’s benchmark.

​
How do you improve MTTA?

Start by cutting noise: acknowledgment speed improves almost automatically when every page is real and actionable. Then tune escalation timeouts so a missed page costs minutes, not half an hour. Finally, review outliers — the handful of slowest acknowledgments each month usually share a root cause, like a schedule gap or a responder whose phone silences notifications overnight. Rootly tracks MTTA per alert, per service, and per on-call shift out of the box — see on-call metrics for the available breakdowns. Browse the full incident management glossary.