OpenText Outage History

Started Oct 21, 2026, 07:37 PM UTC· resolved Oct 21, 2026, 10:18 PM UTC

1. investigating Oct 21, 2026, 07:37 PM UTC

   The following services are currently unavailable. Teams are currently assembled and working to resolve the issue. We appreciate your patience. - Core Collaboration for Engineering (xchange.us.opentext.com) - Core Content Management - Core Content Management (corecontent.us.opentext.com) - Core Content Management for SAP® SuccessFactors | SAP® SuccessFactors Document Management Core by OpenText Tracking Number: IM4021979

2. investigating Oct 21, 2026, 08:35 PM UTC

   The following services are currently unavailable. Teams are currently assembled and working to resolve the issue. We appreciate your patience. - Core Collaboration for Engineering (xchange.us.opentext.com) - Core Content Management - Core Content Management (corecontent.us.opentext.com) - Core Content Management for SAP® SuccessFactors | SAP® SuccessFactors Document Management Core by OpenText Tracking Number: IM4021979

3. monitoring Oct 21, 2026, 09:36 PM UTC

   The following services were unavailable. Services have been restored and are now being validated. We appreciate your patience. - Core Collaboration for Engineering (xchange.us.opentext.com) - Core Content Management - Core Content Management (corecontent.us.opentext.com) - Core Content Management for SAP® SuccessFactors | SAP® SuccessFactors Document Management Core by OpenText Tracking Number: IM4021979

4. resolved Oct 21, 2026, 10:18 PM UTC

   The following services were unavailable. The issue is now resolved. We appreciate your patience. - Core Collaboration for Engineering (xchange.us.opentext.com) - Core Content Management - Core Content Management (corecontent.us.opentext.com) - Core Content Management for SAP® SuccessFactors | SAP® SuccessFactors Document Management Core by OpenText Tracking Number: IM4021979

Read the full incident report →

Started Oct 18, 2026, 05:11 AM UTC· resolved Oct 19, 2026, 07:00 AM UTC

1. resolved Oct 18, 2026, 05:11 AM UTC

   The following applications in both North America (Li3) and Europe (AM3) were unavailable. Teams were assembled at the time and recoveries were seen after restarting Authentication and Entitlement services. Core Content Core for Success Factors Core Federated Compliance Core Collaboration for Engineering (Supplier Exchange) Reference: IM4019859

Read the full incident report →

Started Oct 16, 2026, 09:08 PM UTC· resolved Oct 17, 2026, 02:16 AM UTC

1. investigating Oct 16, 2026, 09:08 PM UTC

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

2. investigating Oct 16, 2026, 10:00 PM UTC

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

3. investigating Oct 16, 2026, 10:48 PM UTC

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

4. investigating Oct 16, 2026, 11:48 PM UTC

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

5. investigating Oct 17, 2026, 12:48 AM UTC

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

6. investigating Oct 17, 2026, 01:39 AM UTC

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

7. resolved Oct 17, 2026, 02:16 AM UTC

   Desktop Messaging BMS was experiencing delays in processing PDF files. The issue is now resolved. We appreciate your patience. Tracking Number: IM4019383

Read the full incident report →

Started Oct 16, 2026, 02:13 PM UTC· resolved Oct 16, 2026, 02:48 PM UTC

1. investigating Oct 16, 2026, 02:13 PM UTC

   Core Management Console is currently experiencing intermittent login failures. Teams are currently assembled and working to resolve the issue. We appreciate your patience. Tracking Number: IM4019194

2. resolved Oct 16, 2026, 02:48 PM UTC

   Core Management Console experienced intermittent login failures. The issue is now resolved. We appreciate your patience. Tracking Number: IM4019194

Read the full incident report →

Started Oct 12, 2026, 05:50 PM UTC· resolved Oct 12, 2026, 05:50 PM UTC

1. resolved Oct 12, 2026, 05:50 PM UTC

   The RCA is now available. Click here for RCA.

Read the full incident report →

