Webroot 中断历史

1. 2026年9月9日 UTC 07:49investigating

   Frankfurt EU8 is currently experiencing service degradation with UCMDB service on EU8 farm. Clients may experience degradation while loading request entities or using an actual service on the EU8 farm. Teams are currently assembled and working to resolve the issue. We appreciate your patience. Tracking Number: IM3995249

2. 2026年9月9日 UTC 08:13resolved

   Frankfurt EU8 experienced service degradation with UCMDB service on EU8 farm. The issue is now resolved. We appreciate your patience. Tracking Number: IM3995249

1. 2026年8月31日 UTC 16:33investigating

   Microsoft O365 Exchange - some users are experiencing an issue connecting to Exchange 365. Microsoft is aware of the issue and has provided Issue ID: EX1464935.

2. 2026年8月31日 UTC 16:57investigating

   Update from Microsoft: Microsoft isolated a common failure pattern across affected Exchange Online requests that is associated with authentication and protocol connectivity. They are analyzing service telemetry to identify the underlying source of impact and validate potential remediation options. Additionally, they are continuing to assess the scope of impact and monitor for additional affected scenarios. More info - Users may experience a variety of symptoms related to this event, including but not limited to: Delays or failures when sending or receiving email messages. Authentication-related errors when accessing Exchange Online services. Difficulties accessing or performing actions within Exchange administration experiences. Intermittent failures affecting mailbox operations and message delivery workflows.

3. 2026年8月31日 UTC 17:51investigating

   Update from Microsoft: Microsoft has identified a potential corrective action for the affected infrastructure and are evaluating deployment options. They are monitoring service telemetry and affected Exchange Online transactions to determine whether the action is reducing impact and to better understand the scope of affected scenarios.

4. 2026年8月31日 UTC 20:14investigating

   Update from Microsoft: Microsoft is continuing to perform comprehensive tests to ensure their mitigation strategy effectively resolves the issue without introducing additional impact. In parallel, they are exploring alternative remediation avenues to minimize impact in the interim.

5. 2026年9月1日 UTC 12:26identified

   Update from Microsoft: A substantial portion of the remediation deployment has been completed, and organizations whose environments remain affected are expected to recover as the deployment reaches the relevant infrastructure. As remediation progresses, Microsoft is focused on validating sustained recovery and monitoring for any remaining pockets of impact before determining whether any additional corrective actions are required.

6. 2026年9月1日 UTC 17:07monitoring

   Update from Microsoft: Microsoft observed continued recovery across previously impacted Exchange Online scenarios, with core mail flow functionality remaining healthy. Their focus remains on validating recovery across dependent Microsoft 365 experiences and confirming that remaining impact scenarios are fully addressed. They are maintaining enhanced monitoring while engineering teams complete end-to-end validation before determining whether any further corrective actions are required.

7. 2026年9月1日 UTC 21:57monitoring

   Update from Microsoft: Microsoft continues to advance multiple workstreams to restore service and prevent additional impact. Microsoft is prioritizing infrastructure that requires the most immediate attention while carefully expanding corrective actions across additional regions, with continued monitoring throughout this process. In parallel, Microsoft is investigating remaining reports of impact and evaluating additional actions to support full service recovery.

8. 2026年9月2日 UTC 12:18monitoring

   Update from Microsoft: Their telemetry indicates service availability remains stable above 99 percent and expect the majority of users should no longer be seeing impact from this issue. The continued focus is on balancing the implementation of their fixes across remaining portions of affected infrastructure to ensure persistent recovery, with added attention on ensuring withstanding recovery of scenarios dependent on REST and Graph API connection methods.

9. 2026年9月3日 UTC 16:45monitoring

   Update from Microsoft: Microsoft discovered an issue in less than one percent of their infrastructure, where additional mitigation efforts to resolve impact for Exchange Online did not successfully deploy. The vast majority of impact remains remediated; however, those serviced from the impacted portion of infrastructure may be unable to access previously recovered Outlook connection methods. Microsoft remains committed to restoring all services to all users and will continue to carefully monitor their telemetry to ensure recovery.

