- Level
- confirmed
- Worst impact
- Major outage
- Components
- Sign in, Sign up, Syncing items between your devices, Saving password and other items, Billing, Admin console, SSO (Single Sign On), Multi-factor Authentication (MFA), Command Line Interface (CLI), 1Password Connect, Service Accounts, Partnership API, Item Sharing, User & Group Provisioning
- Regions
- us
- Down Index
- 48of 100
What to do
Check whether you use 1Password Sign in, Sign up, Syncing items between your devices, Saving password and other items and 10 more in us. Check your stack
Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.Confirm your retries, queues and scheduled jobs caught up after the 8h 30m it lasted.
Anything that failed between 2026-04-14 17:25 UTC and 2026-04-15 01:54 UTC may need a replay.Subscribe to 1Password's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=1password works in Slack (/feed subscribe), Discord feed bots and any RSS reader.
Updates from 1Password 5
- investigating
The 1Password Hosted Service in the US is experiencing high latency and errors. The response team is currently investigating.
provider
- investigating
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.
provider
- monitoring
A fix has been implemented and we are monitoring the results.
provider
- resolved
This incident has been resolved. We will publish a postmortem as soon as one is completed.
provider
- postmortem
# 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, including the web app, browser extensions, and desktop and mobile applications, for customers connecting through the USA/Global region. * **Number of affected requests:** Approximately 2.95% of requests over the incident window to [1Password.com](http://1Password.com) \(USA/Global\) during the incident window resulted in errors or timeouts, though for some brief spikes up to 45% of requests failed. * **Geographic regions affected:** Customers on our USA/Global only, other regions were not affected. ## What Happened? An unusually high volume of traffic exceeded the capacity of our controls, and triggered latency and errors in the underlying applications. * **Timeline of events:** * **2026-04-14 17:25** - Start of incident. * **2026-04-14 17:36** - Issue identified. * **2026-04-14 17:51** - Fix implemented. * **2026-04-14 18:01** - Recovery complete. * **Root cause analysis:** An increase in traffic exceeded the capacity of our traffic management layer, causing degraded service for customers in the USA/Global region. ## How Was It Resolved? * Established runbooks for load shedding and system upgrades mitigated the issue. ## What We Are Doing to Prevent Future Incidents * **Resolution:** We made two key changes to prevent recurrence: 1. **Increased capacity of internal systems** 2. **Upgraded traffic controls at the network edge** * **Verification:** Since implementing these changes, we have observed several additional instances of unusually high traffic matching this incident. In each case, the new controls handled the traffic automatically with no impact to customers or our systems. ## 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 understanding. Sincerely, The 1Password Team
provider
Reports count in aggregate; nothing about you is shown.
Corrections
None so far.
Something wrong on this page? Report an error or send us a note. Every fix is listed here.
Questions about DWN-86edddc490
Is 1Password still down?
No, this incident was resolved 2026-04-15 01:54 UTC. For 1Password's live state, see https://down.guide/1password.
How long did it last?
8h 30m, from 2026-04-14 17:25 UTC to 2026-04-15 01:54 UTC, by the times 1Password posted.
What was affected?
1Password named Sign in, Sign up, Syncing items between your devices, Saving password and other items and 10 more in us.
What caused it?
1Password hasn't published a root cause. If it does, it shows here.
Where does this come from?
1Password's official status page, https://status.1password.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.