1password outage history

We are currently investigating this issue.

We are seeing some improvements to affected services but are continuing to investigate the issue.

A fix has been deployed and we are monitoring the results.

The deployed fix mitigated the issue causing increased error rates for users. We continue to monitor our services while we implement a permanent fix.

This incident has been resolved.

When choosing to view a vault profile using the web interface, a blank page is displayed instead. Our engineering team has found the root cause and are working towards deploying a fix.

A fix has been deployed and this issue is now resolved.

We are currently investigating reports of an incident affecting Device Trust. Some customers may experience delays in device posture checks or authentication failures. We will provide an update as soon as we have more information.

We have identified the triggering change and have rolled it back. We are monitoring to confirm that this has completely resolved the issue.

This incident has been resolved.

SaaS Manager is currently unable to communicate with Managed Credentials. As a result, customers using Better Together features may be unable to make changes to credential ownership. We are actively investigating the issue and will provide updates as more information becomes available.

A fix has been deployed and this issue is now resolved.

SaaS Manager customers with active workflows may have experienced a service degradation that prevented some workflows from running as scheduled. Our teams quickly identified the issue and implemented a fix. We are now monitoring the recovery to ensure services continue to return to normal.

This incident has been resolved.

Our engineering team is investigating an issue causing degraded user-related operations for individual and family accounts. Users are unable to confirm or delete users or create and delete service accounts. Users are also unable to load the Integrations page.

The issue has been identified and our Engineering team are working towards deploying a fix.

A fix has been deployed and this issue is now resolved.

A fix for this issue has been implemented, and our teams are monitoring. During the outage, GitHub Actions might have failed to pull the latest CLI version, causing the pipeline to fail.

We are aware of an outage of Device Trust and are investigating the issue.

We are continuing to investigate the issue.

The issue has been identified and a fix is being implemented.

A fix has been deployed and all services are operational.

# Incident Postmortem - Device Trust Authentication Outage **Date of Incident:** 2026-07-02 **Time of Incident \(UTC\):** 19:28 - 20:28 **Service\(s\) Affected:** This incident affected: USA/Global \(Device Trust Authentication Service, Device Trust Checks Server, Device Trust Portal, Device Trust API\) and Europe \(Device Trust Authentication Service, Device Trust Checks Server, Device Trust Portal, Device Trust API\). **Impact Duration:** 1 Hour ## Summary On July 2, 2026, 1Password Device Trust experienced an outage lasting approximately one hour, beginning at 19:28 UTC. During this window, all Device Trust services were unavailable and users were unable to authenticate. We have identified the root cause: an internal configuration change to our cloud load balancing infrastructure was applied more broadly than intended which temporarily made a required endpoint unreachable. This was not a security incident and did not involve any third party. The configuration has been corrected, service has been fully restored, and we have implemented additional safeguards to help prevent this type of issue from recurring. ## Impact on Customers * **All Device Trust services were completely unavailable during the 60-minute outage window. Users were unable to authenticate to any Device Trust service, including the authentication portal \(**[**auth.kolide.com**](http://auth.kolide.com)**\), admin console \(**[**app.kolide.com**](http://app.kolide.com)**\), API endpoints, and device server.** * **Number of Affected Customers \(approximate\):** 100% of Device Trust customers * **Geographic Regions Affected \(if applicable\):** US and EU ## What Happened? On July 2, 2026, A configuration change intended to improve the security configuration of an internal service was applied more broadly than intended, affecting a shared network routing component relied on by Device Trust. The change replaced the underlying network infrastructure supporting Device Trust. However, the traffic routing configuration continued to reference the previous infrastructure instead of the newly provisioned resources. As a result, Device Trust authentication endpoints became unreachable. Reverting the change restored connectivity and service. * **Timeline of Events \(UTC\):** * 19:28: Network configuration change applied; Network Load Balancers responsible for routing traffic for Device Trust services became unreachable * 19:30: Automated monitoring detects the outage and triggers alerts * 19:33: Incident is declared at [status.1password.com](http://status.1password.com) * 20:03: Root cause is identified as a load balancer configuration issue * 20:24: Load balancer is recreated with correct configuration * 20:26 Recovery is confirmed for [app.kolide.com](http://app.kolide.com) * 20:28 Recovery is confirmed for [auth.kolide.com](http://auth.kolide.com) * **Contributing Factors \(if any\):** * **Shared component scope not visible during review or validation.** The network infrastructure class affected by the change was shared across multiple services, but this dependency was not documented or surfaced in the change review process. As a result, the pre-production validation, while performed in a lower environment before production rollout, did not cover all dependent services, and the impact on Device Trust was not identified before the change reached production. * **Concurrent diagnostic signals slowed root cause identification.** At the time the outage began, unrelated certificate renewal errors surfaced alongside the network connectivity failure. Investigating both signals simultaneously delayed identification of the network configuration change as the root cause. ## How Was It Resolved? * **Resolution Steps:** Once the source of the outage was identified, engineers reverted the configuration change. The affected network infrastructure was recreated with its original, publicly accessible configuration, restoring routing to all Device Trust authentication endpoints. Service recovery was confirmed sequentially across affected services before the incident was closed. * **Verification of Resolution:** Following the revert, engineers verified that all Device Trust authentication endpoints were reachable and accepting traffic. Customer confirmation of resolution was subsequently received through the support team. ## What We Are Doing to Prevent Future Incidents * **Require explicit approval for destructive infrastructure changes.** We are implementing safeguards that require manual review and approval before changes that would destroy and recreate critical network infrastructure can be applied. This creates a forcing function to catch unintended scope before changes reach production. * **Improve scope visibility for shared infrastructure components.** We are documenting the dependencies between shared infrastructure components and the services that rely on them, and integrating this information into our change review process. Future changes to shared components will require an explicit assessment of downstream impact before deployment. * **Strengthen pre-production validation across shared dependencies.** We are updating our change promotion process to require validation against all services that share affected components — not only the intended target — before changes are promoted to production. * **Reduce single points of failure in traffic routing.** We are evaluating architectural changes to introduce redundancy into Device Trust's traffic routing configuration, so that a failure in any single component results in degraded service rather than a complete outage. ## Next Steps and Communication * No action is required from our customers at this time. We are committed to providing a reliable and stable service, and we are taking the necessary steps to learn from this event and prevent it from happening again. Thank you for your understanding. Sincerely, The 1Password Team