Started Oct 12, 2026, 05:45 PM UTC· resolved Oct 12, 2026, 05:45 PM UTC

1. resolved Oct 12, 2026, 05:45 PM UTC

   The RCA is now available. Click here for RCA.

Read the full incident report →

Started Oct 09, 2026, 03:09 PM UTC· resolved Oct 09, 2026, 08:22 PM UTC

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

   Multiple services are currently experiencing an issue where senders of messages are receiving "unbalanced" as a reject/NDR notification. Teams are currently assembled and working to resolve the issue. We appreciate your patience. Tracking Number: forth coming

2. investigating Oct 09, 2026, 03:12 PM UTC

   Multiple services are currently experiencing an issue in which message senders are receiving "unbalanced" as a reject/NDR notification. Teams are currently assembled and working to resolve the issue. We appreciate your patience. Tracking Number: IM4015057

3. investigating Oct 09, 2026, 03:24 PM UTC

   Zix SMB and Secure Cloud Encryption services are currently experiencing an issue when senders of messages are receiving a reject notice/NDR with "Unbalanced" as the reason. Teams are currently assembled and working to resolve the issue. We appreciate your patience. Tracking Number: IM4015057

4. investigating Oct 09, 2026, 04:06 PM UTC

   Zix SMB and Secure Cloud Encryption Services are still experiencing an issue when sending outbound messaging. Teams have assembled, identified the problem, and are working to resolve the issue as quickly as possible. We appreciate your patience. Tracking Number: IM4015057

5. monitoring Oct 09, 2026, 04:25 PM UTC

   Zix SMB and Secure Cloud Encryption services experienced an issue where all outbound messages were rejected for "Unbalanced". Service has been restored and is being validated. We appreciate your patience. Tracking Number: IM4015057

6. resolved Oct 09, 2026, 08:22 PM UTC

   Zix SMB and Secure Cloud Encryption services experienced an issue when sending outbound messages. Users would experience messages being undelivered, with the NDR showing the issue as Unbalanced. The issue is now resolved. We appreciate your patience. Tracking Number: IM4015057

Read the full incident report →

Started Oct 08, 2026, 10:29 PM UTC· resolved Oct 08, 2026, 10:33 PM UTC

1. investigating Oct 08, 2026, 10:29 PM UTC

   We are currently investigating this issue.

2. investigating Oct 08, 2026, 10:32 PM UTC

   Issue has been resolved. Core Share CA is fully operational.

3. resolved Oct 08, 2026, 10:33 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Oct 08, 2026, 08:00 PM UTC· resolved Oct 08, 2026, 11:19 PM UTC

1. identified Oct 08, 2026, 08:00 PM UTC

   Core US is currently experiencing an issue affecting search functionality. Teams have identified a recurrence and are working to resolve the issue. We appreciate your patience. - Core Collaboration for Engineering (xchange.us.opentext.com) - Core Content Management (corecontent.us.opentext.com) - Core Content Management for SAP® SuccessFactors | SAP® SuccessFactors Document Management Core by OpenText - Core Platform - Search Tracking Number: IM4014044

2. identified Oct 08, 2026, 09:00 PM UTC

   Core US is currently experiencing an issue affecting search functionality. Teams have identified a recurrence and are working to resolve the issue. We appreciate your patience. - Core Collaboration for Engineering (xchange.us.opentext.com) - Core Content Management (corecontent.us.opentext.com) - Core Content Management for SAP® SuccessFactors | SAP® SuccessFactors Document Management Core by OpenText - Core Platform - Search Updates for this issue will be sent every 2 hours or if there are any significant updates, whichever comes first. Tracking Number: IM4014044

3. identified Oct 08, 2026, 11:00 PM UTC

   Core US is currently experiencing an issue affecting search functionality. Teams have identified a recurrence and are working to resolve the issue. We appreciate your patience. - Core Collaboration for Engineering (xchange.us.opentext.com) - Core Content Management (corecontent.us.opentext.com) - Core Content Management for SAP® SuccessFactors | SAP® SuccessFactors Document Management Core by OpenText - Core Platform - Search Updates for this issue will be sent every 2 hours or if there are any significant updates, whichever comes first. Tracking Number: IM4014044

