1Password incident
Sign-in failure in some cases due to 2FA prompt not appearing
1Password experienced a minor incident on January 23, 2026 affecting Sign in and Sign in and 1 more component, lasting 38d 19h. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Jan 23, 2026, 08:33 PM UTC
Our team has identified an issue and are actively investigating where when a password is changed and an account has 2FA enabled, the 2FA prompt does not appear upon attempting to sign-in.
- identified Jan 23, 2026, 11:10 PM UTC
Our team has identified an issue where when a password is changed and an account has 2FA enabled or when the Restricted Failed Login Attempts policy is enabled with 2FA enforced, the 2FA prompt does not appear upon attempting to sign-in. We are actively working on a fix and that work will continue into early next week.
- monitoring Jan 26, 2026, 09:30 PM UTC
To mitigate this issue, we've had to temporarily disable the Sign-In Attempts policy and are actively working on a permanent fix to resolve the issue and re-enable use of this policy. This policy will not be in effect for those with it turned on until we resolve this issue.
- monitoring Jan 29, 2026, 08:02 PM UTC
To mitigate this issue, we temporarily disabled the Sign-In Attempts policy — this policy will not be in effect for those with it turned on until we resolve this issue. We are actively working on a permanent fix to resolve the issue and re-enable use of this policy. We will share another update when that work is complete.
- monitoring Jan 30, 2026, 04:55 PM UTC
To mitigate this issue, we temporarily disabled the Sign-In Attempts policy — this policy will not be in effect for those with it turned on until we resolve this issue. We are actively working on a permanent fix to resolve the issue and re-enable use of this policy. We will share another update when that work is complete.
- monitoring Feb 02, 2026, 07:21 PM UTC
To mitigate this issue, we temporarily disabled the Sign-In Attempts policy — this policy will not be in effect for those with it turned on until we resolve this issue. Our team continues to work on a permanent fix to resolve the issue and re-enable use of this policy. We will share another update when that work is complete.
- monitoring Feb 11, 2026, 07:57 PM UTC
Our engineering team are in the process of merging the fix for this issue and we'll be able to provide a date for when the fix will be deployed, by the end of this week. In the meantime, the Sign-In attempts policy will remain disabled until we determine all areas where it is conflicting with 2FA.
- monitoring Feb 18, 2026, 10:42 PM UTC
The fix for the identified 2FA issue is currently available in our Beta release, and planned to be deployed in our next Production release (8.12.4). In the meantime, the Sign-In attempts policy will remain disabled until we determine all areas where it is conflicting with 2FA.
- resolved Mar 03, 2026, 03:52 PM UTC
The fix for the identified 2FA issue has been resolved as of version 8.12.4. The Sign-In attempts policy will become available in the coming weeks.