Reference eligibility: eligible — Institutional or method-author operating guidance documents this procedure; no tool-seller customer-success claim is admitted.
engineering/IT / OP-ENG-01
PagerDuty NTP incident recovery
A clock-drift incident escalated after runbook recovery did not resolve it.
practitioner-reported · · Source account, not a validated implementation
What goes in
- Clock-drift alerts
- Runbooks
- Service ownership
What comes out
- Restored services
- Postmortem assignment
Documented sequence
Order described in the source account; not a sequence between pattern families.
- Validate automated recovery and runbooks
- Declare major incident
- Assemble dependent-service owners
- Try recovery options methodically
- Rotate responders
- Change NTP configuration
- Verify recovery with every service owner
- Assign postmortem before closing
Checks described
- Service-owner recovery confirmation
What changes with context
- Incident dated 2017-10-06; multi-team response
- Novel recovery needed beyond runbooks
Shared patterns · provisional interpretation
-
Diagnose and resolve an exception
Unexpected failure, anomaly, or complaint → investigated explanation and a bounded remedy or recovery path
-
Coordinate commitments to closure
An objective involving people or teams → accountable next actions, handoffs, tracking, and agreed closure
Fit: mapped. Exploratory analyst coding of collected source summaries; not independently tested
Could this transfer?
Hypothetical: Coordinate recovery from a failed payroll batch across upstream owners and downstream consumers.
Limit: Technical restoration is not equivalent to reversing financial transactions.
Evidence limits and unknowns
- Exact configuration change
- Controlled comparison of response effectiveness
Source eligibility and effectiveness
Allowed use: process reference with explicit limits . Source eligibility is not proof of effectiveness, safety or transferability.
Review attribution: AI-assisted source review · 2026-10-18T03:26:44.526806+00:00.
- Eligibility, where granted, permits a process reference only; it is not proof of usefulness, causal effectiveness, safety, or transferability.
- No workflow software executed, no video playback independently observed, and no outcomes independently measured by this audit.
- Exact configuration change
- Controlled comparison of response effectiveness
- Technical restoration is not equivalent to reversing financial transactions.
Source and dates
SRE Workbook — Incident Response, PagerDuty case ↗ · Original practitioner incident account
- Published
- Unknown
- Updated
- Unknown
- Checked (UTC)
- 2026-10-18T03:00:44Z
reported_incident_date: 2017-10-06
Case text dates the PagerDuty incident October 6, 2017. Footer gives book copyright 2018, which is not treated as webpage publication. Chapter publication and update dates not established.
verified other date only · Date evidence ↗
Try a bounded adaptation
This generated starter is untested. It is not the source author’s prompt or a reviewed Commons skill.