1Password Status Page

May 16, 2026 · resolved May 16

This incident has been resolved.

May 4, 2026 · resolved May 4

This incident has been resolved.

Apr 27, 2026 · resolved Apr 28

# Incident Postmortem - Login and Sync Issues **Date of Incident:** 2026-04-27 **Time of Incident \(UTC\):** 14:15 - 15:41 **Service\(s\) Affected:** All web APIs **Impact Duration:** Approximately 86 minutes ## Summary On April 27, 2026, [1Password.com](http://1password.com/) experienced a period of elevated error and full service unavailability in our USA/Global region. A defect deployed in application scaling logic caused a cascading failure during peak usage. This resulted in a period of service unavailability for customers in the USA/Global region. This was not a security incident, and there was no loss of data. ## Impact on Customers * **Sign-in and account access:** Customers in the USA/Global region experienced errors or were unable to sign in or access their 1Password accounts between approximately 14:15 and 15:41 UTC on April 27, 2026. * **All 1Password clients:** The disruption applied to all client types, including the web app, CLI, browser extensions, and desktop and mobile applications, for customers connecting through the USA/Global region. * **Geographic regions affected:** Only customers on the USA/Global region were affected. Other regions were not impacted. ## What Happened? We deployed a change to how our services signal their readiness to serve requests, which contained a latent defect. * **Timeline of events:** * **2026-04-27 14:15 UTC** - Load increase triggers issues. * **2026-04-27 14:29 UTC** - Incident declared; response team mobilized. * **2026-04-27 15:41 UTC** - Issue identified and fix deployed. * **2026-04-28 18:06 UTC** - Incident formally resolved following monitoring. ## How Was It Resolved? Our on-call engineering team identified the scaling logic as the cause of the cascading failure and disabled it via a configuration change. Once disabled, capacity was restored, and traffic recovered. A subsequent configuration change was made to prevent this logic from being re-enabled in production environments. ## What We Are Doing to Prevent Future Incidents * **Immediate fix:** We disabled the defective health check logic and locked the configuration to prevent it from being re-enabled in production. * **Retrospective:** We are conducting a full retrospective with the incident responders to identify further improvements to our systems and our response processes. ## Next Steps and Communication * No action is required from our customers at this time. We are committed to providing a reliable and stable service, and we are taking the necessary steps to learn from this event and prevent it from happening again. Thank you for your patience and understanding. Sincerely, The 1Password Team

Apr 22, 2026 · resolved Apr 22

This incident has been resolved.

Apr 13, 2026 · resolved Apr 22

This incident has been resolved.