Skip to main content
1Password

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

Degraded Lasted 38d 19h · started · 1Password's page

Level
confirmed
Worst impact
Degraded
Components
Sign in, Sign in, Sign in, Sign in
Down Index
24of 100

What to do

  • Check whether you use 1Password Sign in, Sign in, Sign in, Sign in. 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 38d 19h it lasted.

    Anything that failed between 2026-01-23 20:33 UTC and 2026-03-03 15:52 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 9

  1. 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.

    provider

  2. 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.

    provider

  3. 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.

    provider

  4. 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.

    provider

  5. 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.

    provider

  6. 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.

    provider

  7. 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.

    provider

  8. 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.

    provider

  9. 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.

    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-701171b359

Is 1Password still down?

No, this incident was resolved 2026-03-03 15:52 UTC. For 1Password's live state, see https://down.guide/1password.

How long did it last?

38d 19h, from 2026-01-23 20:33 UTC to 2026-03-03 15:52 UTC, by the times 1Password posted.

What was affected?

1Password named Sign in, Sign in, Sign in, Sign in.

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.