10. 2026年9月3日 UTC 18:33monitoring

    Update from Microsoft: All user impact scenarios are now resolved as they rectified the additional mitigation efforts for the Outlook impact which occurred in less than one percent of their infrastructure. They will continue to monitor their telemetry to ensure all services remain healthy and plan to close this communication by next update.

11. 2026年9月4日 UTC 12:22resolved

    This incident has been resolved.

1. 2026年8月28日 UTC 17:16investigating

   Desktop Messaging BMS is currently experiencing delays in processing outbound fax delivery. Document backlogs exist and are currently being processed. Teams are currently assembled and working to resolve the issue. We appreciate your patience. Tracking Number: IM3987893

2. 2026年8月28日 UTC 17:58resolved

   Desktop Messaging BMS experienced delays in processing outbound fax delivery. Backlogs have been cleared, and the issue is now resolved. We appreciate your patience. Tracking Number: IM3987893

1. 2026年8月28日 UTC 02:42investigating

   Core Communications Europe is currently unavailable. Teams are currently assembled and working to resolve the issue. We appreciate your patience. Tracking Number: IM3987509

2. 2026年8月28日 UTC 03:13monitoring

   Core Communications Europe was unavailable. Teams are currently assembled and working to resolve the issue. Service has been restored and is being validated. We appreciate your patience. Tracking Number: IM3987509

3. 2026年8月28日 UTC 03:24resolved

   Core Communications Europe was unavailable. The issue is now resolved. We appreciate your patience. Tracking Number: IM3987509

1. 2026年8月26日 UTC 14:12investigating

   MailStore Cloud is currently unavailable. Teams are currently assembled and working to resolve the issue. We appreciate your patience.

2. 2026年8月26日 UTC 15:05monitoring

   MailStore Cloud was unavailable. Service has been restored and is being validated. We appreciate your patience.

3. 2026年8月26日 UTC 15:57resolved

   MailStore Cloud was unavailable. The issue is now resolved. We appreciate your patience.

1. 2026年8月22日 UTC 03:41investigating

   Core EDR/MDR in the US region is currently experiencing service degradation. Teams are currently assembled and working to resolve the issue. We appreciate your patience.

2. 2026年8月22日 UTC 04:41investigating

   Core EDR/MDR in the US region is currently experiencing service degradation. Teams are currently assembled and working to resolve the issue. We appreciate your patience. Updates for this issue will be sent every 2 hours or if there are significant updates, whichever comes first.

3. 2026年8月22日 UTC 06:41investigating

   Core EDR/MDR in the US region is currently experiencing service degradation. Teams are currently assembled and working to resolve the issue. We appreciate your patience. Updates for this issue will be posted as soon as there are significant updates.

4. 2026年8月24日 UTC 13:18resolved

   Core EDR/MDR in the US region experienced service degradation. The issue has been resolved. We appreciate your patience.

1. 2026年8月20日 UTC 15:54identified

   Core EDR/MDR is currently experiencing service degradation. Agents that were upgraded to version 3.3.0 from an earlier version may experience issues preventing remote uninstallations from completing successfully. New installations of version 3.3.0 are not impacted. Teams have identified that the issue only affects the Windows OS and are working to resolve it. We appreciate your patience. If agent removal is required, please follow the steps outlined in our Knowledge Base article for manual agent uninstallation, which remains effective for affected endpoints: https://help.pillrplatform.com/faq/uninstall.html

2. 2026年8月20日 UTC 17:55identified

   Core EDR/MDR is currently experiencing service degradation. Agents that were upgraded to version 3.3.0 from an earlier version may experience issues preventing remote uninstallations from completing successfully. New installations of version 3.3.0 are not impacted. Teams have identified that the issue affects only the Windows OS and are working to resolve it. We appreciate your patience. If agent removal is required, please follow the steps outlined in our Knowledge Base article for manual agent uninstallation, which remains effective for affected endpoints: https://help.pillrplatform.com/faq/uninstall.html