Users who are attempting to accept their invite with SSO enforcement are unable to accept the invite and receive a 403 error. Our engineering team is actively investigating the issue.

The issue has been identified and our engineering team is working towards deploying a fix.

Our engineering team is continuing to work on deploying a fix for this issue. In the meantime, a workaround has been identified. Please contact our support team directly at [email protected] and they will support you through the workaround steps.

This incident has been resolved.

Some users who are locked out of their 1Password account are encountering a “Something went wrong” error when attempting to restore access using a recovery code. Our development team is aware of the issue and is actively investigating the cause. We will provide updates as more information becomes available.

Our teams continue to investigate this issue. We are actively working to determine the cause and will share additional updates as they become available.

The issue is still under investigation. We will continue to share updates as they become available.

The investigation is ongoing. Our teams are actively working to determine the cause and will share updates as they become available.

The issue has been identified and a fix is being implemented.

A fix has been implemented and we are monitoring the results.

The issue is now resolved, and access to 1Password services should be fully restored.

We have identified the cause of the synchronization issues affecting legacy 1Password 7 clients (OPI7 and OPM7) with 1Password and are deploying a fix. Affected customers may experience item creations or updates not synchronizing to 1Password, in some cases without a visible error. We expect service to be restored shortly and will provide another update once the fix has been fully deployed and verified. Modern clients and broader 1Password functionality do not appear to be affected.

This incident has been resolved.

Sign in attempt audit events are currently delayed and admins are unable to migrate to hosted provisioning. Our engineering team has identified the issue and are actively working on a fix.

A fix has been deployed and we are now monitoring the results.

We are still monitoring the results of the deployed fix. Hosted provisioning issues are resolved. Audit events in some regions are caught up while others are still in progress.

This incident has been resolved.

We are currently investigating an issue affecting the Device Trust Authentication Service. Customers may experience timeouts or receive 503 responses when attempting to authenticate with Device Trust. Our team is actively working to identify the cause and restore normal service as quickly as possible.

