1Password reported this major-impact incident on its official status page on Sep 24, 2025, 03:00 UTC. It was resolved after 1h 9m.
Right now 1Password is operational. Live 1Password status →
# Incident Postmortem - Some customers are unable to interact with the admin console **Date of Incident:** 2025-09-24 **Time of Incident \(UTC\):** 02:27 - 17:16 **Service\(s\) Affected:** Admin console, Sign in **Impact Duration:** 36:49 ## Summary Some customers with certain account configurations were placed on a blocklist and presented with a 403 error page after accessing the admin console. ## Impact on Customers * **Admin console:** Affected customers were presented with a 403 error page whenever they tried to interact with any of the admin console pages. * **Log in:** Affected customers were also unable to log in to the application. * **Number of Affected Customers \(approximate\):** 515 * **Geographic Regions Affected \(if applicable\):** All regions ## What Happened? * **Timeline of Events \(UTC\):** * Sep 24th 2:27am: Spike in application monitoring alerted engineers to increased rates of IP blocking * Sep 24th 3:00am: Cause identified as a change to req
This incident has been resolved.
Our engineering team has rolled out mitigation to remedy affected users. We are monitoring the results.
Our engineering team has identified the issue and are working towards mitigating.
We are continuing to investigate the issue.
We are actively investigating an issue where some users are encountering errors when interacting with the admin console, which leads to errors during sign-in.
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