4. resolved Oct 08, 2026, 11:19 PM UTC

   Core US was experiencing an issue affecting search functionality. The issue is now resolved. We appreciate your patience. - Core Collaboration for Engineering (xchange.us.opentext.com) - Core Content Management (corecontent.us.opentext.com) - Core Content Management for SAP® SuccessFactors | SAP® SuccessFactors Document Management Core by OpenText - Core Platform - Search Tracking Number: IM4014044

Read the full incident report →

Started Oct 08, 2026, 12:37 AM UTC· resolved Oct 08, 2026, 03:53 AM UTC

1. investigating Oct 08, 2026, 12:37 AM UTC

   We are currently experiencing an issue affecting the search functionality for documents uploaded on or after October 2, 2026, at 11:00 AM UTC. Impacted Applications:: Core Content / Core4SF / Core Collaboration for Engineering Documents uploaded prior to the specified date and time should remain fully searchable and unaffected by this issue. Our technical teams are actively engaged and working together to identify the root cause and restore normal search functionality as quickly as possible. We apologize for any inconvenience this may cause and appreciate your patience as we work toward resolution. Additional updates will be provided as more information becomes available.

2. identified Oct 08, 2026, 01:20 AM UTC

   Core US is currently experiencing service degradation. This issue is affecting the search functionality for documents uploaded on or after October 2, 2026, at 11:00 AM UTC. Documents uploaded prior to the specified date and time should remain fully searchable and unaffected by this issue. Our technical teams are actively engaged and working together to identify the root cause and restore normal search functionality as quickly as possible. We apologize for any inconvenience this may cause and appreciate your patience as we work toward resolution. Additional updates will be provided as more information becomes available.

3. monitoring Oct 08, 2026, 02:11 AM UTC

   Core US experienced service degradation. This issue affected the search functionality for documents uploaded on or after October 2, 2026, at 11:00 AM UTC. The queues are currently draining and being monitored. Service has been restored and is being validated. We appreciate your patience. - Core Collaboration for Engineering (xchange.us.opentext.com) - Core Content Management (corecontent.us.opentext.com) - Core Content Management for SAP® SuccessFactors | SAP® SuccessFactors Document Management Core by OpenText - Core Platform - Search Tracking Number: IM4014044

4. monitoring Oct 08, 2026, 03:19 AM UTC

   Core US experienced service degradation. This issue affected the search functionality for documents uploaded on or after October 2, 2026, at 11:00 AM UTC. The queues are currently draining and being monitored. Service has been restored and is being validated. We appreciate your patience. - Core Collaboration for Engineering (xchange.us.opentext.com) - Core Content Management (corecontent.us.opentext.com) - Core Content Management for SAP® SuccessFactors | SAP® SuccessFactors Document Management Core by OpenText - Core Platform - Search Updates for this issue will be posted as soon as there are significant updates.

5. resolved Oct 08, 2026, 03:53 AM UTC

   Core US experienced service degradation. The issue is now resolved. We appreciate your patience. - Core Collaboration for Engineering (xchange.us.opentext.com) - Core Content Management (corecontent.us.opentext.com) - Core Content Management for SAP® SuccessFactors | SAP® SuccessFactors Document Management Core by OpenText - Core Platform - Search Tracking Number: IM4014044

Read the full incident report →

Started Oct 07, 2026, 01:53 PM UTC· resolved Oct 07, 2026, 07:56 PM UTC

1. investigating Oct 07, 2026, 01:53 PM UTC

   Zix - Hosted Exchange some users are currently experiencing an issue accessing OWA, receiving an error 500. Teams are currently assembled and working to resolve the issue. We appreciate your patience. Tracking Number:

