1Password Outage History

The 1Password US hosted service experienced high latency and errors for 8.5 hours, preventing users from signing in and syncing changes between devices. The incident affected all major components including SSO, syncing, billing, MFA, admin console, and APIs. The engineering team implemented a fix and confirmed resolution after monitoring the results.

1Password Teams accounts experienced a 24.2-hour outage preventing access to Developer Environments, which affected password access and CLI functionality. The engineering team identified the root cause and deployed a fix, followed by a monitoring period before full resolution.

1Password Individual and Family account users experienced a 3.3-hour outage preventing access to their Developer Environments, affecting password access and CLI functionality. The engineering team identified the root cause and deployed a fix to resolve the issue.

1Password experienced a feature availability issue where certain features were unexpectedly turned off for some customers. The incident lasted 34 minutes and was classified as minor impact. The team implemented a fix and confirmed resolution after monitoring the results.

1Password experienced a major incident where users were unable to read vault items from the CLI tool, specifically affecting the `op read` and `op document get` commands. The issue expanded during the incident to also impact document retrieval performance outside of the CLI across the broader service. The incident lasted 2.2 hours with the team identifying the root cause, developing a fix, and deploying the resolution.

1Password's Support team performed scheduled maintenance that caused delays in customer support response times. The maintenance lasted 11.1 hours and affected users' ability to receive timely responses to their support requests. The maintenance was completed successfully and normal support operations resumed.

1Password experienced a sign-in issue where the 2FA prompt failed to appear for users who changed their password and had 2FA enabled, or when the Restricted Failed Login Attempts policy was enabled with 2FA enforced. As a temporary mitigation, the Sign-In Attempts policy was disabled for all affected users during the incident. The issue was permanently resolved with the release of version 8.12.4 after approximately 39 days.