Incident Management Practical By Samson Tanimawo, PhD Published Jan 3, 2026 4 min read

MTTA: Time From Page to Acknowledged

MTTA is response readiness. Shrinking it shrinks MTTR.

Definition

MTTA: time from page-sent to on-call acknowledgement. Not from incident-start; that's MTTD plus MTTA. The two metrics are distinct.

Acknowledge means 'I am responding'. It does not mean fixed; it means engaged. The pager stops re-paging; the team knows someone is on it.

Typically measured per page, aggregated per shift, per engineer, per service. Different views surface different problems.

Sev 1: under 5 minutes. Sev 2: under 15. Sev 3: under 1 hour during business hours.

Aim for 95th percentile within target. Median is too forgiving; outliers are where incidents go wrong.

Per-service tier: customer-critical services tighter; internal services looser.

Multi-channel paging. Phone, app, SMS, voice escalation. Phone DND, dead battery, no signal: all real failures.

Backup on-call. If primary doesn't acknowledge in 5 minutes, secondary gets paged. Tested monthly.

Test the path quarterly. Synthetic pages verify the chain end-to-end. Surprises during real incidents are expensive.

Trend up: paging tool degrading, rotation understaffed, on-call fatigue. Investigate.

Trend down: usually good. Watch for acknowledgement-without-action. Track MTTR separately.

Outliers are signal. The 99th percentile MTTA tells you how the worst case responds. Often more useful than the median.

First: tool reliability. Lost pages mean lost MTTA. Paging tool dashboards show delivery rates.

Second: rotation health. Burnout, vacation gaps, off-hours coverage. Survey; staff up.

Third: process. Is the right person getting paged? Is the alert properly classified? Routing fixes are usually high-leverage.