Our teams continue to investigate the cause of timeout errors affecting the Device Trust Authentication Service.

Our teams continue to investigate the cause of timeout errors affecting the Device Trust Authentication Service. Customers may experience authentication failures, timeouts, or 503 errors when attempting to authenticate with Device Trust. At this time, there is no significant change in impact or scope to report. Investigation and mitigation efforts remain ongoing, and we will provide another update as soon as additional information becomes available.

Authentication services have recovered, and our teams continue to investigate the cause of timeout errors affecting the Device Trust Authentication Service. Investigation and mitigation efforts remain ongoing, and we will provide another update as soon as additional information becomes available.

Our teams have identified a cause of the issues affecting the Device Trust Authentication Service and have taken steps to provide relief. We are seeing improved service performance and are continuing to monitor the situation closely to ensure stability. We will provide further updates as needed.

This incident has been resolved.

Files can not be uploaded or downloaded, and images may not be loading properly. Pages within the application may not be loading. Some integrations and workflows may have experienced errors. This issue affects the US and EU regions. Our engineering team is currently investigating.

The issue has been identified, and our engineers are working on a fix.

Issues with file uploads and downloads, pages not loading, and errors affecting some integrations and workflows are now resolved. Customers may still experience issues with images loading properly, and our engineering team is actively working to resolve them. We expect further progress and resolution later today. The issue affected both the US and EU regions.

This incident has been resolved.

Workflows and integrations have not run as of approximately 12:30pm ET today, this means that automatic onboarding and off-boarding are currently not occurring. In addition, the Workflows and Integrations pages are failing to load. Our Engineering team has identified the issue and are currently working on a fix.

A fix has been implemented and we are now monitoring the results. Failed workflows will need to be manually re-run, failed integrations will re-run automatically within 24 hours but likely sooner.

This incident has been resolved.

We are currently investigating an issue causing errors and increased latency across our services. Customers may experience failures or delays when logging in and syncing, including via CLI.

Our teams continue to investigate an issue causing errors and increased latency across our services. Customers may experience failures or delays when logging in and syncing, including via CLI. We are actively working to identify the root cause and will provide further updates as more information becomes available.

We are seeing signs of recovery for the issue causing errors and increased latency across our services. Some customers may still experience intermittent failures or delays when logging in and syncing, including via CLI. Our teams continue to monitor the situation closely.

Service has largely recovered, and we are continuing to monitor the situation closely. Some customers may still experience intermittent issues with login and syncing, including via CLI.

Traffic levels have returned to normal and service performance has stabilized. We are continuing to monitor to ensure full recovery.

This incident has been resolved.

# Incident Postmortem - Login and Sync Issues **Date of Incident:** 2026-04-27 **Time of Incident \(UTC\):** 14:15 - 15:41 **Service\(s\) Affected:** All web APIs **Impact Duration:** Approximately 86 minutes ## Summary On April 27, 2026, [1Password.com](http://1password.com/) experienced a period of elevated error and full service unavailability in our USA/Global region. A defect deployed in application scaling logic caused a cascading failure during peak usage. This resulted in a period of service unavailability for customers in the USA/Global region. This was not a security incident, and there was no loss of data. ## Impact on Customers * **Sign-in and account access:** Customers in the USA/Global region experienced errors or were unable to sign in or access their 1Password accounts between approximately 14:15 and 15:41 UTC on April 27, 2026. * **All 1Password clients:** The disruption applied to all client types, including the web app, CLI, browser extensions, and desktop and mobile applications, for customers connecting through the USA/Global region. * **Geographic regions affected:** Only customers on the USA/Global region were affected. Other regions were not impacted. ## What Happened? We deployed a change to how our services signal their readiness to serve requests, which contained a latent defect. * **Timeline of events:** * **2026-04-27 14:15 UTC** - Load increase triggers issues. * **2026-04-27 14:29 UTC** - Incident declared; response team mobilized. * **2026-04-27 15:41 UTC** - Issue identified and fix deployed. * **2026-04-28 18:06 UTC** - Incident formally resolved following monitoring. ## How Was It Resolved? Our on-call engineering team identified the scaling logic as the cause of the cascading failure and disabled it via a configuration change. Once disabled, capacity was restored, and traffic recovered. A subsequent configuration change was made to prevent this logic from being re-enabled in production environments. ## What We Are Doing to Prevent Future Incidents * **Immediate fix:** We disabled the defective health check logic and locked the configuration to prevent it from being re-enabled in production. * **Retrospective:** We are conducting a full retrospective with the incident responders to identify further improvements to our systems and our response processes. ## Next Steps and Communication * No action is required from our customers at this time. We are committed to providing a reliable and stable service, and we are taking the necessary steps to learn from this event and prevent it from happening again. Thank you for your patience and understanding. Sincerely, The 1Password Team

