# Sign-in failure in some cases due to 2FA prompt not appearing

- Provider: [1Password](https://down.guide/1password)
- Level: confirmed
- Impact: Degraded
- lasted 38d 19h
- started 2026-01-23 20:33 UTC
- Sign in, Sign in, Sign in +1
- id: DWN-701171b359
- Official page: https://stspg.io/964rrz5cq8py

## Updates from 1Password
### 2026-01-23 20:33 UTC: investigating
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.

### 2026-01-23 23:10 UTC: identified
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.

### 2026-01-26 21:30 UTC: monitoring
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.

### 2026-01-29 20:02 UTC: monitoring
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.

### 2026-01-30 16:55 UTC: monitoring
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.

### 2026-02-02 19:21 UTC: monitoring
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.

### 2026-02-11 19:57 UTC: monitoring
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.

### 2026-02-18 22:42 UTC: monitoring
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.

### 2026-03-03 15:52 UTC: resolved
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.

---
down.guide reads providers' official status pages every minute and adds its own evidence, always labeled. Free, no account. Agents: MCP at https://down.guide/mcp, REST at https://down.guide/api/v1, feeds at https://down.guide/feed. Built by Sazabi (https://sazabi.com/?utm_source=down-guide&utm_medium=markdown).