2. monitoring Oct 07, 2026, 03:27 PM UTC

   Zix - Hosted Exchange some users are currently experiencing an issue accessing OWA, receiving an error 500.. Service has been restored and is being validated. We appreciate your patience. Tracking Number: IM4013681

3. monitoring Oct 07, 2026, 03:27 PM UTC

   We are continuing to monitor for any further issues.

4. resolved Oct 07, 2026, 07:56 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Oct 02, 2026, 05:00 PM UTC· resolved Oct 02, 2026, 05:00 PM UTC

1. resolved Oct 02, 2026, 05:00 PM UTC

   Frankfurt EU38 experienced an issue with Integration Studio. Saving listeners and creating scenarios were not working. The issue is now resolved. We appreciate your patience. Tracking Number: 3349552

Read the full incident report →

Started Oct 01, 2026, 09:46 AM UTC· resolved Oct 01, 2026, 10:18 AM UTC

1. investigating Oct 01, 2026, 09:46 AM UTC

   Core Archive for SAP® Solutions - DE and Core Archive for SAP® Solutions - AU are currently unavailable. Teams are currently assembled and working to resolve the issue. We appreciate your patience. Tracking Number: IM4009632

2. resolved Oct 01, 2026, 10:18 AM UTC

   Core Archive for SAP® Solutions - DE and Core Archive for SAP® Solutions - AU were unavailable. The issue is now resolved. We appreciate your patience. Tracking Number: IM4009632

Read the full incident report →

Started Sep 30, 2026, 03:17 PM UTC· resolved Oct 08, 2026, 12:27 AM UTC

1. investigating Sep 30, 2026, 03:17 PM UTC

   We are currently investigating an issue causing processing delays for clients within the Core Capture GCP-EU environment. Our technical teams are actively working to identify the cause and restore normal processing as quickly as possible. We will provide additional updates as more information becomes available.

2. identified Sep 30, 2026, 04:11 PM UTC

   Our technical teams have identified a potential cause for the processing slowness and are currently conducting tests to validate the findings and confirm a path forward for remediation. We will provide a further update as testing progresses and additional information becomes available.

3. monitoring Sep 30, 2026, 08:40 PM UTC

   A fix has been implemented, and initial testing has shown improved processing performance. Our technical teams continue to closely monitor the environment to confirm processing remains stable. We will provide further updates as monitoring continues.

4. investigating Oct 02, 2026, 12:35 PM UTC

   We are seeing a recurrence of the processing slowness impacting clients within the Core Capture GCP-EU environment. Our technical teams are actively investigating the issue and working to restore normal processing as quickly as possible. We will provide additional updates as more information becomes available.

5. monitoring Oct 02, 2026, 07:15 PM UTC

   At this time, we are no longer observing processing slowness, and the system has returned to normal processing speeds. Our technical teams continue to work with our vendor to identify any potential latency that may be introduced at the network or other service layers. Customers should expect normal processing performance. If you experience any further slowness, please follow the standard reporting process to report the issue so that our teams can investigate promptly.

6. monitoring Oct 05, 2026, 05:56 PM UTC

   We continue to work closely with our vendor to investigate the ongoing performance issue. The system is currently experiencing slower-than-normal processing, but transactions are continuing to be processed at this time. Our teams remain actively engaged and are working to restore normal processing speeds. We will provide additional updates as more information becomes available.

7. monitoring Oct 07, 2026, 01:50 AM UTC

   We have applied several fixes that have resulted in improved processing performance within the Core Capture GCP-EU environment. Our teams continue to work closely with the vendor to address the remaining performance concerns and bring the issue to a complete resolution. We will provide further updates as progress continues. Customers should expect normal processing performance. If you experience any further slowness, please follow the standard reporting process to report the issue so that our teams can investigate promptly.

8. resolved Oct 08, 2026, 12:27 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Sep 25, 2026, 06:56 PM UTC· resolved Sep 25, 2026, 06:56 PM UTC

