1Password outage history

1Password reported a disruption to its Device Trust Service that caused delays in device posture checks and authentication failures for some customers. The incident began at 8:45 PM UTC and affected users relying on Device Trust for sign-in and posture verification.

The triggering change was identified and rolled back at 8:55 PM UTC, with monitoring ongoing to confirm a full recovery. By 9:15 PM UTC, the Device Trust Authentication Service had returned to normal and affected components were restored.

An outage in 1Password's SaaS Manager disrupted account governance functions, preventing changes to credential ownership for users of Better Together features. The disruption began in the USA/Global region around 5:55 PM UTC and extended to the Europe region around 6:50 PM UTC as the issue persisted across multiple regions. Users reliant on managing credential ownership could have experienced limited ability to modify ownership settings during the incident.

1Password users with active SaaS Manager workflows experienced a brief service degradation as some workflows did not run as scheduled. The impact affected the USA/Global and Europe SaaS Manager components, causing a short disruption to automated tasks for those users. The incident began at 6:55 PM UTC and was resolved by 7:00 PM UTC. 1Password's teams quickly identified the issue and implemented a fix, with monitoring ongoing to ensure services return to normal operations.

Users faced degraded user-related operations in 1Password beginning at 7:00 PM UTC, with the ability to confirm or delete users, create/delete service accounts, and load the Integrations page affected. The impact spanned multiple regions and components, including USA/Global Service Accounts and User & Group Provisioning, Canada, Europe, and Enterprise deployments, disrupting core account-management workflows for about an hour.

1Password experienced a Device Trust outage that disrupted authentication-related services across USA/Global and Europe. The disruption affected the Device Trust Authentication Service, Checks Server, Portal, and API, leaving users unable to complete device trust workflows and impacting sign-ins that rely on device trust checks. The incident began at 7:50 PM UTC with multiple Device Trust components going down.

Status updates indicated the issue was identified and a fix was being implemented by 8:15 PM UTC, with all affected components restored to service by 8:35 PM UTC after about 45 minutes. This restored authentication and device trust workflows for users.

Users trying to accept invitations with SSO enforcement could not complete onboarding due to 403 errors, a problem affecting the USA/Global, Canada, Europe, and Enterprise User & Group Provisioning components. The incident began at 10:11 PM UTC when the invite flow started failing and affected onboarding for provisioned accounts. Engineers identified the issue by 10:55 PM UTC and began deploying a fix; a workaround was shared by 11:45 PM UTC with guidance from support. The issue was resolved by 2:10 PM UTC as provisioning returned to normal across all affected regions.

An incident affected users trying to restore access with a recovery code, causing sign-in issues across multiple regions. In particular, users attempting to unlock accounts in Europe / Sign in, Enterprise / Sign in, Canada / Sign in, and USA/Global / Sign in encountered a 'Something went wrong' error when using a recovery code. The disruption began around 5:15 PM UTC and prevented access restoration for a portion of users, impacting the sign-in experience for those accounts for a period of time.

Engineers identified the problem and began implementing a fix, with progress updates around 6:35 PM UTC and 6:55 PM UTC. A fix was deployed and monitoring started, and all regions returned to normal by 7:05 PM UTC. The service was resumed for affected users as the recovery code flow regained reliability.

1Password experienced a brief maintenance window impacting the Device Trust Authentication Service in the USA/Global and Europe regions. The maintenance began at 1:01 AM UTC as the system transitioned from up to maintenance, affecting authentication operations for a short period. The affected components were the USA/Global / Device Trust Authentication Service and the Europe / Device Trust Authentication Service.

The services were restored by 2:05 AM UTC, with normal operation return after the maintenance window. The event was contained to that window and did not indicate a broader outage; users relying on device-trust authentication may have experienced brief interruptions during the window.

The 1Password incident affected sign-in for users where MFA prompts failed to appear, especially after password changes with MFA enabled. Users also reported intermittent performance issues when accessing 1Password.com or through developer tools. The issue was first acknowledged after a status update at Jan 23, 2026 8:35 PM UTC, with affected regions including Europe, USA/Global, Canada, and Enterprise sign-in flows. Reports from North America and Europe described MFA codes not working and sign-in delays, suggesting a broader regional impact across multiple components.

1Password communications acknowledged ongoing investigation and mitigation efforts. A fix for the 2FA sign-in problem was indicated as available in the Beta release and planned for deployment in the next Production release (8.12.4), while the Sign-in attempts policy remained disabled pending full resolution. The situation continued through late February with monitoring and updates as of Feb 21, 2026 7:40 PM UTC, affecting users across Europe, North America, and the UK.

1Password.com experienced intermittent issues with some forms across multiple regions, including Enterprise, Europe, Canada, and USA/Global. Users attempting to submit or interact with forms may have encountered failures or delays. The outage began at Jan 12, 2026 5:25 PM UTC and lasted approximately 5 hours and 35 minutes, with service restored by Jan 12, 2026 11:00 PM UTC. The disruption was tied to an issue with one of 1Password's vendors, and the team worked with the vendor to restore service. The incident prompted two official status updates on the 1Password status page before resolution.