- Level
- confirmed
- Worst impact
- Major outage
- Components
- 1Password.com website, Sign in, Sign up, Syncing items between your devices, Saving password and other items, Access to passwords and other items, Billing, Admin console, SSO (Single Sign On), Multi-factor Authentication (MFA), Command Line Interface (CLI), 1Password Connect, Service Accounts, Partnership API, Events API and Reporting, Item Sharing, User & Group Provisioning
- Regions
- us
- Down Index
- 49of 100
What to do
Check whether you use 1Password 1Password.com website, Sign in, Sign up, Syncing items between your devices and 13 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 1d 3h it lasted.
Anything that failed between 2026-04-27 14:54 UTC and 2026-04-28 18:00 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 7
- investigating
We are currently investigating an issue causing errors and increased latency across our services. Customers may experience failures or delays when logging in and syncing, including via CLI.
provider
- investigating
Our teams continue to investigate an issue causing errors and increased latency across our services. Customers may experience failures or delays when logging in and syncing, including via CLI. We are actively working to identify the root cause and will provide further updates as more information becomes available.
provider
- identified
We are seeing signs of recovery for the issue causing errors and increased latency across our services. Some customers may still experience intermittent failures or delays when logging in and syncing, including via CLI. Our teams continue to monitor the situation closely.
provider
- monitoring
Service has largely recovered, and we are continuing to monitor the situation closely. Some customers may still experience intermittent issues with login and syncing, including via CLI.
provider
- monitoring
Traffic levels have returned to normal and service performance has stabilized. We are continuing to monitor to ensure full recovery.
provider
- resolved
This incident has been resolved.
provider
- postmortem
# 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
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-48b2221351
Is 1Password still down?
No, this incident was resolved 2026-04-28 18:00 UTC. For 1Password's live state, see https://down.guide/1password.
How long did it last?
1d 3h, from 2026-04-27 14:54 UTC to 2026-04-28 18:00 UTC, by the times 1Password posted.
What was affected?
1Password named 1Password.com website, Sign in, Sign up, Syncing items between your devices and 13 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.