1. resolved Sep 25, 2026, 06:56 PM UTC

   Core EDR/MDR experienced an issue affecting workflow processing. Workflows created on or after 11 September 2026, as well as existing workflows updated on or after that date, may have not been triggering as expected. 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 Sep 23, 2026, 08:10 PM UTC· resolved Sep 29, 2026, 04:50 PM UTC

1. investigating Sep 23, 2026, 08:10 PM UTC

   Core DNS Protection Block Page customers accessing blocked HTTPS websites may see a browser certificate warning instead of the DNS Protection block page. Blocked websites remain inaccessible, and DNS Protection continues to enforce policies as expected. Teams are currently assembled and working to resolve the issue. No customer action is required at this time. If further action becomes necessary, specific instructions will be provided. We appreciate your patience. Tracking Number: I5791953

2. investigating Sep 23, 2026, 09:10 PM UTC

   Core DNS Protection Block Page customers accessing blocked HTTPS websites may see a browser certificate warning instead of the DNS Protection block page. Blocked websites remain inaccessible, and DNS Protection continues to enforce policies as expected. Teams are currently assembled and working to resolve the issue. No customer action is required at this time. If further action becomes necessary, specific instructions will be provided. We appreciate your patience. Tracking Number: I5791953

3. investigating Sep 23, 2026, 10:13 PM UTC

   Core DNS Protection Block Page customers accessing blocked HTTPS websites may see a browser certificate warning instead of the DNS Protection block page. Blocked websites remain inaccessible, and DNS Protection continues to enforce policies as expected. Teams are currently assembled and working to resolve the issue. No customer action is required at this time. If further action becomes necessary, specific instructions will be provided. We appreciate your patience. Tracking Number: I5791953

4. investigating Sep 23, 2026, 11:09 PM UTC

   Core DNS Protection Block Page customers accessing blocked HTTPS websites may see a browser certificate warning instead of the DNS Protection block page. Blocked websites remain inaccessible, and DNS Protection continues to enforce policies as expected. Teams are currently assembled and working to resolve the issue. No customer action is required at this time. If further action becomes necessary, specific instructions will be provided. 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: I5791953

5. investigating Sep 24, 2026, 07:09 AM UTC

   Core DNS Protection Block Page customers accessing blocked HTTPS websites may see a browser certificate warning instead of the DNS Protection block page. Blocked websites remain inaccessible, and DNS Protection continues to enforce policies as expected. Teams are currently assembled and working to resolve the issue. No customer action is required at this time. If further action becomes necessary, specific instructions will be provided. 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: I5791953

6. identified Sep 24, 2026, 02:17 PM UTC

   Core DNS Protection Block Page clients accessing blocked HTTPS websites may see a browser certificate warning instead of the DNS Protection block page. Blocked websites remain inaccessible, and DNS Protection continues to enforce policies as expected. Teams have identified the cause and are working to resolve the issue as quickly as possible. No customer action is required at this time. If further action becomes necessary, specific instructions will be provided. Updates for this issue will be sent every 8 hours or if there are significant updates, whichever comes first. We appreciate your patience. Tracking Number: I5791953

7. identified Sep 24, 2026, 10:17 PM UTC

   Core DNS Protection Block Page clients accessing blocked HTTPS websites may see a browser certificate warning instead of the DNS Protection block page. Blocked websites remain inaccessible, and DNS Protection continues to enforce policies as expected. Teams have identified the cause and are working to resolve the issue as quickly as possible. No customer action is required at this time. If further action becomes necessary, specific instructions will be provided. Updates for this issue will be sent every 12 hours or if there are significant updates, whichever comes first. We appreciate your patience. Tracking Number: I5791953

8. identified Sep 25, 2026, 12:15 PM UTC

   Core DNS Protection Block Page clients accessing blocked HTTPS websites may see a browser certificate warning instead of the DNS Protection block page. Blocked websites remain inaccessible, and DNS Protection continues to enforce policies as expected. Teams have identified the cause and are working to resolve the issue as quickly as possible. No customer action is required at this time. If further action becomes necessary, specific instructions will be provided. Updates for this issue will be sent every 12 hours or if there are significant updates, whichever comes first. We appreciate your patience. Tracking Number: I5791953

