INC-2025-108: Authentication Service Sev3 Incident
Date: 2026-03-22 Service: Authentication Service Severity: Sev3 Incident Commander: Morgan Lee Jira References: ACME-1015, ACME-1016 GitHub References: GH-1015, GH-1016 API References: API-AUTHENTICATION-01
Summary
The Authentication Service experienced customer-visible degradation caused by partial deploy where only half of the pods received new configuration. The incident affected dependent paths that include Authentication Service, Checkout Service, Billing Service, Inventory Service, and Notification Service, with the strongest impact localized to Authentication Service.
Timeline
- Detection: synthetic checks and service SLO burn alerts fired.
- Triage: on-call engineers reviewed traces, dependency dashboards, and recent deployments.
- Mitigation: traffic was shifted, retries were reduced, and the affected worker pool was drained.
- Recovery: error rate returned to baseline after remediation was deployed and queues caught up.
Root Cause
The proximate cause was partial deploy where only half of the pods received new configuration. The deeper contributing factor was incomplete validation of the Authentication Service operational contract against API API-AUTHENTICATION-01 and insufficient pre-release checks for high-cardinality traffic.
Customer Impact
Customers saw intermittent failures, elevated latency, or delayed asynchronous updates depending on where their request crossed the Authentication Service boundary. No permanent data loss was identified.
Remediation
- Track remediation in Jira tickets ACME-1015, ACME-1016.
- Implement code and test changes in GitHub items GH-1015, GH-1016.
- Update the relevant runbook for Authentication Service and replay this scenario in staging.