1Password reported this major-impact incident on its official status page on Oct 16, 2026, 23:45 UTC. It was resolved after 3d 20h.
Right now 1Password is operational. Live 1Password status →
# Incident Postmortem - High error rates on 1Password.com when syncing data and provisioning users. **Date of Incident:** 16 October 2026 **Time of Incident \(UTC\):** 23:00 - 00:11 \(Oct 17\) **Service\(s\) Affected:** Admin Console, Item Syncing, Provisioning **Impact Duration:** 1hr10m ## Summary **What happened:** On Friday, October 16, 2026, from 4:00 to 5:10 p.m. Pacific \(23:00–00:10 UTC\), some requests to 1Password web services failed. Earlier that day, we deployed an infrastructure change meant to improve efficiency. The change caused one of our backend systems to hold on to resources longer than expected, and the system eventually ran out of capacity. **Impact:** About 2% of requests to 1Password web services in the US failed during the 70-minute window. The issue happened during a period of low traffic, which limited the number of people affected. **Resolution:** We increased the affected system’s capacity and applied configuration changes so resources are recycl
This incident has been resolved.
The deployed fix mitigated the issue causing increased error rates for users. We continue to monitor our services while we implement a permanent fix.
A fix has been deployed and we are monitoring the results.
We are seeing some improvements to affected services but are continuing to investigate the issue.
We are currently investigating this issue.
Overlapping incidents aren't necessarily related.
1Password reported 3 incidents in the last 90 days, 2 of them major or critical. A typical incident lasted 27 min. See 1Password's uptime and incident history