9. identified Sep 25, 2026, 09:40 PM UTC

   Core DNS Protection Block Page clients accessing blocked HTTPS websites may see a browser certificate warning instead of the DNS Protection block page. Blocked websites remain inaccessible, and DNS Protection continues to enforce policies as expected. Teams are implementing a fix, and the backend update is already in place. The required DNS Agent update is currently being validated before broader deployment, and a related client utility update is also planned to be deployed. We appreciate your patience. No customer action is required at this time. If further action becomes necessary, specific instructions will be provided. Updates for this issue will be sent on 28 September 2026 or if there are significant updates, whichever comes first. Tracking Number: I5791953

10. identified Sep 28, 2026, 01:31 PM UTC

    Core DNS Protection Block Page clients accessing blocked HTTPS websites may see a browser certificate warning instead of the DNS Protection block page. Blocked websites remain inaccessible, and DNS Protection continues to enforce policies as expected. Teams are implementing a fix, and the backend update is already in place. The required DNS Agent update is currently being validated before broader deployment, and a related client utility update is also planned to be deployed. We appreciate your patience. No customer action is required at this time. If further action becomes necessary, specific instructions will be provided. Updates for this issue will be sent every 6 hours or if there are significant updates, whichever comes first.

11. identified Sep 28, 2026, 08:15 PM UTC

    Core DNS Protection Block Page clients accessing blocked HTTPS websites may see a browser certificate warning instead of the DNS Protection block page. Blocked websites remain inaccessible, and DNS Protection continues to enforce policies as expected. Teams have scheduled the required DNS Agent update to begin today, and a related client utility update is also planned to be deployed. We appreciate your patience. No customer action is required at this time. If further action becomes necessary, specific instructions will be provided. Updates for this issue will be sent every 6 hours or if there are significant updates, whichever comes first. Tracking Number: I5791953

12. identified Sep 29, 2026, 02:13 AM UTC

    Core DNS Protection Block Page clients accessing blocked HTTPS websites may see a browser certificate warning instead of the DNS Protection block page. Blocked websites remain inaccessible, and DNS Protection continues to enforce policies as expected. The required DNS Agent update, and a related client utility update is in progress. We appreciate your patience. No customer action is required at this time. If further action becomes necessary, specific instructions will be provided. Updates for this issue will be sent by 1:00 PM Eastern tomorrow, or if there are significant updates, whichever comes first. Tracking Number: I5791953

13. resolved Sep 29, 2026, 04:50 PM UTC

    Core DNS Protection Block Page clients experienced an issue accessing blocked HTTPS websites. The required updates are now available and should be applied automatically soon. Once completed, the issue is expected to be resolved without further action. The related certificate deployment utility is also available for download. We appreciate your patience. Tracking Number: I5791953

Read the full incident report →

Started Sep 18, 2026, 03:11 PM UTC· resolved Sep 18, 2026, 05:30 PM UTC

1. investigating Sep 18, 2026, 03:11 PM UTC

   Customers using CTIS-based ingestion in the OCP US environment may experience delays processing submitted jobs. Jobs submitted through SFTP or email ingestion may remain in the “Starting” state for an extended period until CTIS service connectivity is restored. Teams are assembled and actively looking at the issue for root cause and remediation Reference: IM4001177

2. investigating Sep 18, 2026, 03:23 PM UTC

   We are continuing to investigate this issue.

3. investigating Sep 18, 2026, 04:38 PM UTC

   Customers using CTIS-based ingestion in the OCP US environment may experience delays in processing submitted jobs. Jobs submitted through SFTP or email ingestion may remain in the “Starting” state for an extended period until CTIS service connectivity is restored. Teams are currently assembled and working to resolve the issue. We appreciate your patience. Tracking Number: IM4001177