We’re aware of an issue affecting sign-in to 1Password SaaS Manager. Our teams are actively investigating and working to resolve this as quickly as possible.

The issue affecting sign-in to 1Password SaaS Manager has been mitigated. Our teams are continuing to monitor the situation to ensure stability.

This incident has been resolved.

The 1Password Hosted Service in the US is experiencing high latency and errors. The response team is currently investigating.

The 1Password engineering team is investigating an issue where customers may be unable to sign in to 1Password. This issue may also prevent changes from syncing between 1Password clients. This issue impacts the 1Password.com (US) service.

A fix has been implemented and we are monitoring the results.

This incident has been resolved. We will publish a postmortem as soon as one is completed.

# 2026-04-14 SEV1 Incident Postmortem - Hosted Service in the US experiencing high latency and errors # Incident Postmortem - Elevated Application Error **Date of Incident:** 2026-04-14 **Time of Incident \(UTC\):** 17:25 - 18:00 **Service\(s\) Affected:** Sign in, Admin console **Impact Duration:** Approximately 35 minutes ## Summary On April 14, 2026, [1Password.com](http://1Password.com) experienced elevated error rates due to an increase in traffic to our USA/Global infrastructure. Requests arrived more quickly than they could be serviced in our USA/global region. Customers experienced errors and high latency. This was not a security incident, and there was no loss of data. ## Impact on Customers * **Sign-in and account access:** Some customers in the USA/Global region experienced errors when attempting to sign in or access their 1Password accounts between 17:25 and 18:00 UTC on April 14, 2026. * **All 1Password clients:** The disruption applied to all client types, including the web app, browser extensions, and desktop and mobile applications, for customers connecting through the USA/Global region. * **Number of affected requests:** Approximately 2.95% of requests over the incident window to [1Password.com](http://1Password.com) \(USA/Global\) during the incident window resulted in errors or timeouts, though for some brief spikes up to 45% of requests failed. * **Geographic regions affected:** Customers on our USA/Global only, other regions were not affected. ## What Happened? An unusually high volume of traffic exceeded the capacity of our controls, and triggered latency and errors in the underlying applications. * **Timeline of events:** * **2026-04-14 17:25** - Start of incident. * **2026-04-14 17:36** - Issue identified. * **2026-04-14 17:51** - Fix implemented. * **2026-04-14 18:01** - Recovery complete. * **Root cause analysis:** An increase in traffic exceeded the capacity of our traffic management layer, causing degraded service for customers in the USA/Global region. ## How Was It Resolved? * Established runbooks for load shedding and system upgrades mitigated the issue. ## What We Are Doing to Prevent Future Incidents * **Resolution:** We made two key changes to prevent recurrence: 1. **Increased capacity of internal systems** 2. **Upgraded traffic controls at the network edge** * **Verification:** Since implementing these changes, we have observed several additional instances of unusually high traffic matching this incident. In each case, the new controls handled the traffic automatically with no impact to customers or our systems. ## Next Steps and Communication * No action is required from our customers at this time. We are committed to providing a reliable and stable service, and we are taking the necessary steps to learn from this event and prevent it from happening again. Thank you for your understanding. Sincerely, The 1Password Team

SSO is experiencing degraded functionality because of an upstream provider. We are monitoring, and users may need to retry when authenticating with their IdP.

We are continuing to monitor for any further issues.

This incident has been resolved.

Teams accounts are currently unable to access their Environments. Our engineering team has identified the issue and are working towards deploying a fix.

Our engineering team has deployed a fix and we are monitoring the results.

This incident has been resolved.