OpenText Outage History

Started Jul 09, 2026, 03:20 PM UTC· resolved Jul 13, 2026, 12:34 PM UTC

1. investigating Jul 09, 2026, 03:20 PM UTC

   Zix - Hosted Exchange is currently receiving reports of slowness accessing email via OWA and Outlook desktop. Teams are currently assembled and working to investigate the issue. We appreciate your patience. Tracking Number: Pending

2. investigating Jul 09, 2026, 07:07 PM UTC

   Investigating - Zix Hosted Exchange teams continue to investigate reports of intermittent slowness when accessing email through OWA and Outlook desktop. No server-side issues have been identified at this time, and the investigation remains ongoing. We appreciate your patience and will provide further updates as information becomes available. Tracking Number: IM3958701

3. monitoring Jul 10, 2026, 12:19 PM UTC

   Monitoring - Zix Hosted Exchange - Our teams have not identified any service-side issues at this time and will continue to closely monitor the environment for any further reports or signs of impact. Tracking Number: IM3958701

4. resolved Jul 13, 2026, 12:34 PM UTC

   Zix - Hosted Exchange - Our teams have not identified any service-side issues at this time and will continue to closely monitor the environment for any further reports or signs of impact. Tracking Number: IM3958701

Read the full incident report →

Started Jul 07, 2026, 04:19 PM UTC· resolved Jul 07, 2026, 08:13 PM UTC

1. investigating Jul 07, 2026, 04:19 PM UTC

   Zix Encryption Services - Email Message Privacy (EMP) portals and plugins are currently experiencing an issue. Teams are currently assembled and working to resolve the issue. We appreciate your patience. Tracking Number: IM3957099

2. resolved Jul 07, 2026, 08:13 PM UTC

   Zix Encryption Services - Email Message Privacy (EMP) portals and plugins experienced an issue with availability. The issue is now resolved. We appreciate your patience. Tracking Number: IM3957099

Read the full incident report →

Started Jul 07, 2026, 03:42 PM UTC· resolved Jul 07, 2026, 06:20 PM UTC

1. investigating Jul 07, 2026, 03:42 PM UTC

   Server Backup US East (Boyers) is currently experiencing login issues with the Iron Mountain portal. Teams are currently assembled and working to resolve the issue. We appreciate your patience. Tracking Number: IM3957043

2. investigating Jul 07, 2026, 04:42 PM UTC

   Server Backup US East (Boyers) is currently experiencing login issues with the Iron Mountain portal. Teams are currently assembled and working to resolve the issue. We appreciate your patience. Tracking Number: IM3957043

3. investigating Jul 07, 2026, 05:40 PM UTC

   Server Backup US East (Boyers) is currently experiencing login issues with the Iron Mountain portal. 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. Tracking Number: IM3957043

4. resolved Jul 07, 2026, 06:20 PM UTC

   Server Backup US East (Boyers) experienced login issues with the Iron Mountain portal. The issue is now resolved. We appreciate your patience. Tracking Number: IM3957043

Read the full incident report →

Started Jul 03, 2026, 03:09 PM UTC· resolved Jul 03, 2026, 04:19 PM UTC

1. investigating Jul 03, 2026, 03:09 PM UTC

   OCP North America is in a degraded state. The following applications are impacted and customers may feel degraded performance: - Core Content Management (corecontent.us.opentext.com) - Core Content Management for SAP® SuccessFactors

2. monitoring Jul 03, 2026, 04:04 PM UTC

   OCP North America was in a degraded state. The following applications were impacted, and customers may have experienced degraded performance. Service has been restored and is now being validated. We appreciate your patience. - Core Content Management (corecontent.us.opentext.com) - Core Content Management for SAP® SuccessFactors - Core Platform - Metadata (cms.us.opentext.com) Tracking Number: IM3955195

3. resolved Jul 03, 2026, 04:19 PM UTC

   OCP North America was in a degraded state. The following applications were impacted, and customers may have experienced degraded performance. The issue is now resolved. We appreciate your patience. - Core Content Management (corecontent.us.opentext.com) - Core Content Management for SAP® SuccessFactors - Core Platform - Metadata (cms.us.opentext.com) Tracking Number: IM3955195

Read the full incident report →

Started Jun 30, 2026, 11:07 AM UTC· resolved Jul 01, 2026, 01:35 PM UTC