4. monitoring Sep 18, 2026, 05:04 PM UTC

   CTIS Service was in a degraded state in OCP US. Customers using CTIS-based ingestion in the OCP US environment may have experienced delays in processing submitted jobs. Service has been restored and is being validated. We appreciate your patience. Tracking Number: IM4001177

5. resolved Sep 18, 2026, 05:30 PM UTC

   CTIS Service was in a degraded state in OCP US. Customers using CTIS-based ingestion in the OCP US environment may have experienced delays in processing submitted jobs. The issue is now resolved. We appreciate your patience. Tracking Number: IM4001177

Read the full incident report →

Started Sep 17, 2026, 03:29 PM UTC· resolved Sep 17, 2026, 03:50 PM UTC

1. investigating Sep 17, 2026, 03:29 PM UTC

   Frankfurt EU8 is currently experiencing service degradation. Customers may experience intermittent issues accessing the service. Operations, Engineering, and Support teams are actively investigating the issue and working to restore service as quickly as possible. We are treating this as a high priority and will continue to closely monitor the environment while mitigation efforts are in progress. We appreciate your patience and understanding. We will share more updates as they become available. Tracking Number: IM4000627

2. resolved Sep 17, 2026, 03:50 PM UTC

   Frankfurt EU8 experienced service degradation. Customers may have experienced intermittent issues accessing the service. The issue is now resolved. We appreciate your patience and understanding. Tracking Number: IM4000627

3. postmortem Sep 18, 2026, 04:45 PM UTC

   # **Incident Report** **Tracking number**: IM4000627 PM1011731 **Incident window:** September 17, 2026, from 14:28 GMT to September 17, 2026, at 15:04 GMT **Services affected:** OpenText™ Enterprise Service Management \(Frankfurt EU8\) **RCA target completion date:** October 2, 2026 **Overview** On September 17, 2026, at 15:17 GMT, Incident Management was engaged to investigate performance degradation affecting OpenText™ Enterprise Service Management clients in the Frankfurt EU8 environment. **Impact** Users experienced performance degradation and reduced system responsiveness while accessing the application. **Resolution** The investigation identified high CPU and memory utilization within the database environment, that contributed to the observed performance delays. To mitigate the issue and restore service, technical teams created an index for the affected database query to improve query efficiency and executed a controlled restart of the affected deployments. Following these actions, technical teams validated that system performance and stability returned to normal operating thresholds. Full-service recovery was confirmed at 15:40 GMT on September 17, 2026.

Read the full incident report →

Started Sep 14, 2026, 01:35 PM UTC· resolved Sep 14, 2026, 02:16 PM UTC

1. investigating Sep 14, 2026, 01:35 PM UTC

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

2. monitoring Sep 14, 2026, 01:56 PM UTC

   Frankfurt EU8 experienced a service degradation. Service has been restored and is being validated. We appreciate your patience. Tracking Number: IM3998323

3. resolved Sep 14, 2026, 02:16 PM UTC

   Frankfurt EU8 experienced a service degradation. The issue is now resolved. We appreciate your patience. Tracking Number: IM3998323

4. postmortem Sep 18, 2026, 12:42 PM UTC

   # **Incident Report** **Tracking number:** IM3998323 PM1011731 **Incident window:** September 14, 2026, from 12:32 GMT to 13:35 GMT **Services affected:** OpenText™ Enterprise Service Management \(Frankfurt EU8\) **RCA target completion date:** August 29, 2026 **Overview** On September 14, 2026, at 13:31 GMT, Incident Management was engaged to investigate service degradation affecting the OpenText™ Enterprise Service Management. **Impact** Several customers experienced performance degradation while using the OpenText™ Service Management \(SMAX\) application. The product UI was slow to resolve during this period for impacted customers and some logins were delayed. **Resolution** The investigation determined that a database spike initiated by an external integration resulted in the observed performance degradation. The integration was paused to reduce impact on the database and the system automatically. Performance stabilized at 13:35 GMT on September 14, 2026. OpenText has followed up on the integration with impacted customers to ensure best practices for use are followed going forward.