3. 2026年8月20日 UTC 22:58identified

   Core EDR/MDR is currently experiencing service degradation. Agents that were upgraded to version 3.3.0 from an earlier version may experience issues preventing remote uninstallations from completing successfully. New installations of version 3.3.0 are not impacted. Teams have identified that the issue affects only the Windows OS and are working to resolve it. If agent removal is required, please follow the steps outlined in our Knowledge Base article for manual agent uninstallation, which remains effective for affected endpoints: https://help.pillrplatform.com/faq/uninstall.html Updates for this issue will be sent every 2 hours or if there are significant updates, whichever comes first. We appreciate your patience.

4. 2026年8月20日 UTC 23:42monitoring

   Core EDR/MDR experienced service degradation. Service has been restored in agent version 3.3.2, which is now GA. For customers still on version 3.3.0, a manual upgrade can be triggered through the Action System before proceeding with the uninstall.

5. 2026年8月21日 UTC 01:45resolved

   Core EDR/MDR experienced service degradation. The issue is now resolved. We appreciate your patience.

1. 2026年8月13日 UTC 18:36investigating

   Secure Cloud Portal is currently experiencing an issue with Microsoft 365 license assignments. Our teams are actively investigating and working to restore normal functionality as quickly as possible. We appreciate your patience and understanding while we work toward a resolution. Workaround: After updating license counts in the Secure Cloud Portal, please sign in to the customer's Microsoft 365 Admin Center and assign licenses to users directly within the Microsoft 365 tenant. Tracking Number: IM3979306

2. 2026年8月14日 UTC 16:24resolved

   This incident has been resolved.

1. 2026年8月13日 UTC 15:09investigating

   Cloud Fax services is currently experiencing delays in processing of fax files. Teams are currently assembled and working to resolve the issue. We appreciate your patience. Desktop Messaging BMS Tracking Number: IM3978817

2. 2026年8月13日 UTC 16:15investigating

   Desktop Messaging BMS is experiencing delays in processing fax files. Teams are currently assembled and working to resolve the issue. We appreciate your patience. Tracking Number: IM3978817

3. 2026年8月13日 UTC 17:02resolved

   Desktop Messaging BMS experienced delays in processing fax files. The issue is now resolved. We appreciate your patience. Tracking Number: IM3978817

1. 2026年8月9日 UTC 09:06investigating

   Enterprise Service Management hosted under the saas.microfocus.com domain may currently experience issues accessing their applications. Teams are assembled and working to resolve the issue. We appreciate your patience Tracking Number: IM3976323

2. 2026年8月9日 UTC 09:06investigating

   We are continuing to investigate this issue.

3. 2026年8月9日 UTC 10:13investigating

   Enterprise Service Management hosted under the saas.microfocus.com domain may currently experience issues accessing their applications. Teams are assembled and working to resolve the issue. We appreciate your patience. Updates for this issue will be sent every 2 hours or if there are significant updates, whichever comes first Tracking Number: IM3976323

4. 2026年8月9日 UTC 12:17monitoring

   Enterprise Service Management hosted under the saas.microfocus.com domain may currently experience issues accessing their applications. A fix has been implemented and we are monitoring the results. We appreciate your patience. Tracking Number: IM3976323

5. 2026年8月9日 UTC 14:34monitoring

   Enterprise Service Management hosted under the saas.microfocus.com domain may currently experience issues accessing their applications. A fix has been implemented, and we are monitoring the results. We appreciate your patience. Updates for this issue will be sent every 2 hours or if there are significant updates, whichever comes first. Tracking Number: IM3976323

6. 2026年8月10日 UTC 00:33monitoring

   Enterprise Service Management hosted under the saas.microfocus.com domain might have experienced issues accessing their applications. A fix has been implemented, and we are monitoring the results. We appreciate your patience. Updates for this issue will be sent every 8 hours or if there are significant updates, whichever comes first. Tracking Number: IM3976323

7. 2026年8月10日 UTC 01:17resolved

   Enterprise Service Management hosted under the saas.microfocus.com domain might have experienced issues accessing their applications. The issue is now resolved. We appreciate your patience. Tracking Number: IM3976323