1. investigating Jun 30, 2026, 11:07 AM UTC

   Zix - Hosted Exchange (HEX) - Our engineering team is currently investigating new reports of Outlook connection issues in the EMEA region. Teams are currently assembled and working to resolve the issue. We appreciate your patience. Tracking Number: IM3953059

2. monitoring Jun 30, 2026, 12:25 PM UTC

   We have deployed a fix that has resolved the issue. The team is continuing to monitor the system closely to ensure everything remains stable. Tracking Number: IM3953059

3. resolved Jul 01, 2026, 01:35 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Jun 29, 2026, 05:57 PM UTC· resolved Jun 29, 2026, 05:57 PM UTC

1. resolved Jun 29, 2026, 05:57 PM UTC

   Core EDR/MDR experienced an issue. The Detection & Response portal was temporarily unavailable earlier today. The issue is now resolved. We appreciate your patience. If you have any questions or concerns, please reach out to the Support Team.

Read the full incident report →

Started Jun 29, 2026, 01:35 PM UTC· resolved Jun 30, 2026, 11:11 AM UTC

1. investigating Jun 29, 2026, 01:35 PM UTC

   Zix - Hosted Exchange (HEX) - Our engineering team is currently investigating reports of Outlook connection issues in the EMEA region. Teams are currently assembled and working to resolve the issue. We appreciate your patience. Tracking Number: IM3952482

2. investigating Jun 29, 2026, 02:44 PM UTC

   Zix - Hosted Exchange (HEX) is currently experiencing an issue with Outlook connections in EMEA region. Teams are currently assembled and working to resolve the issue. We appreciate your patience. Tracking Number: IM3952482

3. monitoring Jun 29, 2026, 07:56 PM UTC

   Zix - Hosted Exchange experienced an issue with Outlook connections in the EMEA region. We are starting to receive reports of mailboxes successfully reconnected again. We are continuing to monitor the service. We appreciate your patience. Tracking Number: IM3952482

4. resolved Jun 30, 2026, 11:11 AM UTC

   Tracking Number: IM3952482 - Users confirmed yesterday that they are now able to connect to Outlook.

Read the full incident report →

Started Jun 29, 2026, 07:01 AM UTC· resolved Jun 29, 2026, 08:30 AM UTC

1. resolved Jun 29, 2026, 07:01 AM UTC

   Core Compliance in OCP US was not available from 6/29/2026 04:53 GMT to 06:53 GMT. During the outage policy enforcement across customer information was not functioning. Teams were engaged and the issue was resolved by adjusting the configuration of the backend database. Ref: IM3952401

Read the full incident report →

Started Jun 28, 2026, 02:20 AM UTC· resolved Jun 30, 2026, 10:58 AM UTC

1. investigating Jun 28, 2026, 02:20 AM UTC

   We are currently investigating an issue where some users are experiencing HEX mailbox delivery problems. IM3952049

2. investigating Jun 28, 2026, 12:44 PM UTC

   IM3952049 - We are continuing to investigate the issue. While some mitigation steps have been attempted, the root cause has not yet been identified. Our engineering team is actively working on this and we will provide further updates as we have more information.

3. monitoring Jun 29, 2026, 08:10 AM UTC

   We have deployed a fix that has resolved the issue. The team is continuing to monitor the system closely to ensure everything remains stable. IM3952049

4. resolved Jun 30, 2026, 10:58 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Jun 26, 2026, 03:54 PM UTC· resolved Jul 23, 2026, 11:43 AM UTC

1. investigating Jun 26, 2026, 03:54 PM UTC

   The following services are experiencing a potential service degradation. Services that can be failed over to our alternate site will be failed over to avoid impact. Teams are currently assembled and working to resolve the issue. We appreciate your patience. - Desktop Messaging BMS - Fax Cloud Connect (RightFax) - Fax2Mail - Core Messaging - Email - Core Messaging - SMS Tracking Number: IM3951663

2. investigating Jun 26, 2026, 04:54 PM UTC

   The following services are experiencing a potential service degradation. Services that can be failed over to our alternate site will be failed over to avoid impact. Teams are currently assembled and working to resolve the issue. We appreciate your patience. - Desktop Messaging BMS - Fax Cloud Connect (RightFax) - Fax2Mail - Core Messaging - Email - Core Messaging - SMS The next update for this issue will be sent on 28 June 2026, or if there are any significant updates, whichever comes first. Tracking Number: IM3951663

