Is OpenText down?

The following services are experiencing an issue with TLS connections to Google-owned servers. Teams are currently assembled and working to resolve the issue. We appreciate your patience. - Zix Encryption Services - Hosted SMB - Zix Encryption Services - Secure Cloud Email Encryption (AEE/ZEE) - Zix Encryption Services - ZixGateway (Hosted) Tracking Number: IM3971825

The following services are experiencing an issue with TLS connections to multiple external mail services. Teams are currently assembled and working to resolve the issue. We appreciate your patience. - Zix Encryption Services - Hosted SMB - Zix Encryption Services - Secure Cloud Email Encryption (AEE/ZEE) - Zix Encryption Services - ZixGateway (Hosted) Tracking Number: IM3971825

We are continuing to investigate this issue.

The following services are experienced an issue with TLS connections to multiple external mail services. Service has been restored and is now being validated. We appreciate your patience. - Zix Encryption Services - Hosted SMB - Zix Encryption Services - Secure Cloud Email Encryption (AEE/ZEE) - Zix Encryption Services - ZixGateway (Hosted) - Zix Threat Protection Services - ZixProtect Tracking Number: IM3971825

The following services are experienced an issue with TLS connections to multiple external mail services. - Zix Encryption Services - Hosted SMB - Zix Encryption Services - Secure Cloud Email Encryption (AEE/ZEE) - Zix Encryption Services - ZixGateway (Hosted) - Zix Threat Protection Services - ZixProtect The issue is now resolved. We appreciate your patience. Tracking Number: IM3971825

São Paulo BR14 experienced performance and functionalities degradation in service. The issue is now resolved. We appreciate your patience. Tracking Number: IM3971517

**Interim Root Cause** **Tracking number:** IM3971517 PM1011702 **Incident window:** July 31, 2026, from 03:32 GMT to 04:42 GMT on July 30, 226 **Services affected:** OpenText™ Enterprise Service Management \(ESM BR14\) **Overview** On July 31, 2026, at 04:10 GMT, Incident Management was engaged to investigate degraded system performance on the OpenText™ Enterprise Service Management \(ESM BR14\) environment. **Impact** Users experienced degraded system performance and functionality issues. **Root Cause** The investigation revealed intermittent connectivity failures between the RabbitMQ cluster and dependent application components. RabbitMQ, which operates as a multi-node clustered service facilitating communication between the core application engine and other components, failed to automatically re-establish connectivity in certain instances, necessitating a cluster rebuild. The root cause analysis identified two primary contributing factors: • RabbitMQ Metadata Store Instability: An instability within the RabbitMQ Metadata store caused inconsistencies in queue metadata, resulting in messaging disruptions across the platform. • Connection Recovery Failures: Certain application services were unable to automatically re-establish stable RabbitMQ connections after failures, leading to degraded platform performance and functionality. **Resolution** The RabbitMQ service was rebuilt, restoring service at 04:24 GMT. Post-restoration validation activities were completed successfully at 04:42 GMT, ending the impact. **Action Plan** Engineering teams continue to investigate the underlying root cause of this incident and identify additional corrective and preventive measures to reduce the risk of recurrence. As part of the remediation effort, a long-term stability improvement program has been launched to enhance RabbitMQ resilience, strengthen application connection recovery mechanisms, and expand proactive monitoring and alerting capabilities. These improvements, along with enhancements planned for Release 26.3.1, are expected to further improve system stability and significantly reduce the likelihood of similar incidents in the future.

We are currently investigating reports of partners incorrectly authenticating through the Customer Portal with incorrect log ins. Our team is actively triaging this issue now. Incident: IM3969646

We have successfully initiated a rollback that caused this authentication issue and have confirmed the issue no longer is ouccring. We are continuing to actively monitor our logs to ensure everything is fully operational. Incident: IM3969646

This incident has been resolved.

Oregon US6 is currently experiencing intermittent service unavailability. Teams are currently assembled and working to resolve the issue. We appreciate your patience. Tracking Number: IM3968671

Oregon US6 is currently experiencing intermittent service unavailability. Teams are currently assembled and working to resolve the issue. We appreciate your patience. Tracking Number: IM3968671

Oregon US6 experienced intermittent service unavailability. The issue is now resolved. We appreciate your patience. Tracking Number: IM3968671

