1password 中断历史

1. 2026年10月16日 UTC 23:45investigating

   我们目前正在调查这一问题.

2. 2026年10月17日 UTC 00:34investigating

   我们看到受影响的服务有所改进,但正在继续调查这一问题.

3. 2026年10月17日 UTC 03:13monitoring

   已经部署了一个固定方案,我们正在监测结果.

4. 2026年10月19日 UTC 20:12monitoring

   安装的固定装置减轻了造成用户出错率上升的问题。 我们继续监测我们的服务,同时执行永久的解决方案.

5. 2026年10月20日 UTC 19:48resolved

   这一事件已经得到解决.

自动翻译自官方事件更新。

1. 2026年10月16日 UTC 17:31identified

   在选择使用网络界面查看金库配置时,会显示空白页面。 我们的工程队找到了根源,并正在努力部署一个固定方案.

2. 2026年10月16日 UTC 17:42resolved

   已经安装了一个固定装置,这个问题现已得到解决.

自动翻译自官方事件更新。

1. 2026年9月9日 UTC 20:43investigating

   我们正在调查一起影响设备信托基金的事件的报告。 一些客户在设备态势检查或认证失败时可能会遇到延误. 一旦掌握更多信息,我们将提供最新情况.

2. 2026年9月9日 UTC 20:53monitoring

   我们已经查明了触发性变化,并已将其卷回。 我们正在监测,以确认这已完全解决问题.

3. 2026年9月9日 UTC 21:11resolved

   这一事件已经得到解决.

自动翻译自官方事件更新。

1. 2026年7月22日 UTC 17:55investigating

   SaaS经理目前无法与管理全权证书联系。 因此,使用"更好共同"功能的客户可能无法对证书所有权进行修改. 我们正在积极调查这一问题,并将在获得更多信息后提供最新情况.

2. 2026年7月22日 UTC 19:20resolved

   已经安装了一个固定装置,这个问题现已得到解决.

自动翻译自官方事件更新。

1. 2026年7月17日 UTC 18:52monitoring

   SaaS管理器拥有活泼工作流程的客户可能经历了服务退化,使得一些工作流程无法如期运行. 我们的小组迅速查明了这一问题,并采取了一项措施。 我们现在正在监测复苏情况,以确保各项服务继续恢复正常.

2. 2026年7月17日 UTC 18:57resolved

   这一事件已经得到解决.

自动翻译自官方事件更新。

1. 2026年7月13日 UTC 18:59investigating

   我们的工程组正在调查一个导致个人和家庭账户用户业务退化的问题。 用户无法确认或删除用户或创建并删除服务账户. 用户也无法加载整合页面.

2. 2026年7月13日 UTC 19:37identified

   这个问题已经确定,我们的工程小组正在努力部署一个固定装置.

3. 2026年7月13日 UTC 19:57resolved

   已经安装了一个固定装置,这个问题现已得到解决.

自动翻译自官方事件更新。

1. 2026年7月13日 UTC 15:47resolved

   这一问题的解决已经落实,我们的小组正在监测。 在停电期间,GitHub Actions可能未能拉出最新的CLI版本,导致管道故障.

自动翻译自官方事件更新。

1. 2026年7月2日 UTC 19:44investigating

   我们知道设备信托公司停业,正在调查这一问题.

2. 2026年7月2日 UTC 20:05investigating

   我们正在继续调查这个问题。

3. 2026年7月2日 UTC 20:12identified

   这一问题已经确定,一个解决办法正在实施之中.

4. 2026年7月2日 UTC 20:30resolved

   已部署一个固定装置,所有服务都已投入使用.