3. investigating Jun 29, 2026, 08:20 AM UTC

   The following services are experiencing a potential service degradation. Services that can be failed over to our alternate site will be failed over to avoid impact. Teams are currently assembled and working to resolve the issue. We appreciate your patience. - Desktop Messaging BMS - Fax Cloud Connect (RightFax) - Fax2Mail - Core Messaging - Email - Core Messaging - SMS Updates for this issue will be sent every 2 hours or if there are significant updates, whichever comes first. Tracking Number: IM3951663

4. investigating Jun 29, 2026, 12:20 PM UTC

   The following services are experiencing a potential service degradation. Services that can be failed over to our alternate site will be failed over to avoid impact. Teams are currently assembled and working to resolve the issue. We appreciate your patience. - Desktop Messaging BMS - Fax Cloud Connect (RightFax) - Fax2Mail - Core Messaging - Email - Core Messaging - SMS Updates for this issue will be sent every 24 hours or if there are significant updates, whichever comes first. Tracking Number: IM3951663

5. investigating Jun 30, 2026, 12:20 PM UTC

   The following services are experiencing a potential service degradation. Services that can be failed over to our alternate site will be failed over to avoid impact. Teams are currently assembled and working to resolve the issue. We appreciate your patience. - Desktop Messaging BMS - Fax Cloud Connect (RightFax) - Fax2Mail - Core Messaging - Email - Core Messaging - SMS Updates for this issue will be sent every 24 hours or if there are significant updates, whichever comes first. Tracking Number: IM3951663

6. investigating Jul 01, 2026, 12:20 PM UTC

   The following services are experiencing a potential service degradation. Services that can be failed over to our alternate site will be failed over to avoid impact. Teams are currently assembled and working to resolve the issue. We appreciate your patience. - Desktop Messaging BMS - Fax Cloud Connect (RightFax) - Fax2Mail - Core Messaging - Email - Core Messaging - SMS Updates for this issue will be sent every 24 hours or if there are significant updates, whichever comes first. Tracking Number: IM3951663

7. investigating Jul 02, 2026, 12:20 PM UTC

   The following services are experiencing a potential service degradation. Services that can be failed over to our alternate site will be failed over to avoid impact. Teams are currently assembled and working to resolve the issue. We appreciate your patience. - Desktop Messaging BMS - Fax Cloud Connect (RightFax) - Fax2Mail - Core Messaging - Email - Core Messaging - SMS Updates for this issue will be sent every 24 hours or if there are significant updates, whichever comes first. Tracking Number: IM3951663

8. investigating Jul 03, 2026, 12:20 PM UTC

   The following services are experiencing a potential service degradation. Services that can be failed over to our alternate site will be failed over to avoid impact. Teams are currently assembled and working to resolve the issue. We appreciate your patience. - Desktop Messaging BMS - Fax Cloud Connect (RightFax) - Fax2Mail - Core Messaging - Email - Core Messaging - SMS The next update will be sent on 6 July 2026 at 13:00 UTC or if there are significant updates, whichever comes first. Tracking Number: IM3951663

9. investigating Jul 06, 2026, 01:00 PM UTC

   The following services are experiencing a potential service degradation. Services that can be failed over to our alternate site will be failed over to avoid impact. Teams are currently assembled and still working to resolve the issue. We appreciate your patience. - Desktop Messaging BMS - Fax Cloud Connect (RightFax) - Fax2Mail - Core Messaging - Email - Core Messaging - SMS Updates for this issue will be sent every 24 hours or if there are significant updates, whichever comes first. Tracking Number: IM3951663

10. investigating Jul 07, 2026, 01:00 PM UTC

    The following services are experiencing a potential service degradation. Services that can be failed over to our alternate site will be failed over to avoid impact. Teams are currently assembled and still working to resolve the issue. We appreciate your patience. - Desktop Messaging BMS - Fax Cloud Connect (RightFax) - Fax2Mail - Core Messaging - Email - Core Messaging - SMS Updates for this issue will be sent every 24 hours or if there are significant updates, whichever comes first.

11. investigating Jul 08, 2026, 06:08 PM UTC

    The following services were experiencing a potential service degradation. Service has been restored to a workaround and is being validated at this time. If you continue to experience any related issues, please contact your support service desk team for further assistance. - Desktop Messaging BMS - Fax Cloud Connect (RightFax) - Fax2Mail - Core Messaging - Email - Core Messaging - SMS Updates for this issue will be posted as soon as there are significant updates. We appreciate your patience. Tracking Number: IM3951663