8. 2026年8月13日 UTC 19:01postmortem

   **Root Cause Analysis** **Tracking number:** IM3976323 PM1011709 **Incident window:** August 9, 2026, from 01:00 GMT to 11:35 GMT **Services affected:** OpenText™ Shared Network Services **Overview** On August 9, 2026, at 06:24 GMT, Incident Management was engaged to investigate client-reported access issues affecting multiple OpenText SaaS services. **Impact** Clients were unable to access the OpenText SaaS services. **Root Cause** The investigation determined that a Domain Name System Security Extensions \(DNSSEC\) Key Signing Key \(KSK\) expired for the [microfocus.com](http://microfocus.com) DNS zone, resulting in DNS resolution failures across multiple services. This condition disrupted DNS resolution across multiple DNSSEC-enabled subzones, including [saas.microfocus.com](http://saas.microfocus.com), resulting in service inaccessibility. Furthermore, downstream propagation timelines and varying client-side caching behaviors extended recovery durations for a subset of endpoints. **Resolution** To mitigate the issue, the team implemented a configuration change to generate and apply new DNSSEC signing keys. The existing DNS signatures were removed, and the [microfocus.com](http://microfocus.com) DNS zone was re-signed using the newly generated keys. Following the configuration change, validation activities were completed successfully, and service was restored at 11:35 GMT, ending the impact. Note: Some clients may have continued to experience name-resolution issues due to stale DNS records cached within their internal DNS infrastructure, proxy servers, or firewall appliances. These issues should resolve once the cached DNS records expired or refreshed. **Action Plan** PM1011709-003: Review and optimize DNSSEC KSK alert triggers. - In progress - Target complete: August 14, 2026 PM1011709-004: Implement proactive internal monitoring and automated alert generation for DNSSEC key rollovers. - In progress - Target complete: September 4, 2026 PM1011709-006: Review incident escalation procedures to optimize the process. - In progress - Target complete: September 4, 2026 PM1011709-007: Evaluate external accessibility monitoring capabilities for critical application endpoints. - In progress - Target complete: September 4, 2026

1. 2026年8月8日 UTC 15:05investigating

   Investigating: We are currently experiencing an issue in the CP Portal where users may encounter an "Unknown Error" message. Our Engineering team is actively investigating the issue and working toward a resolution. We will provide further updates as more information becomes available. Tracking Number - IM3976014

2. 2026年8月8日 UTC 20:03monitoring

   The issue affecting the CP Portal, where users may have encountered an "Unknown Error" message, has been identified and resolved by our Backend Engineering team. The fix has been successfully implemented, and services are operating as expected. We are currently monitoring the environment to ensure stability and confirm that the issue does not recur. We will continue to provide updates as needed. Tracking Number - IM3976014

3. 2026年8月10日 UTC 12:58resolved

   The issue affecting the CP Portal, where users may have encountered an "Unknown Error" message, has been identified and resolved by our Backend Engineering team. The fix has been successfully implemented, and services are now operating as expected. Tracking Number - IM3976014

1. 2026年8月7日 UTC 17:59investigating

   Secure Cloud Portal (cp.appriver.com) is currently experiencing an issue with Microsoft 365 license changes. Teams are currently assembled and working to resolve the issue. We appreciate your patience. If you need any 365 license changes, please email [email protected] to create a ticket for processing. Tracking Number: IM397569

2. 2026年8月7日 UTC 20:14monitoring

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

3. 2026年8月13日 UTC 18:25resolved

   This incident has been resolved.

1. 2026年8月6日 UTC 17:18investigating

   Zix Encryption Services - Secure Cloud Email Encryption AEE DLP is currently experiencing an issue requiring the sender of an email to log in to an interface to release messages from DLP. Teams are currently assembled and working to resolve the issue. We appreciate your patience. Tracking Number: IM3975128

2. 2026年8月6日 UTC 21:14monitoring

   Zix Encryption Services - Secure Cloud Email Encryption AEE DLP experienced an issue requiring the sender of an email to log in to an interface to release messages from DLP. Service has been restored and is now being validated. We appreciate your patience. Tracking Number: IM3975128

3. 2026年8月7日 UTC 12:56resolved

   Zix Encryption Services - Secure Cloud Email Encryption AEE DLP experienced an issue requiring the sender of an email to log in to an interface to release messages from DLP. The issue is now resolved. We appreciate your patience. Tracking Number: IM3975128

1. 2026年8月3日 UTC 22:28identified

   核心紧急救灾方案/紧急救灾方案目前正在出现服务退化。 代理安装器下载可能无法如预期的那样工作 。 各小组已查明原因,并正在拟订解决办法。 我们感谢你的耐心。 如果您有任何问题或担心,请联系支助小组.

2. 2026年8月3日 UTC 23:28identified

   核心紧急救灾方案/紧急救灾方案目前正在出现服务退化。 代理安装器下载可能无法如预期的那样工作 。 各小组已查明原因,并正在拟订解决办法。 我们感谢你的耐心。 这个问题的更新将每2小时发送一次,或者如果有重大更新,以时间在先者为准。 如果您有任何问题或担心,请联系支助小组.

3. 2026年8月4日 UTC 00:54monitoring

   中央经发司/经发司经历了服务退化。 服务已经恢复,目前正在验证。 我们感谢你的耐心。 这个问题的更新将每2小时发送一次,或者如果有重大更新,以时间在先者为准。 如果您有任何问题或担心,请联系支助小组.

4. 2026年8月4日 UTC 02:51resolved

   中央经发司/经发司经历了服务退化。 这个问题现已解决。 我们感谢你的耐心.

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

1. 2026年7月31日 UTC 14:29investigating

   以下服务正面临TLS连接到Google自有服务器的问题. 各小组目前正在集结并努力解决这一问题。 我们感谢你的耐心。 - Zix加密服务 - 主机SMB - Zix加密服务 - 安全云电子邮件加密(AEE/ZEE) - Zix加密服务 - ZixGateway(Hosted) 追踪号码:IM3971825

2. 2026年7月31日 UTC 14:37investigating

   以下服务遇到一个问题: TLS 连接到多个外部邮件服务. 各小组目前正在集结并努力解决这一问题。 我们感谢你的耐心。 - Zix加密服务 - 主机SMB - Zix加密服务 - 安全云电子邮件加密(AEE/ZEE) - Zix加密服务 - ZixGateway(Hosted) 追踪号码:IM3971825

3. 2026年7月31日 UTC 14:45investigating

   以下服务遇到一个问题: TLS 连接到多个外部邮件服务. 各小组目前正在集结并努力解决这一问题。 我们感谢你的耐心。 - Zix加密服务 - 主机SMB - Zix加密服务 - 安全云电子邮件加密(AEE/ZEE) - Zix加密服务 - ZixGateway(Hosted) - Zix威胁保护服务 追踪号码:IM3971825

4. 2026年7月31日 UTC 14:57monitoring

   以下服务遇到一个问题: TLS连接多个外部邮件服务. 服务已经恢复,目前正在验证。 我们感谢你的耐心。 - Zix加密服务 - 主机SMB - Zix加密服务 - 安全云电子邮件加密(AEE/ZEE) - Zix加密服务 - ZixGateway(Hosted) - Zix威胁保护服务 追踪号码:IM3971825

5. 2026年7月31日 UTC 17:35resolved

   以下服务遇到一个问题: TLS连接多个外部邮件服务. - Zix加密服务 - 主机SMB - Zix加密服务 - 安全云电子邮件加密(AEE/ZEE) - Zix加密服务 - ZixGateway(Hosted) - Zix威胁保护服务 这个问题现已解决。 我们感谢你的耐心。 追踪号码:IM3971825

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

1. 2026年7月31日 UTC 04:43resolved

   圣保罗BR14在服务中经历了性能和功能退化. 这个问题现已解决。 我们感谢你的耐心。 追踪编号:IM3971517

2. 2026年7月31日 UTC 13:47postmortem

   ** 临时根源** ** 追踪号码:** IM3971517 PM 1011702 (英语). ** 事件窗口:** 2026年7月31日,从格林尼治平时03:32到格林尼治平时04:42,226年7月30日 ** 受影响的服务:** OpenTextTM 企业服务管理\(ESM BR14\) ** 概览** 2026年7月31日格林尼治平时04:10分,事件管理公司参与调查OpenTextTM Entertainment Service Management\(ESM BR14\)环境中的退化系统性能. ** 影响** 用户经历了系统性能退化和功能问题。 ** 循环原因** 调查显示,RabbitMQ集群与依赖性应用组件之间断断续续的连接失败. RabbitMQ作为一个多节点集群服务运行,促进核心应用引擎和其他组件之间的通信,它在某些情况下未能自动重建连接,因此需要集群重建. 根源分析确定了两个主要因素: • RabbitMQ元数据存储不稳定性:RabbitMQ元数据存储内部的不稳定导致队列元数据不一致,导致整个平台的短信中断。 • 连接恢复失败:某些应用程序服务在失败后无法自动重建稳定的兔子MQ连接,导致平台性能和功能退化. ** 决议** 兔MQ服务被重建,于格林尼治平时04:24恢复服务. 恢复后验证活动于格林尼治平时04:42顺利完成,结束了影响. ** 行动计划** 工程小组继续调查这一事件的根本原因,并找出更多的纠正和预防措施来减少再次发生的风险。 作为整治工作的一部分,启动了长期稳定改善方案,以提高兔子MQ的复原力,加强应用连接恢复机制,并扩展主动监测和警报能力。 这些改进以及计划为第26.3.1版进行的改进,预计会进一步提高系统稳定性并大大减少今后发生类似事件的可能性.

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

1. 2026年7月28日 UTC 17:31identified

   我们目前正在调查有关合作伙伴通过客户端进行不正确认证的报告。 我们的团队正在积极研究这个问题。 事件:IM3969646

2. 2026年7月28日 UTC 17:38monitoring

   我们已成功地发起回滚,造成这一认证问题,并证实这一问题已不复存在。 我们继续积极监测我们的日志,以确保所有记录都充分运作。 事件:IM3969646

3. 2026年7月29日 UTC 17:38resolved

   这一事件已经得到解决.

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

1. 2026年7月27日 UTC 15:22investigating

   俄勒冈州US6目前出现间歇性服务无法提供的情况. 各小组目前正在集结并努力解决这一问题。 我们感谢你的耐心。 追踪编号: IM3968671

2. 2026年7月27日 UTC 15:54resolved

   俄勒冈州美国6号遭遇断断续续的服务无法提供. 这个问题现已解决。 我们感谢你的耐心。 追踪编号: IM3968671

3. 2026年7月29日 UTC 17:30postmortem

   ** 临时根源** ** 追踪号码:** IM3968671 PM 1011655 (英语). ** 事件窗口:** 2026年7月27日,格林尼治标准时13:28至格林尼治标准时14:15 ** 受影响的服务:** OpenTextTM 企业服务管理\(ESM US6\) ** 概览** 2026年7月27日格林尼治平时14:11分,事件管理公司参与调查美国6号环境的间歇性可用性和性能退化. ** 影响** 客户端经历了服务性能的退化,导致用户界面\(UI\)响应时间缓慢. ** 循环原因** 根源分析确定了两个主要因素: • RabbitMQ元数据存储不稳定性:RabbitMQ元数据存储内部的不稳定导致队列元数据不一致,导致整个平台的短信中断。 • 连接恢复失败:某些应用程序服务在失败后无法自动重建稳定的兔子MQ连接,导致平台性能和功能退化. ** 决议** 调查显示,Gateway和平台服务的复制能力不足,影响了服务业绩。 两种服务的复制品数量增加,服务得到恢复. 格林尼治平时14:15完成全面验证,结束了撞击. ** 行动计划** 工程小组继续调查这一事件的根本原因,并找出更多的纠正和预防措施来减少再次发生的风险。 作为整治工作的一部分,启动了长期稳定改善方案,以提高兔子MQ的复原力,加强应用连接恢复机制,并扩展主动监测和警报能力。 这些改进以及计划为第26.3.1版进行的改进,预计会进一步提高系统稳定性并大大减少今后发生类似事件的可能性。 OpenText采取了以下行动,并将根据需要确定额外的预防行动. • 执行RabbitMQ的静态吊舱任务,取代动态分配以减少吊舱出错的风险。 - ** 委员会** · 增加分配给RabbitMQ舱的CPU资源,以缓解性能瓶颈,并改进总体系统稳定性。 - ** 委员会**

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

1. 2026年7月27日 UTC 09:03investigating

   欧盟8国法兰克福目前时断时续地得不到服务。 各小组目前正在集结并努力解决这一问题。 我们感谢你的耐心。 追踪编号:IM3968415

2. 2026年7月27日 UTC 10:54monitoring

   法兰克福欧盟八国出现断断续续的服务无法提供. 服务已经恢复,目前正在验证。 我们感谢你的耐心。 追踪编号:IM3968415

3. 2026年7月27日 UTC 11:42resolved

   法兰克福欧盟八国出现断断续续的服务无法提供. 这个问题现已解决。 我们感谢你的耐心。 追踪编号:IM3968415

4. 2026年7月29日 UTC 14:26postmortem

   ** 临时根源** ** 追踪号码:** IM3968415 PM 1011655 (英语). ** 事件窗口:** 2026年7月27日,格林尼治平时06:31至09:41 ** 受影响的服务:** OpenTextTM 企业服务管理\(ESM EU8\) ** 概览** 2026年7月27日格林尼治平时07:10分,事件管理公司参与调查断断续续的接入问题和服务缺乏情况. ** 影响** 若干客户在欧盟8国无害环境管理环境中经历了间歇性准入问题和服务缺乏问题。 ** 循环原因** 根源分析确定了两个主要因素: • RabbitMQ元数据存储不稳定性:RabbitMQ元数据存储内部的不稳定导致队列元数据不一致,导致整个平台的短信中断。 • 连接恢复失败:某些应用程序服务在失败后无法自动重建稳定的兔子MQ连接,导致平台性能和功能退化. ** 决议** CPU分配增加,并重新平衡了RabbitMQ队列以提高系统稳定性和性能. 平台吊舱的系统重启工作于格林尼治平时07:56完成,恢复了核心服务. 然而,SLT服务继续遇到问题。 集群重建,服务于格林尼治平时9:41恢复正常. 在整个环境中完成了额外的人工检查,以清除虚假的降解警报,没有观察到其他问题。 格林尼治平时11:38完成验证,结束了撞击. ** 行动计划** 工程小组继续调查这一事件的根本原因,并找出更多的纠正和预防措施来减少再次发生的风险。 作为整治工作的一部分,启动了长期稳定改善方案,以提高兔子MQ的复原力,加强应用连接恢复机制,并扩展主动监测和警报能力。 这些改进以及计划为第26.3.1版进行的改进,预计会进一步提高系统稳定性并大大减少今后发生类似事件的可能性。 OpenText采取了以下行动,并将根据需要确定额外的预防行动. • 执行RabbitMQ的静态吊舱任务,取代动态分配以减少吊舱出错的风险。 - ** 委员会** · 增加分配给RabbitMQ舱的CPU资源,以缓解性能瓶颈,并改进总体系统稳定性。 - ** 委员会**

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

1. 2026年7月27日 UTC 07:17investigating

   欧盟8国法兰克福目前时断时续地得不到服务。 各小组目前正在集结并努力解决这一问题。 我们感谢你的耐心。 追踪编号:IM3968415

2. 2026年7月27日 UTC 08:19resolved

   欧盟8国法兰克福目前时断时续地得不到服务。 各小组目前正在集结并努力解决这一问题。 我们感谢你的耐心。 追踪编号:IM3968415

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