5. 2026年7月11日 UTC 01:05postmortem

   # 死后事件 - 设备信任认证退出 ** 事件日期:** 2026-07-02 ** 事件时间\(UTC):** 19:28-20:28 ** 受影响:** 这起事件影响了:USA/Global\(DEVice Trust Certification Service, Device Trust Certification Server, Device Trust Portal, Device Trust API\)和欧洲\(DEVice Trust API Certification Server, Device Trust API\). ** 影响时间:** 1小时 □ 总结 2026年7月2日,1Password Device Trust经历了持续约一小时的停电,从协调世界时19:28起. 在此窗口中,所有设备托管服务都无法获得,用户无法认证. 我们查明了根源:我们云量平衡基础设施的内部配置改变应用范围比预期的要广,这暂时使一个必要的终点无法到达。 这不是安全事件,也没有涉及任何第三方。 配置得到纠正,服务全面恢复,我们实施了额外的保障措施来帮助防止此类问题再起. □ 对客户的影响 * ** 在60分钟的停电窗口中,完全没有所有设备信托服务。 用户无法认证任何设备信托服务,包括认证门户\(****auth.kolide.com**)(http://auth.kolide.com) * ** 受影响的客户数量\(大约\):** 100%的装置信托客户 * ** 受影响地区(如果适用):** 美国和欧盟 □发生了什么事? 2026年7月2日,旨在改进内部服务安全配置的配置改变被应用得比预期的要广泛,影响了由"设备信托"依赖的共享网络路由组件. 这一改变取代了支持设备信托基金的基本网络基础设施。 然而,交通线路配置继续参照以前的基础设施,而不是新提供的资源。 因此,"设备信托"认证端点变得无法通达. 恢复变更恢复了连接和服务. * ** 事件时间线\(UTC):** * 19:28:应用网络配置改变;负责设备托管服务线路流量的网络负荷平衡器变得无法访问 * 19:30:自动监测检测断电并触发警报 * 19:33:事件公布于[status.1password.com] (http://status.1password.com). *20:03:根因被确定为负载平衡器配置问题 * 20: 24: 装入平衡器以正确的配置重现 * [app.kolide.com](http://app.kolide.com)确认恢复。 * 20:28 [auth.kolide.com] (http://auth.kolide.com)确认恢复。 * ** 促成因素\ (如果有):** * ** 审评或审定期间不可见的共享组成部分范围。 ** 受这一变化影响的网络基础设施类别由多个服务共享,但在变革审查过程中没有记录或浮出水面。 因此,生产前的验证虽然在生产推出前在更低的环境中进行,但并不涵盖所有依赖性服务,在变化达到出产前没有识别出对"设备信托"的影响. * 当前的诊断信号减缓了根源的识别。 ** 在断电开始时,不相干的证书更新出错与网络连接失败一起浮出水面. 同时调查这两个信号都延迟了网络配置变化作为根本原因的识别. □是怎样解决的? * ** 决议步骤:** 一旦断电源被确定,工程师们就恢复了配置变化. 受影响的网络基础设施用其最初的、可公开查阅的配置进行了再造,恢复了所有设备信托认证终点的线路。 在事件结束前,已连续确认服务恢复情况。 ** 核查决议:** 复出后,工程师核实所有"设备信托"认证端点都可以到达并接受流量. 随后通过支助小组收到了客户对决议的确认。 □我们正在做的防止未来事件 * 需要明确核准破坏性基础设施的改变。 ** 我们正在实施保障措施,这些保障措施需要人工审查和批准,然后才能实施破坏和再造关键网络基础设施的变革。 这产生了一种迫使在变化到达生产之前捕捉出意料范围的功能. * 提高共享基础设施组成部分的能见度。 ** 我们正在记录共享基础设施组成部分与依赖这些组成部分的服务之间的依赖性,并将这些信息纳入我们的改革审查进程。 今后对共同组成部分的改变将需要在部署之前明确评估下游的影响。 * ** 在所有共同依赖国之间加强生产前验证。 ** 我们正在更新我们的促进改革进程,要求在推动改革投入生产之前,对所有共享受影响组成部分的服务进行验证——不仅是预定目标。 * ** 减少交通线路故障的单点。 ** 我们正在评估建筑的改变,以便将冗余引入设备信托公司的交通线路配置,这样,任何单一组件的故障都会导致服务退化,而不是完全停用。 □ 下一步和交流 * 目前不需要我们的客户采取行动。 我们致力于提供可靠和稳定的服务,我们正在采取必要步骤从这一事件中吸取教训并阻止它再次发生。 谢谢你的理解。 真诚的, 1Password团队

自动翻译自官方事件更新。

1. 2026年6月29日 UTC 22:08investigating

   试图接受SSO执行邀请的用户无法接受邀请并收到403个错误. 我们的工程组正在积极调查这个问题.

2. 2026年6月29日 UTC 22:55identified

   这一问题已经确定,我们的工程队正在努力部署一个固定装置.