12. monitoring Jul 08, 2026, 06:13 PM UTC

    The following services were experiencing a potential service degradation. Service has been restored to a workaround and is being validated at this time. If you continue to experience any related issues, please contact your support service desk team for further assistance. - Desktop Messaging BMS - Fax Cloud Connect (RightFax) - Fax2Mail - Core Messaging - Email - Core Messaging - SMS Updates for this issue will be posted as soon as there are significant updates. We appreciate your patience. Tracking Number: IM3951663

13. resolved Jul 23, 2026, 11:43 AM UTC

    The following services were experiencing a potential service degradation. The issue is now resolved. We appreciate your patience. - Desktop Messaging BMS - Fax Cloud Connect (RightFax) - Fax2Mail - Core Messaging - Email - Core Messaging - SMS Tracking Number: IM3951663

Read the full incident report →

Started Jun 26, 2026, 07:18 AM UTC· resolved Jun 26, 2026, 07:18 AM UTC

1. resolved Jun 26, 2026, 07:18 AM UTC

   Frankfurt EU28 experienced service unavailability. The issue is now resolved. We appreciate your patience. Tracking Number: IM3951449

2. postmortem Jun 26, 2026, 12:48 PM UTC

   # Incident Report **Tracking number:** IM3951449 PM1011657 **Incident window:** June 26, 2026, from 06:18 GMT to 07:10 GMT **Services affected:** OpenText™ Enterprise Service Manager **RCA target completion date:** July 13, 2026 **Overview** On June 26, 2026, 07:32 GMT, Incident Management was engaged to investigate performance degradation affecting multiple customers on the EU28 farm. **Impact** Users experienced service performance degradation. **Resolution** The investigation revealed that degraded RabbitMQ performance was the cause of intermittent service availability on the EU28 farm. The RabbitMQ service was rebuilt as part of the recovery activities, and application performance was restored at 07:10 GMT.

Read the full incident report →

Started Jun 24, 2026, 05:16 PM UTC· resolved Jun 24, 2026, 06:02 PM UTC

1. investigating Jun 24, 2026, 05:16 PM UTC

   Core Capture EU is currently unavailable. Teams are being assembled to troubleshoot and remediate the issue.

2. resolved Jun 24, 2026, 06:02 PM UTC

   Core Capture EU was unavailable. The issue is now resolved. We appreciate your patience. Tracking Number: IM3950513

Read the full incident report →

Started Jun 24, 2026, 05:08 PM UTC· resolved Jul 08, 2026, 01:30 PM UTC

1. monitoring Jun 24, 2026, 05:08 PM UTC

   We are currently investigating reports of Link Protection returning errors when attempting to access links that are wrapped with our Link Protection scanning. We will update once we have more information. Incident: IM3949690

2. identified Jun 24, 2026, 05:12 PM UTC

   We are currently still triaging and testing our Link Protection with all available resources. We are seeing sporadic failures of link scanning and are working to bring the platform back to fully operational status.

3. monitoring Jun 24, 2026, 07:28 PM UTC

   We have implemented a fix on this and are currently monitoring logs to ensure we are not seeing any furthers with Link Protection scans. Incident: IM3949690

4. monitoring Jun 25, 2026, 03:19 PM UTC

   We are continuing to monitor our back-end logs and have seen small downtime windows that are occurring sporadically today. Our team is monitoring and continuing to work on resolve the underlying root issue. Incident: IM3949690

5. monitoring Jun 29, 2026, 01:32 PM UTC

   We are continuing to monitor our back-end logs and have seen small downtime windows that are occurring sporadically this morning. Our team is monitoring and continuing to work on resolve the underlying root issue with a planned hot fix. Incident: IM3949690

6. monitoring Jun 30, 2026, 04:43 PM UTC

   We have a planned fix in place for the underlying issue to be released today into production. We will update once the deployment has been deployed and will continue to monitor the back end logs for any further errors.

7. monitoring Jun 30, 2026, 08:50 PM UTC

   We have deployed the hot fix for the root issue and are team is monitoring our back-end logs to ensure no further error occur on the scan.

8. monitoring Jul 01, 2026, 03:04 PM UTC

   We are seeing intermittent "service unavailable" errors with the wrapped Link Protection URL's and are team continues to triage the issue. They are currently investigating the back end logs to see what is causing the errors to continue to generate. Incident: IM3949690