Read the full incident report →

Started Sep 14, 2026, 12:26 PM UTC· resolved Sep 14, 2026, 02:50 PM UTC

1. investigating Sep 14, 2026, 12:26 PM UTC

   Zix Archive Services BCA and ZixArchive are currently experiencing an issue when administrators navigate to the Archive pages of their respective interfaces. Teams are currently assembled and working to resolve the issue. We appreciate your patience. Tracking Number: IM3997654

2. monitoring Sep 14, 2026, 01:31 PM UTC

   Zix Archive Services BCA and ZixArchive experienced an issue when administrators navigated to the Archive pages of their respective interfaces. Service has been restored and is being validated. We appreciate your patience. Tracking Number: IM3997654

3. resolved Sep 14, 2026, 02:50 PM UTC

   Zix Archive Services BCA and ZixArchive experienced an issue when administrators navigated to the Archive pages of their respective interfaces. The issue is now resolved. We appreciate your patience. Tracking Number: IM3997654

Read the full incident report →

Started Aug 31, 2026, 04:33 PM UTC· resolved Sep 04, 2026, 12:22 PM UTC

1. investigating Aug 31, 2026, 04:33 PM UTC

   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. investigating Aug 31, 2026, 04:57 PM UTC

   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. investigating Aug 31, 2026, 05:51 PM UTC

   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. investigating Aug 31, 2026, 08:14 PM UTC

   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. identified Sep 01, 2026, 12:26 PM UTC

   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. monitoring Sep 01, 2026, 05:07 PM UTC

   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. monitoring Sep 01, 2026, 09:57 PM UTC

   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. monitoring Sep 02, 2026, 12:18 PM UTC

   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. monitoring Sep 03, 2026, 04:45 PM UTC

   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. monitoring Sep 03, 2026, 06:33 PM UTC

    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. resolved Sep 04, 2026, 12:22 PM UTC

    This incident has been resolved.

Read the full incident report →

Started Aug 28, 2026, 04:15 PM UTC· resolved Aug 28, 2026, 05:58 PM UTC

1. investigating Aug 28, 2026, 04:15 PM UTC

   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. investigating Aug 28, 2026, 05:16 PM UTC

   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

3. resolved Aug 28, 2026, 05:58 PM UTC

   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

Read the full incident report →

Started Aug 28, 2026, 02:42 AM UTC· resolved Aug 28, 2026, 03:24 AM UTC

1. investigating Aug 28, 2026, 02:42 AM UTC

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

2. monitoring Aug 28, 2026, 03:13 AM UTC

   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. resolved Aug 28, 2026, 03:24 AM UTC

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

Read the full incident report →

Started Aug 26, 2026, 02:12 PM UTC· resolved Aug 26, 2026, 03:57 PM UTC

1. investigating Aug 26, 2026, 02:12 PM UTC

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

2. monitoring Aug 26, 2026, 03:05 PM UTC

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

3. resolved Aug 26, 2026, 03:57 PM UTC

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

Read the full incident report →

Started Aug 20, 2026, 03:54 PM UTC· resolved Aug 21, 2026, 01:45 AM UTC

1. identified Aug 20, 2026, 03:54 PM UTC

   Core EDR/MDR is currently experiencing service degradation. Agents that were upgraded to version 3.3.0 from an earlier version may experience remote uninstallation issues to complete successfully. New installations of version 3.3.0 are not impacted. Teams have identified the issue only affects the Windows OS and are working to resolve the issue. 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. identified Aug 20, 2026, 04:56 PM UTC

   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. identified Aug 20, 2026, 05:55 PM UTC

   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

4. identified Aug 20, 2026, 06:58 PM UTC

   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.

5. identified Aug 20, 2026, 08:58 PM UTC

   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.

6. identified Aug 20, 2026, 10:58 PM UTC

   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.

7. monitoring Aug 20, 2026, 11:42 PM UTC

   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.

8. resolved Aug 21, 2026, 01:45 AM UTC

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

Read the full incident report →