1Password reported this major-impact incident on its official status page on Sep 26, 2025, 16:51 UTC. It was resolved after 3h 33m.
Right now 1Password is operational. Live 1Password status →
# Incident Postmortem - Degraded performance when accessing 1Password **Date of Incident:** 2025-09-26 **Time of Incident:** 4:20pm UTC - 5:39pm UTC **Service\(s\) Affected:** SSO, Web Sign In, Sign Up, Web Interface, CLI **Impact Duration:** ~60 minutes ## Summary On September 26, 2025 at 4:20 UTC 1Password’s web interface and APIs experienced degraded performance for all customers in the US region. This was not a result of a security incident and customer data was not affected. ## Impact on Customers During the duration of the incident: * **Web interface, Administration:** Customers experienced delays when accessing the 1Password web interface. * **Single Sign-on \(SSO\), Multi-factor Authentication \(MFA\):** Users with SSO or MFA enabled experienced delays, and in some cases failures to login. * **Command Line Interface \(CLI\):** CLI users faced increased latency and timeouts when attempting to access our web APIs. * **Browser Extension:** Users requiring web interfac
This incident has been resolved. We will publish a post-mortem as soon as we complete it.
The engineering team deployed a mitigation, which has addressed the issue. We will continue to monitor performance.
The engineering team is rolling out a mitigation in our production environment.
The engineering team is continuing to test a mitigation in our test environment before deploying it to production. Customer impact is being actively managed and instances of slowdowns should continue to decrease.
The engineering team has identified the issue and we are continuing to test a mitigation in our test environment before rolling it out to production. Customer impact is being actively managed and slowdowns should be increasingly rare.
Engineering teams are testing a mitigation in our non-production environments to verify before rolling it out to our production environments. Customer impact is being actively managed and slowdowns should be rare if they occur at all.
Engineering teams have identified a potential cause and are actively managing customer impact. Customers may see some slowdowns, but due to the active management those slowdowns are unlikely.
The engineering team is actively managing degraded performance and continuing attempts to identify root cause. Customers may still experience some slowdowns when accessing 1Password online.
The engineering team is actively managing degraded performance and simultaneously attempting to identify root cause. Customers may still experience some slowdowns when accessing 1Password online.
The engineering team is continuing to investigate and actively managing service degradation. Customers may still experience periods of slowdowns when accessing the 1Password service.
Overall service is still degraded, but experiencing periods of improvement.
The engineering team is restarting key systems in an attempt to alleviate slowdowns.
We are actively investigating an issue where customers may be experiencing degraded performance and slowdowns when accessing 1Password.
Our 5-minute checks didn't record a change in 1Password's overall status around this incident. Smaller or regional incidents often leave a provider's overall status green.
Overlapping incidents aren't necessarily related.
1Password reported 4 incidents in the last 90 days, 2 of them major or critical. A typical incident lasted 42 min. See 1Password's uptime and incident history