9. monitoring Jul 01, 2026, 07:00 PM UTC

   Our teams continue to triage the issue and are seeing lower failure rates on URL scanning with the hotfix. They are actively working to resolve the underlying/root issue. We will update once we have further details from our development teams. Incident: IM3949690

10. monitoring Jul 02, 2026, 01:50 PM UTC

    Our team continues to triage and work on a back end fix for the sporadic "service unavailable" errors. We will update once we have any further information on this. Incident: IM3949690

11. monitoring Jul 02, 2026, 02:59 PM UTC

    Our team is activelty working to add more servers into the server clusters to help mitigate any further throughput issues and plan to have those in place this afternoon. We will update once those have been completed. Incident: IM3949690

12. monitoring Jul 02, 2026, 11:28 PM UTC

    We have completed adding more server resources to the cluster and are currently monitoring logs to ensure no further errors occur. Incident: IM3949690

13. monitoring Jul 06, 2026, 12:33 PM UTC

    The team is continuing to monitor logs, and we are seeing a decrease in the "service unavailable" being returned. We are actively still triaging the issue to ensure full operational status of the service. Incident: IM3949690

14. monitoring Jul 06, 2026, 06:59 PM UTC

    The team is continuing to monitor the back end logs and are indicating a low count of any further "service unavailable" errors being presented but are actively working to ensure all services are fully operational. Incident: IM3949690

15. monitoring Jul 07, 2026, 11:57 AM UTC

    We are seeing significant reduction in Link Protection errors but are actively monitor the health of the platform to ensure the service remains flly operational at this time. Incident: IM3949690

16. resolved Jul 08, 2026, 01:30 PM UTC

    This incident has been resolved.

Read the full incident report →

Started Jun 24, 2026, 04:43 PM UTC· resolved Jun 24, 2026, 04:43 PM UTC

1. resolved Jun 24, 2026, 04:43 PM UTC

   The RCA is now available. Click Here for RCA.

Read the full incident report →

Started Jun 24, 2026, 03:38 PM UTC· resolved Jun 25, 2026, 10:07 AM UTC

1. investigating Jun 24, 2026, 03:38 PM UTC

   Frankfurt EU18 is currently experiencing a degradation in service. Teams have identified that the farm is still experiencing slowness and are currently 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: IM3950211

2. investigating Jun 24, 2026, 05:38 PM UTC

   Frankfurt EU18 is currently experiencing a degradation in service. 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. Tracking Number: IM3950211

3. investigating Jun 24, 2026, 07:42 PM UTC

   Frankfurt EU18 is currently experiencing a degradation in service. 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. Tracking Number: IM3950211

4. investigating Jun 24, 2026, 09:43 PM UTC

   Frankfurt EU18 is currently experiencing a degradation in service. Teams are currently assembled and working to resolve the issue. We appreciate your patience. Updates for this issue will be sent every 4 hours or if there are significant updates, whichever comes first. Tracking Number: IM3950211

5. investigating Jun 25, 2026, 01:43 AM UTC

   Frankfurt EU18 is currently experiencing a degradation in service. Teams are currently assembled and working to resolve the issue. We appreciate your patience. Updates for this issue will be sent every 4 hours or if there are significant updates, whichever comes first. Tracking Number: IM3950211

6. investigating Jun 25, 2026, 05:43 AM UTC

   Frankfurt EU18 is currently experiencing a degradation in service. 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. Tracking Number: IM3950211

7. investigating Jun 25, 2026, 07:43 AM UTC

   Frankfurt EU18 is currently experiencing a degradation in service. 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. Tracking Number: IM3950211

8. resolved Jun 25, 2026, 10:07 AM UTC

   Frankfurt EU18 was experiencing a degradation in service. The issue is now resolved. We appreciate your patience. Tracking Number: IM3950211

9. postmortem Jun 25, 2026, 05:40 PM UTC

   # Incident Report **Tracking number:** IM3950211 PM1011655 **Incident window:** June 24, 2026, from 07:00 GMT to 09:45 GMT, on June 25, 2026 **Services affected:** OpenText™ Enterprise Service Management **RCA target completion date:** July 10, 2026 **Overview** On June 24, 2026, at 09:51 GMT, Incident Management was engaged to investigate performance degradation in the EU18 environment. **Impact** Service performance was degraded. **Resolution** The investigation revealed that the recent release to our 26.2 version introduced a regression into the product related to the CMDB function. After investigating the issue, the related component was reverted to the 26.1 release while an updated hotfix is being created to address the issue in future deployments. This was completed and service was restored at 08:40 GMT. Full validation was complete by 09:55 GMT, ending the impact.