3. 2026年6月29日 UTC 23:40identified

   我们的工程小组正在继续努力为这一问题部署一个解决办法。 与此同时,还确定了一个变通办法。 请与我们的支援团队联系, 联系支持@ 1password.com, 他们将通过工作步骤支持你.

4. 2026年6月30日 UTC 14:09resolved

   这一事件已经得到解决.

自动翻译自官方事件更新。

1. 2026年6月24日 UTC 17:15investigating

   一些被锁出自己1Password账户的用户在试图使用恢复代码恢复访问时遇到了"某事出错"的错误. 我们的发展团队意识到了这个问题,正在积极调查原因. 一旦获得更多信息,我们将提供最新资料.

2. 2026年6月24日 UTC 17:30investigating

   我们的小组继续调查这一问题。 我们正积极努力确定原因,并将在获得更多最新情况后分享.

3. 2026年6月24日 UTC 17:50investigating

   这个问题仍在调查之中。 我们将继续在获得最新情况后予以分享.

4. 2026年6月24日 UTC 18:32investigating

   调查仍在进行中。 我们的小组正在积极努力确定原因,并将在获得最新情况后分享.

5. 2026年6月24日 UTC 18:35identified

   这一问题已经确定,一个解决办法正在实施之中.

6. 2026年6月24日 UTC 18:51monitoring

   一项措施已经执行,我们正在监测结果.

7. 2026年6月24日 UTC 19:01resolved

   现在这个问题已经解决了,应当全面恢复1Password服务.

自动翻译自官方事件更新。

1. 2026年6月18日 UTC 17:54identified

   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.

2. 2026年6月18日 UTC 18:50resolved

   This incident has been resolved.

1. 2026年6月16日 UTC 16:24identified

   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.

2. 2026年6月16日 UTC 16:58monitoring

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

3. 2026年6月16日 UTC 21:11monitoring

   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.

4. 2026年6月17日 UTC 16:00resolved

   This incident has been resolved.

1. 2026年6月11日 UTC 21:49investigating

   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.

2. 2026年6月11日 UTC 22:02investigating

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

3. 2026年6月11日 UTC 22:17investigating

   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.

4. 2026年6月11日 UTC 22:32investigating

   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.

5. 2026年6月11日 UTC 22:47monitoring

   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.

6. 2026年6月12日 UTC 23:18resolved

   This incident has been resolved.

1. 2026年5月16日 UTC 15:51investigating

   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.

2. 2026年5月16日 UTC 17:33identified

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

3. 2026年5月16日 UTC 17:46monitoring

   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.

4. 2026年5月16日 UTC 20:36resolved

   This incident has been resolved.

1. 2026年5月4日 UTC 17:59identified

   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.

2. 2026年5月4日 UTC 18:27monitoring

   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.

3. 2026年5月4日 UTC 18:34resolved

   This incident has been resolved.

1. 2026年4月27日 UTC 14:54investigating

   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.

2. 2026年4月27日 UTC 15:08investigating

   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.

3. 2026年4月27日 UTC 15:22identified

   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.

4. 2026年4月27日 UTC 15:41monitoring

   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.

5. 2026年4月27日 UTC 17:09monitoring

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

6. 2026年4月28日 UTC 18:00resolved

   This incident has been resolved.

7. 2026年5月12日 UTC 15:38postmortem

   # 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

1. 2026年4月22日 UTC 15:18investigating

   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.

2. 2026年4月22日 UTC 15:27monitoring

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

3. 2026年4月22日 UTC 16:06resolved

   This incident has been resolved.

1. 2026年4月14日 UTC 17:25investigating

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

2. 2026年4月14日 UTC 17:46investigating

   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.

3. 2026年4月14日 UTC 18:00monitoring

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

4. 2026年4月15日 UTC 01:54resolved

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

5. 2026年5月6日 UTC 15:31postmortem

   # 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

1. 2026年4月13日 UTC 17:24monitoring

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

2. 2026年4月17日 UTC 15:07monitoring

   We are continuing to monitor for any further issues.

3. 2026年4月22日 UTC 15:17resolved

   This incident has been resolved.

1. 2026年4月1日 UTC 14:13identified

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

2. 2026年4月1日 UTC 17:52monitoring

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

3. 2026年4月2日 UTC 14:23resolved

   This incident has been resolved.