1Password reported this critical-impact incident on its official status page on Apr 14, 2026, 17:25 UTC. It was resolved after 8h 30m.
Right now 1Password is operational. Live 1Password status →
# 2026-04-14 SEV1 Incident Postmortem - Hosted Service in the US experiencing high latency and errors # Incident Postmortem - Elevated Application Error **Date of Incident:** 2026-04-14 **Time of Incident \(UTC\):** 17:25 - 18:00 **Service\(s\) Affected:** Sign in, Admin console **Impact Duration:** Approximately 35 minutes ## Summary On April 14, 2026, [1Password.com](http://1Password.com) experienced elevated error rates due to an increase in traffic to our USA/Global infrastructure. Requests arrived more quickly than they could be serviced in our USA/global region. Customers experienced errors and high latency. This was not a security incident, and there was no loss of data. ## Impact on Customers * **Sign-in and account access:** Some customers in the USA/Global region experienced errors when attempting to sign in or access their 1Password accounts between 17:25 and 18:00 UTC on April 14, 2026. * **All 1Password clients:** The disruption applied to all client types, in
This incident has been resolved. We will publish a postmortem as soon as one is completed.
A fix has been implemented and we are monitoring the results.
The 1Password engineering team is investigating an issue where customers may be unable to sign in to 1Password. This issue may also prevent changes from syncing between 1Password clients. This issue impacts the 1Password.com (US) service.
The 1Password Hosted Service in the US is experiencing high latency and errors. The response team is currently investigating.
Our 5-minute checks didn't record a change in 1Password's overall status around this incident. Smaller or regional incidents often leave a provider's overall status green.
Overlapping incidents aren't necessarily related.
1Password reported 4 incidents in the last 90 days, 2 of them major or critical. A typical incident lasted 42 min. See 1Password's uptime and incident history