Read the full incident report →

Started Jun 24, 2026, 10:13 AM UTC· resolved Jun 24, 2026, 01:14 PM UTC

1. investigating Jun 24, 2026, 10:13 AM UTC

   Frankfurt EU18 is currently experiencing a degradation in service. Teams are currently assembled and working to resolve the issue. We appreciate your patience. Tracking Number: IM3938234

2. investigating Jun 24, 2026, 11:13 AM UTC

   Frankfurt EU18 is currently experiencing a degradation in service. 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. Tracking Number: IM3938234

3. investigating Jun 24, 2026, 11:42 AM UTC

   Frankfurt EU18 is currently experiencing a degradation in service and may experience intermittent failure for a few minutes. 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. Tracking Number: IM3938234

4. resolved Jun 24, 2026, 01:14 PM UTC

   Frankfurt EU18 was experiencing a degradation in service The issue is now resolved. We appreciate your patience. Tracking Number: IM3938234

Read the full incident report →

Started Jun 23, 2026, 03:44 PM UTC· resolved Jun 23, 2026, 04:29 PM UTC

1. investigating Jun 23, 2026, 03:44 PM UTC

   We are currently investigating reports of Link Protection returning errors when attempting to access links that are wrapped with our Link Protection scanning. We will update once we have more information. Incident: IM3949690

2. resolved Jun 23, 2026, 04:29 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Jun 19, 2026, 03:25 PM UTC· resolved Jun 23, 2026, 03:40 PM UTC

1. investigating Jun 19, 2026, 03:25 PM UTC

   We are currently investigating an issue with the Customer Portal returning a "500 error" page when attempting to navigate. We will update once we have more information. Incident: IM3947784

2. monitoring Jun 19, 2026, 04:08 PM UTC

   We have confirmed the issue on our end appears to be resolved and our engineering team is currently monitoring the logs for any further issues. Incident: IM3947784

3. resolved Jun 23, 2026, 03:40 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Jun 17, 2026, 01:17 PM UTC· resolved Jun 17, 2026, 04:10 PM UTC

1. investigating Jun 17, 2026, 01:17 PM UTC

   Clients are unable to log into the faxadmin portal and experiencing SOAP API query errors. Teams are currently assembled and working to resolve the issue. We appreciate your patience. Tracking Number: IM3946292

2. investigating Jun 17, 2026, 02:17 PM UTC

   Desktop Messaging BMS is experiencing a degradation in service. Clients are unable to log in to the faxadmin portal and are experiencing SOAP API query errors. Teams are currently assembled and working to resolve the issue. We appreciate your patience. Tracking Number: IM3946292

3. investigating Jun 17, 2026, 03:17 PM UTC

   Desktop Messaging BMS is experiencing a degradation in service. Clients are unable to log in to the faxadmin portal and are experiencing SOAP API query errors. Teams are currently assembled and working to resolve the issue. We appreciate your patience. Tracking Number: IM3946292

4. resolved Jun 17, 2026, 04:10 PM UTC

   Desktop Messaging BMS experienced a degradation in service. Clients were unable to log in to the faxadmin portal and are experiencing SOAP API query errors. The issue is now resolved. We appreciate your patience. Tracking Number: IM3946292

Read the full incident report →

Started Jun 16, 2026, 06:55 PM UTC· resolved Jun 16, 2026, 06:55 PM UTC

1. resolved Jun 16, 2026, 06:55 PM UTC

   Core EDR/MDR experienced a data processing issue that affected a limited set of agents and subscription records during the routine maintenance on 15 June 2026. As a result, you may notice the following: - Activity from that day may not be fully reflected - Some agents uninstalled that day may still appear as installed - Subscription changes from that day may not be fully reflected - In limited cases, minor billing discrepancies may occur The issue is now resolved, and systems are operating normally. We appreciate your patience. If you notice anything unexpected, please contact your OpenText Support Team.

Read the full incident report →

Started Jun 16, 2026, 05:44 PM UTC· resolved Jun 16, 2026, 07:05 PM UTC

1. investigating Jun 16, 2026, 05:44 PM UTC

   Oregon US7 is currently experiencing an issue. Clients are unable to access the UI. Teams are currently assembled and working to resolve the issue. We appreciate your patience. Tracking Number: IM3945745