**Interim Root Cause** **Tracking number:** IM3968671 PM1011655 **Incident windows:** July 27, 2026, from 13:28 GMT to 14:15 GMT **Services affected:** OpenText™ Enterprise Service Management \(ESM US6\) **Overview** On July 27, 2026, at 14:11 GMT, Incident Management was engaged to investigate intermittent availability and performance degradation in the US6 environment. **Impact** Clients experienced degraded service performance, resulting in slow user interface \(UI\) response times. **Root Cause** The root cause analysis identified two primary contributing factors: • RabbitMQ Metadata Store Instability: An instability within the RabbitMQ Metadata store caused inconsistencies in queue metadata, resulting in messaging disruptions across the platform. • Connection Recovery Failures: Certain application services were unable to automatically re-establish stable RabbitMQ connections after failures, leading to degraded platform performance and functionality. **Resolution** The investigation revealed that insufficient replica capacity in Gateway and Platform services was impacting service performance. The number of replicas for both services was increased, and the service was restored. Full validation was completed by 14:15 GMT, ending the impact. **Action Plan** Engineering teams continue to investigate the underlying root cause of this incident and identify additional corrective and preventive measures to reduce the risk of recurrence. As part of the remediation effort, a long-term stability improvement program has been launched to enhance RabbitMQ resilience, strengthen application connection recovery mechanisms, and expand proactive monitoring and alerting capabilities. These improvements, along with enhancements planned for Release 26.3.1, are expected to further improve system stability and significantly reduce the likelihood of similar incidents in the future. OpenText took the following actions and will determine additional preventative actions as needed. ‌ • Implemented static pod assignment for RabbitMQ, replacing dynamic allocation to reduce the risk of pod contention. - **COMPLETE** • Increased CPU resources allocated to RabbitMQ pods to alleviate performance bottlenecks and improve overall system stability. - **COMPLETE**

Frankfurt EU8 is currently experiencing intermittent service unavailability. Teams are currently assembled and working to resolve the issue. We appreciate your patience. Tracking Number: IM3968415

Frankfurt EU8 experienced intermittent service unavailability. Service has been restored and is now being validated. We appreciate your patience. Tracking Number: IM3968415

Frankfurt EU8 experienced intermittent service unavailability. Service has been restored and is now being validated. We appreciate your patience. Tracking Number: IM3968415

Frankfurt EU8 experienced intermittent service unavailability. The issue is now resolved. We appreciate your patience. Tracking Number: IM3968415

**Interim Root Cause** **Tracking number:** IM3968415 PM1011655 **Incident windows:** July 27, 2026, from 06:31 GMT to 09:41 GMT **Services affected:** OpenText™ Enterprise Service Management \(ESM EU8\) **Overview** On July 27, 2026, at 07:10 GMT, Incident Management was engaged to investigate intermittent access issues and service unavailability. **Impact** Several clients experienced intermittent access issues and service unavailability across the ESM EU8 environment. **Root Cause** The root cause analysis identified two primary contributing factors: • RabbitMQ Metadata Store Instability: An instability within the RabbitMQ Metadata store caused inconsistencies in queue metadata, resulting in messaging disruptions across the platform. • Connection Recovery Failures: Certain application services were unable to automatically re-establish stable RabbitMQ connections after failures, leading to degraded platform performance and functionality. **Resolution** The CPU allocation was increased, and the RabbitMQ queues were rebalanced to improve system stability and performance. Systematic restarts of the platform pods were completed at 07:56 GMT, which restored the core services. However, the SLT service continued to experience issues. The cluster was rebuilt, and services normalized at 09:41 GMT. Additional manual checks were completed across the environment to clear false degradation alerts, and no further issues were observed. Validations were completed at 11:38 GMT, ending the impact. **Action Plan** Engineering teams continue to investigate the underlying root cause of this incident and identify additional corrective and preventive measures to reduce the risk of recurrence. As part of the remediation effort, a long-term stability improvement program has been launched to enhance RabbitMQ resilience, strengthen application connection recovery mechanisms, and expand proactive monitoring and alerting capabilities. These improvements, along with enhancements planned for Release 26.3.1, are expected to further improve system stability and significantly reduce the likelihood of similar incidents in the future. OpenText took the following actions and will determine additional preventative actions as needed. ‌ • Implemented static pod assignment for RabbitMQ, replacing dynamic allocation to reduce the risk of pod contention. - **COMPLETE** • Increased CPU resources allocated to RabbitMQ pods to alleviate performance bottlenecks and improve overall system stability. - **COMPLETE**