2. investigating Jun 16, 2026, 06:45 PM UTC

   Oregon US7 is currently experiencing an issue. Clients are unable to access the UI. Teams are currently assembled and working to resolve the issue. We appreciate your patience. Tracking Number: IM3945745

3. resolved Jun 16, 2026, 07:05 PM UTC

   Oregon US7 experienced an issue. Clients were unable to access the UI. The issue is now resolved. We appreciate your patience. Tracking Number: IM3945745

4. postmortem Jun 18, 2026, 04:25 PM UTC

   # **Incident Report** **Tracking number:** IM3945745 PM1011644 **Incident window:** June 16, 2026, from 16:20 GMT to 18:56 GMT **Services affected:** OpenText™ Enterprise Service Management \(ESM\) **RCA target completion date:** July 1, 2026 **Overview** On June 16, 2026, at 17:19 GMT, Incident Management was engaged to investigate an internal availability Issue impacting ESM SMAX US7. **Impact** Users experienced transaction failures within the Oregon US7 farm, affecting the presales environment and resulting in user inaccessibility. **Resolution** The investigation revealed that platform pods were unable to come online due to readiness probe failures. A controlled rollout restart of platform pods was initiated to continue troubleshooting. This action was intended to be non-disruptive, however, errors occurred which prevented successful pod initialization and contributed to the outage duration. Corrective actions were taken to resolve the messaging failures which enabled platform pods to successfully restart. Service was restored at 18:56 GMT, ending the impact.

Read the full incident report →

Started Jun 16, 2026, 02:14 PM UTC· resolved Jun 16, 2026, 02:25 PM UTC

1. investigating Jun 16, 2026, 02:14 PM UTC

   Core Secure Access is currently experiencing an outage. Clients are unable to access URLs. Teams are currently assembled and working to resolve the issue. We appreciate your patience. Tracking Number: IM3945596

Read the full incident report →

Started Jun 16, 2026, 01:46 PM UTC· resolved Jun 16, 2026, 02:33 PM UTC

1. investigating Jun 16, 2026, 01:46 PM UTC

   OpenText Core Secure Access login is unavailable. Users who are logging in may encounter errors in the login process. Teams are currently assembled and working to resolve the issue. We appreciate your patience. Tracking Number: IM3945596

2. investigating Jun 16, 2026, 02:20 PM UTC

   OpenText Core Secure Access login is unavailable. Users who are logging in may encounter errors in the login process. Teams are currently assembled and working to resolve the issue. We appreciate your patience. Tracking Number: IM3945596

3. monitoring Jun 16, 2026, 02:30 PM UTC

   Core Secure Access was unavailable. Service has been restored and is now being validated. We appreciate your patience. Tracking Number: IM3945596

4. resolved Jun 16, 2026, 02:33 PM UTC

   Core Secure Access was unavailable. The issue is now resolved. We appreciate your patience. Tracking Number: IM3945596

Read the full incident report →

Started Jun 15, 2026, 02:34 PM UTC· resolved Jun 15, 2026, 04:07 PM UTC

1. investigating Jun 15, 2026, 02:34 PM UTC

   We are currently investigating an issue with Link Protection in which the legacy wrapped URL's (link.zixcentral.com) are failing to load. We will update once we have further details. Incident #: IM3944768

2. resolved Jun 15, 2026, 04:07 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Jun 15, 2026, 02:20 PM UTC· resolved Jun 16, 2026, 12:19 PM UTC

1. investigating Jun 15, 2026, 02:20 PM UTC

   Zix Encryption Services - Email Message Privacy (EMP) is currently experiencing an issue with portals attached to US Dallas Site 502. Teams are currently assembled and working to resolve the issue. We appreciate your patience. Tracking Number: IM3944733

2. monitoring Jun 15, 2026, 03:23 PM UTC

   Zix Encryption Services - Email Message Privacy (EMP) experienced an issue with portals attached to US Dallas Site 502. Service has been restored and is now being validated. We appreciate your patience. Tracking Number: IM3944733

3. resolved Jun 16, 2026, 12:19 PM UTC

   Zix Encryption Services - Email Message Privacy (EMP) experienced an issue with portals attached to US Dallas Site 502. The issue is now resolved. We appreciate your patience. Tracking Number: IM3944733

Read the full incident report →