Webroot Outage History

Started Jun 10, 2026, 09:39 PM UTC· resolved Jun 11, 2026, 09:37 PM UTC

1. investigating Jun 10, 2026, 09:39 PM UTC

   We want to inform you of a recent service disruption affecting Outlook connectivity to our Exchange environment. Earlier today, during routine maintenance, some users experienced issues connecting to Outlook. Upon identifying the cause, our team promptly rolled back changes, which has resolved the issue. Service has now been fully restored, and Outlook connectivity is functioning normally. Tracking Number: IM3942421

2. monitoring Jun 10, 2026, 09:39 PM UTC

   We want to inform you of a recent service disruption affecting Outlook connectivity to our Exchange environment. Earlier today, during routine maintenance, some users experienced issues connecting to Outlook. Upon identifying the cause, our team promptly rolled back changes, which has resolved the issue. Service has now been fully restored, and Outlook connectivity is functioning normally. Tracking Number: IM3942421

3. resolved Jun 11, 2026, 09:37 PM UTC

   Zix Hosted Exchange experienced was unavailable for some users connecting via Outlook. Service has been restored and is now being validated. We appreciate your patience. Tracking Number: IM3942421

Read the full incident report →

Started Jun 09, 2026, 08:47 PM UTC· resolved Jun 16, 2026, 12:09 PM UTC

1. investigating Jun 09, 2026, 08:47 PM UTC

   We are currently experiencing degradation in the OCP US environment impacting content uploads. Teams are engaged in troubleshooting to resolve the issue.

2. monitoring Jun 09, 2026, 11:03 PM UTC

   A fix has been implemented and we are monitoring the environment

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

   This incident has been resolved.

Read the full incident report →

Started Jun 09, 2026, 08:17 PM UTC· resolved Jun 11, 2026, 11:52 AM UTC

1. investigating Jun 09, 2026, 08:17 PM UTC

   Zix Encryption Services - Secure Cloud Email Encryption (AEE) is currently experiencing an issue with the delayed processing of emails sent to the DLP service. Teams are currently assembled and working to resolve the issue. We appreciate your patience. Tracking Number: IM394167

2. monitoring Jun 09, 2026, 11:25 PM UTC

   Zix Encryption Services - Secure Cloud Email Encryption (AEE) experienced an issue with the delayed processing of emails sent to the DLP service. Service has been restored and is now being validated. We appreciate your patience. Tracking Number: IM394167

3. resolved Jun 11, 2026, 11:52 AM UTC

   Zix Encryption Services - Secure Cloud Email Encryption (AEE) experienced an issue with the delayed processing of emails sent to the DLP service. No further reports have been received. The issue is now resolved. We appreciate your patience. Tracking Number: IM394167

Read the full incident report →

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

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

   Fax Cloud Connect (RightFax) and Fax2Mail are currently experiencing intermittent connectivity issues that started on 3 June 2026 at 10:26 UTC. Clients are unable to access the portal to send faxes. Teams are currently assembled and working to resolve the issue. Backlogs exist and are currently being processed. We appreciate your patience. Tracking Number: IM3938188

2. monitoring Jun 03, 2026, 04:25 PM UTC

   Fax Cloud Connect (RightFax) and Fax2Mail experienced intermittent connectivity issues that started on 3 June 2026 at 10:26 UTC and were restored at 15:26 UTC. Clients were unable to access the portal to send faxes. Service has been restored, and backlogs are being processed. We appreciate your patience. Tracking Number: IM3938188

3. resolved Jun 03, 2026, 04:57 PM UTC

   Fax Cloud Connect (RightFax) and Fax2Mail experienced intermittent connectivity issues that started on 3 June 2026 at 10:26 UTC and were restored at 15:26 UTC. Clients were unable to access the portal to send faxes. Backlogs have been cleared at 16:50 UTC, and the issue is now resolved. We appreciate your patience. Tracking Number: IM3938188

Read the full incident report →

Started Jun 03, 2026, 02:30 PM UTC· resolved Jun 03, 2026, 02:30 PM UTC

1. resolved Jun 03, 2026, 02:30 PM UTC

   Frankfurt EU3 experienced service degradation. The issue is now resolved. We appreciate your patience. Tracking Number: IM3938234

2. postmortem Jun 10, 2026, 02:04 PM UTC

   **Tracking number:** IM3938234 PM1011629 **Incident window:** June 3, 2026, from 12:26 GMT to 14:07 GMT **Services affected:** OpenText™ ITOM - Enterprise Service Management # Overview On June 3, 2026, at 14:21 GMT, Incident Management was engaged to investigate service degradation impacting the SMAX Frankfurt EU3 environment. # Impact Customers experienced slowness and unresponsiveness when accessing the SMAX user interface. # Root Cause The investigation revealed that platform pod instability led to degraded performance and unresponsive behavior within the SMAX user interface. High query volume was generated into the database and caused the database to stall. This overloaded the CPU of the originating platform instance. # Resolution The online platform pods were restarted, which resolved the performance issues, and service returned to normal at 14:07 GMT, ending the impact. # Action Plan 1. Removed the previous online platform pods which triggered the offline platform deployment to create new pods to help to further manage the database load. - **Complete** 2. Review alerting to ensure that essential events for which the alert needs to be re-enabled are in place. - **In progress - Target complete June 23, 2026** 3. Investigate this defect further to find a long-term solution. - **In progress - Target complete July 9, 2026**

Read the full incident report →

Started Jun 02, 2026, 04:20 PM UTC· resolved Jun 03, 2026, 02:32 PM UTC

1. monitoring Jun 02, 2026, 04:20 PM UTC

   Our team is actively monitoring our fix and have seen sporadic reports of "Service Unavailable" when accessing wrapped URL's. Our team is monitoring the logs and have placed fixes in place to mitigate the errors quickly. The team is currently working on testing/deployment of a permanent hotfix for this issue as well. We apologize for any inconvenience this may be causing. Incident: IM3936734

2. resolved Jun 03, 2026, 02:32 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Jun 01, 2026, 03:02 PM UTC· resolved Jun 01, 2026, 06:11 PM UTC

1. identified Jun 01, 2026, 03:02 PM UTC

   We have identified and issue with the ETP Link Protection service and are working to resolve this issue as soon as possible. Incident #:IM3936734

2. identified Jun 01, 2026, 04:15 PM UTC

   We have identified the issue and are working with our engineering team to resolve the issue. We are seeing sporadic failures of our Link Protection and are continuing to work towards a resolution. Incident #:IM3936734

3. monitoring Jun 01, 2026, 05:10 PM UTC

   We have deployed a hotfix and are seeing improvements in the Link Protection scanning completing. We are currently monitoring to ensure the issue is fully reesolved. Incident #:IM3936734

4. resolved Jun 01, 2026, 06:11 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Jun 01, 2026, 01:52 PM UTC· resolved Jun 01, 2026, 08:22 PM UTC

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

   Zix Encryption Services - ZixPortal is currently experiencing an issue with using the link from the secure message portal invites. Teams are currently assembled and working to resolve the issue. We appreciate your patience. Tracking Number: IM3936680

2. monitoring Jun 01, 2026, 04:02 PM UTC

   Zix - Cybersecurity - Zix Encryption Services - ZixPortal experienced an issue with users receiving "Message Expired" and "Message Deleted" notifications. Service has been restored and is now being validated. We appreciate your patience. Tracking Number: IM3936680

3. resolved Jun 01, 2026, 08:22 PM UTC

   Zix Encryption Services - ZixPortal experienced an issue when using the link in secure message portal invites. There have been no new issues reported after the fix. The issue is now resolved. We appreciate your patience. Tracking Number: IM3936680

Read the full incident report →

Started May 31, 2026, 03:26 AM UTC· resolved May 31, 2026, 11:36 AM UTC

1. identified May 31, 2026, 03:26 AM UTC

   Multiple OCP applications are not available in both EU and NA. Teams are engaged and actively working towards a resolution

2. monitoring May 31, 2026, 03:37 AM UTC

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

3. resolved May 31, 2026, 11:36 AM UTC

   This incident has been resolved.

Read the full incident report →

Started May 29, 2026, 02:22 PM UTC· resolved May 29, 2026, 03:08 PM UTC

1. investigating May 29, 2026, 02:22 PM UTC

   We are currently investigating an issue in which our Link Protection is retuning a "service unavailable" error when accessing a protected link. Out internal teams are actively triaging the issue and will update as soon as more information is made available. Incident: IM3935335

2. resolved May 29, 2026, 03:08 PM UTC

   We have resolved the issue and apologize for any inconvenience this may have caused. Incident: IM3935335

Read the full incident report →

Started May 29, 2026, 09:46 AM UTC· resolved May 29, 2026, 01:50 PM UTC

1. identified May 29, 2026, 09:46 AM UTC

   Core Capture Australia is experiencing performance degradation in processing documents. Teams have been assembled and are working towards a resolution

2. monitoring May 29, 2026, 12:17 PM UTC

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

3. resolved May 29, 2026, 01:50 PM UTC

   This incident has been resolved.

Read the full incident report →

Started May 28, 2026, 02:03 PM UTC· resolved Jun 01, 2026, 04:03 AM UTC

1. investigating May 28, 2026, 02:03 PM UTC

   The following services are experiencing service unavailability. Teams are currently assembled and working to resolve the issue. We appreciate your patience. - Core Messaging Data Sovereignty - Core Messaging - Email - Core Messaging - SMS - Core Messaging - Voice - MyPortal Tracking Number: IM3934421

2. investigating May 28, 2026, 03:02 PM UTC

   The following services are experiencing service unavailability. Teams are currently assembled and working to resolve the issue. We appreciate your patience. - Core Messaging Data Sovereignty - Core Messaging - Email - Core Messaging - SMS - Core Messaging - Voice - MyPortal Tracking Number: IM3934421

3. investigating May 28, 2026, 04:01 PM UTC

   The following services are experiencing service unavailability. Teams are currently assembled and working to resolve the issue. We appreciate your patience. - Core Messaging Data Sovereignty - Core Messaging - Email - Core Messaging - SMS - Core Messaging - Voice - MyPortal Updates for this issue will be sent every 3 hours or if there are significant updates, whichever comes first. Tracking Number: IM3934421

4. investigating May 28, 2026, 07:20 PM UTC

   The following services are experiencing service degradation. Teams are currently assembled and working to resolve the issue. We appreciate your patience. - Core Messaging Data Sovereignty - Core Messaging - Email - Core Messaging - SMS - Core Messaging - Voice - MyPortal The impact statement has been updated from service unavailability to service degradation. Updates for this issue will be sent every 3 hours or if there are significant updates, whichever comes first. Tracking Number: IM3934421

5. investigating May 28, 2026, 10:00 PM UTC

   The following services are experiencing service degradation. Teams are currently assembled and working to resolve the issue. We appreciate your patience. - Core Messaging Data Sovereignty - Core Messaging - Email - Core Messaging - SMS - Core Messaging - Voice - MyPortal Updates for this issue will be sent every 4 hours or if there are significant updates, whichever comes first. Tracking Number: IM3934421

6. investigating May 29, 2026, 02:55 AM UTC

   The following services are experiencing service degradation. Teams are currently assembled and working to resolve the issue. We appreciate your patience. - Core Messaging Data Sovereignty - Core Messaging - Email - Core Messaging - SMS - Core Messaging - Voice - MyPortal Updates for this issue will be sent every 6 hours or if there are significant updates, whichever comes first. Tracking Number: IM3934421

7. investigating May 29, 2026, 08:09 AM UTC

   The following services are experiencing service degradation. Teams are currently assembled and working to resolve the issue. We appreciate your patience. - Core Messaging Data Sovereignty - Core Messaging - Email - Core Messaging - SMS - Core Messaging - Voice - MyPortal Updates for this issue will be sent every 6 hours or if there are significant updates, whichever comes first. Tracking Number: IM3934421

8. investigating May 29, 2026, 02:00 PM UTC

   The following services are experiencing service degradation. Teams are currently assembled and working to resolve the issue. We appreciate your patience. - Core Messaging Data Sovereignty - Core Messaging - Email - Core Messaging - SMS - Core Messaging - Voice - MyPortal Updates for this issue will be sent every 6 hours or if there are significant updates, whichever comes first. Tracking Number: IM3934421

9. investigating May 29, 2026, 08:05 PM UTC

   The following services are experiencing service degradation. Teams are currently assembled and working to resolve the issue. We appreciate your patience. - Core Messaging Data Sovereignty - Core Messaging - Email - Core Messaging - SMS - Core Messaging - Voice - MyPortal The next update for this issue will be after 24 hours or if there are significant updates, whichever comes first. Tracking Number: IM3934421

10. monitoring May 30, 2026, 12:28 PM UTC

    The following services were experiencing service degradation. Service has been restored and monitoring is in progress. We appreciate your patience. - Core Messaging Data Sovereignty - Core Messaging - Email - Core Messaging - SMS - Core Messaging - Voice - MyPortal The next update for this issue will be on Monday at 1:00 PM GMT, whichever comes first. Tracking Number: IM3934421

11. resolved Jun 01, 2026, 04:03 AM UTC

    The following services were experiencing service degradation. The issue is now resolved. We appreciate your patience. - Core Messaging Data Sovereignty - Core Messaging - Email - Core Messaging - SMS - Core Messaging - Voice - MyPortal Tracking Number: IM3934421

Read the full incident report →

Started May 28, 2026, 01:06 PM UTC· resolved Jun 01, 2026, 04:01 AM UTC

1. investigating May 28, 2026, 01:06 PM UTC

   The following services are currently experiencing a degradation in service. Teams are currently assembled and working to resolve the issue. We appreciate your patience. - Desktop Messaging BMS - Fax Cloud Connect (RightFax) - Fax2Mail - MyPortal - Production Messaging - Core Messaging Data Sovereignty - Core Messaging - Email - Core Messaging - SMS - Core Messaging - Voice - MyPortal Tracking Number: IM3933223

2. investigating May 28, 2026, 02:01 PM UTC

   The following services are currently experiencing a degradation in service. Teams are currently assembled and working to resolve the issue. We appreciate your patience. - Desktop Messaging BMS - Fax Cloud Connect (RightFax) - Fax2Mail - MyPortal - Production Messaging The incident number has been updated to reflect the correct incident number. Tracking Number: IM3934421 OpenText teams have identified that Core Messaging Europe is experiencing service unavailability and will be removed from this update. A separate update will be posted for Core Messaging Europe services to provide a more accurate impact to the customers.

3. investigating May 28, 2026, 03:02 PM UTC

   The following services are currently experiencing a degradation in service. Teams are currently assembled and working to resolve the issue. We appreciate your patience. - Desktop Messaging BMS - Fax Cloud Connect (RightFax) - Fax2Mail - MyPortal - Production Messaging Tracking Number: IM3934421

4. investigating May 28, 2026, 04:01 PM UTC

   The following services are currently experiencing a degradation in service. Teams are currently assembled and working to resolve the issue. We appreciate your patience. - Desktop Messaging BMS - Fax Cloud Connect (RightFax) - Fax2Mail - MyPortal - Production Messaging Updates for this issue will be sent every 3 hours or if there are significant updates, whichever comes first. Tracking Number: IM3934421

5. investigating May 28, 2026, 07:00 PM UTC

   The following services are currently experiencing a degradation in service. Teams are currently assembled and working to resolve the issue. We appreciate your patience. - Desktop Messaging BMS - Fax Cloud Connect (RightFax) - Fax2Mail - MyPortal - Production Messaging Updates for this issue will be sent every 3 hours or if there are significant updates, whichever comes first. Tracking Number: IM3934421

6. investigating May 28, 2026, 10:00 PM UTC

   The following services are currently experiencing a degradation in service. Teams are currently assembled and working to resolve the issue. We appreciate your patience. - Desktop Messaging BMS - Fax Cloud Connect (RightFax) - Fax2Mail - MyPortal - Production Messaging Updates for this issue will be sent every 4 hours or if there are significant updates, whichever comes first. Tracking Number: IM3934421

7. investigating May 29, 2026, 02:00 AM UTC

   The following services are currently experiencing a degradation in service. Teams are currently assembled and working to resolve the issue. We appreciate your patience. - Desktop Messaging BMS - Fax Cloud Connect (RightFax) - Fax2Mail - MyPortal - Production Messaging Updates for this issue will be sent every 6 hours or if there are significant updates, whichever comes first. Tracking Number: IM3934421

8. investigating May 29, 2026, 08:09 AM UTC

   The following services are currently experiencing a degradation in service. Teams are currently assembled and working to resolve the issue. We appreciate your patience. - Desktop Messaging BMS - Fax Cloud Connect (RightFax) - Fax2Mail - MyPortal - Production Messaging Updates for this issue will be sent every 6 hours or if there are significant updates, whichever comes first. Tracking Number: IM3934421

9. investigating May 29, 2026, 02:00 PM UTC

   The following services are currently experiencing a degradation in service. Teams are currently assembled and working to resolve the issue. We appreciate your patience. - Desktop Messaging BMS - Fax Cloud Connect (RightFax) - Fax2Mail - MyPortal - Production Messaging Updates for this issue will be sent every 6 hours or if there are significant updates, whichever comes first. Tracking Number: IM3934421

10. investigating May 29, 2026, 08:05 PM UTC

    The following services are currently experiencing a degradation in service. Teams are currently assembled and working to resolve the issue. We appreciate your patience. - Desktop Messaging BMS - Fax Cloud Connect (RightFax) - Fax2Mail - MyPortal - Production Messaging The next update for this issue will be after 24 hours or if there are significant updates, whichever comes first. Tracking Number: IM3934421

11. monitoring May 30, 2026, 12:29 PM UTC

    The following services was experiencing a degradation in service. Service has been restored and monitoring is in progress. We appreciate your patience. - Desktop Messaging BMS - Fax Cloud Connect (RightFax) - Fax2Mail - MyPortal - Production Messaging The next update for this issue will be on Monday at 1:00 PM GMT, whichever comes first. Tracking Number: IM3934421

12. resolved Jun 01, 2026, 04:01 AM UTC

    The following services was experiencing a degradation in service. The issue is now resolved. We appreciate your patience. - Desktop Messaging BMS - Fax Cloud Connect (RightFax) - Fax2Mail - MyPortal - Production Messaging Tracking Number: IM3934421

Read the full incident report →

Started May 27, 2026, 11:03 AM UTC· resolved May 27, 2026, 11:45 AM UTC

1. investigating May 27, 2026, 11:03 AM UTC

   The following services are currently experiencing an issue. Teams are currently assembled and working to resolve the issue. We appreciate your patience. - Fax Cloud Connect (RightFax) - Fax2Mail - Production Messaging Tracking Number: IM3933644

2. resolved May 27, 2026, 11:45 AM UTC

   The following services experienced an issue. The issue is now resolved; however, backlogs are still being processed. We appreciate your patience. - Fax Cloud Connect (RightFax) - Fax2Mail - Production Messaging Tracking Number: IM3933644

Read the full incident report →

Started May 25, 2026, 03:32 PM UTC· resolved May 25, 2026, 03:32 PM UTC

1. resolved May 25, 2026, 03:32 PM UTC

   Oregon US6 experienced service degradation. The issue is now resolved. We appreciate your patience. Tracking Number: IM3932733

Read the full incident report →

Started May 24, 2026, 03:49 AM UTC· resolved May 24, 2026, 04:46 AM UTC

1. investigating May 24, 2026, 03:49 AM UTC

   Alloy North America is currently experiencing service degradation. Teams are currently assembled and working to resolve the issue. We appreciate your patience. Tracking Number: IM3932089

2. resolved May 24, 2026, 04:46 AM UTC

   Alloy North America was experiencing service degradation. The issue is now resolved. We appreciate your patience. Tracking Number: IM3932089

Read the full incident report →

Started May 21, 2026, 07:54 PM UTC· resolved May 21, 2026, 08:30 PM UTC

1. investigating May 21, 2026, 07:54 PM UTC

   We are currently investigating this issue.

2. investigating May 21, 2026, 07:58 PM UTC

   Issue has been resolved.

3. resolved May 21, 2026, 08:30 PM UTC

   Core Share NA experienced login issue. The issue is now resolved. We appreciate your patience.

Read the full incident report →

Started May 21, 2026, 04:04 PM UTC· resolved May 26, 2026, 07:25 AM UTC

1. investigating May 21, 2026, 04:04 PM UTC

   Frankfurt EU3 and Oregon US7 are currently experiencing email functionality issues. Teams are currently assembled and working to resolve the issue. We appreciate your patience. Tracking Number: IM3930847

2. investigating May 21, 2026, 05:04 PM UTC

   Frankfurt EU3 and Oregon US7 are currently experiencing email functionality issues. 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: IM3930847

3. investigating May 21, 2026, 09:04 PM UTC

   Frankfurt EU3 and Oregon US7 are currently experiencing email functionality issues. 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: IM3930847

4. investigating May 22, 2026, 01:06 AM UTC

   Frankfurt EU3 and Oregon US7 are currently experiencing email functionality issues. 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: IM3930847

5. investigating May 22, 2026, 01:54 AM UTC

   Frankfurt EU3 and Oregon US7 are currently experiencing email functionality issues. Teams have identified the cause 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: IM3930847

6. identified May 22, 2026, 06:50 AM UTC

   Frankfurt EU3 and Oregon US7 are currently experiencing email functionality issues. Teams have identified the cause 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: IM3930847

7. identified May 22, 2026, 10:50 AM UTC

   Frankfurt EU3 and Oregon US7 are currently experiencing email functionality issues. Teams have identified the cause 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: IM3930847

8. identified May 22, 2026, 02:50 PM UTC

   Frankfurt EU3 and Oregon US7 are currently experiencing email functionality issues. Teams have identified the cause 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: IM3930847

9. identified May 22, 2026, 08:36 PM UTC

   Frankfurt EU3 and Oregon US7 are currently experiencing email functionality issues. Teams have identified the cause and are working to resolve the issue. We appreciate your patience. The next update for this issue will be sent on Monday, May 25, 2026, or if there are significant updates, whichever comes first. Tracking Number: IM3930847

10. identified May 25, 2026, 06:55 AM UTC

    Frankfurt EU3 and Oregon US7 are currently experiencing email functionality issues. Teams have identified the cause and are working to resolve the issue. We appreciate your patience. Updates for this issue will be sent every 5 hours, or if there are significant updates, whichever comes first. Tracking Number: IM3930847

11. identified May 25, 2026, 11:55 AM UTC

    Frankfurt EU3 and Oregon US7 are currently experiencing email functionality issues. Teams have identified the cause and are working to resolve the issue. We appreciate your patience. Updates for this issue will be sent every 5 hours, or if there are significant updates, whichever comes first. Tracking Number: IM3930847

12. identified May 25, 2026, 04:55 PM UTC

    Frankfurt EU3 and Oregon US7 are currently experiencing email functionality issues. Teams have identified the cause and are working to resolve the issue. We appreciate your patience. Updates for this issue will be sent every 5 hours, or if there are significant updates, whichever comes first. Tracking Number: IM3930847

13. identified May 25, 2026, 09:55 PM UTC

    Frankfurt EU3 and Oregon US7 are currently experiencing email functionality issues. Teams have identified the cause and are working to resolve the issue. We appreciate your patience. Updates for this issue will be sent every 5 hours, or if there are significant updates, whichever comes first. Tracking Number: IM3930847

14. identified May 26, 2026, 03:00 AM UTC

    Frankfurt EU3 and Oregon US7 are currently experiencing email functionality issues. Teams have identified the cause and are working to resolve the issue. We appreciate your patience. Updates for this issue will be sent every 5 hours, or if there are significant updates, whichever comes first. Tracking Number: IM3930847

15. resolved May 26, 2026, 07:25 AM UTC

    Frankfurt EU3 and Oregon US7 were experiencing email functionality issues. The issue is now resolved. We appreciate your patience. Tracking Number: IM3930847

Read the full incident report →

Started May 15, 2026, 01:41 PM UTC· resolved May 15, 2026, 07:31 PM UTC

1. investigating May 15, 2026, 01:41 PM UTC

   Zix Encryption Services - Secure Cloud Email Encryption (AEE/ZEE) is currently experiencing an issue with delays in delivering email. Teams are currently assembled and working to resolve the issue. We appreciate your patience. Tracking Number: IM3927189

2. investigating May 15, 2026, 04:27 PM UTC

   Zix Encryption Services - Secure Cloud Email Encryption (AEE/ZEE) is currently experiencing an issue with delays in delivering email. Teams are currently assembled and working to resolve the issue. We appreciate your patience. Tracking Number: IM3927189

3. monitoring May 15, 2026, 06:30 PM UTC

   Zix Encryption Services - Secure Cloud Email Encryption (AEE/ZEE) experienced an issue with delays in delivering email messages. Service has been restored and is now being validated. We appreciate your patience. Tracking Number: IM3927189

4. resolved May 15, 2026, 07:31 PM UTC

   Zix Encryption Services - Secure Cloud Email Encryption (AEE/ZEE) experienced an issue with delays in delivering email. The issue is now resolved. We appreciate your patience. Tracking Number: IM3927189

Read the full incident report →

Started May 14, 2026, 02:18 PM UTC· resolved May 14, 2026, 03:35 PM UTC

1. investigating May 14, 2026, 02:18 PM UTC

   ProviderLink is currently experiencing an issue. Teams are currently assembled and working to resolve the issue. We appreciate your patience. Tracking Number: IM3926497

2. investigating May 14, 2026, 03:31 PM UTC

   ProviderLink is currently experiencing an issue. Teams are currently assembled and working to resolve the issue. We appreciate your patience. Tracking Number: IM3926497

3. monitoring May 14, 2026, 03:34 PM UTC

   ProviderLink experienced an issue. Service has been restored and is now being validated. We appreciate your patience. Tracking Number: IM3926497

4. resolved May 14, 2026, 03:35 PM UTC

   ProviderLink experienced an issue. The issue is now resolved. We appreciate your patience. Tracking Number: IM3926497

Read the full incident report →

Started May 14, 2026, 02:08 PM UTC· resolved May 14, 2026, 02:24 PM UTC

1. investigating May 14, 2026, 02:08 PM UTC

   ProviderLink is currently experiencing an issue. Teams are currently assembled and working to resolve the issue. We appreciate your patience. Tracking Number: IM3926497

Read the full incident report →

Started May 13, 2026, 06:19 PM UTC· resolved May 18, 2026, 04:56 PM UTC

1. identified May 13, 2026, 06:19 PM UTC

   Core EDR/MDR customers in the UK data center attempting to perform new installations of the EDR/MDR agent may experience installation failures. Teams have identified the cause and are working to resolve the issue. We appreciate your patience. While the Core Endpoint Protection component installs successfully, the EDR/MDR components may fail to install, resulting in incomplete agent deployment. Existing agents may also fail to upgrade to version 3.0.3; however, currently installed agents will continue to function as expected.

2. identified May 13, 2026, 07:19 PM UTC

   Core EDR/MDR customers in the UK data center attempting to perform new installations of the EDR/MDR agent may experience installation failures. Teams are currently assembled and working to resolve the issue. We appreciate your patience. While the Core Endpoint Protection component installs successfully, the EDR/MDR components may fail to install, resulting in incomplete agent deployment. Existing agents may also fail to upgrade to version 3.0.3; however, currently installed agents will continue to function as expected. Updates for this issue will be sent every 6 hours, or if there are significant updates, whichever comes first.

3. identified May 14, 2026, 01:19 AM UTC

   Core EDR/MDR customers in the UK data center attempting to perform new installations of the EDR/MDR agent may experience installation failures. Teams are currently assembled and working to resolve the issue. We appreciate your patience. While the Core Endpoint Protection component installs successfully, the EDR/MDR components may fail to install, resulting in incomplete agent deployment. Existing agents may also fail to upgrade to version 3.0.3; however, currently installed agents will continue to function as expected. Updates for this issue will be sent every 6 hours, or if there are significant updates, whichever comes first.

4. identified May 14, 2026, 11:41 AM UTC

   Core EDR/MDR customers in the UK data center attempting to perform new installations of the EDR/MDR agent may experience installation failures. Teams are currently assembled and working to resolve the issue. We appreciate your patience. While the Core Endpoint Protection component installs successfully, the EDR/MDR components may fail to install, resulting in incomplete agent deployment. Existing agents may also fail to upgrade to version 3.0.3; however, currently installed agents will continue to function as expected. Updates for this issue will be sent every 6 hours, or if there are significant updates, whichever comes first.

5. identified May 14, 2026, 02:19 PM UTC

   Core EDR/MDR customers in the UK data center attempting to perform new installations of the Linux EDR/MDR agent may experience installation failures. Teams are currently assembled and working to resolve the issue. We appreciate your patience. EDR/MDR components may now be installed, and existing agents can now be upgraded to version 3.0.3. Updates for this issue will be sent every 6 hours, or if there are significant updates, whichever comes first.

6. monitoring May 14, 2026, 08:27 PM UTC

   Core EDR/MDR customers in the UK data center attempting to perform new installations of the Linux EDR/MDR agent may have experienced installation failures. Service has been restored and is now being validated. We appreciate your patience. While the Core Endpoint Protection component installs successfully, the EDR/MDR components may fail to install, resulting in incomplete agent deployment for new customers in the UK data center. Updates for this issue will be sent every 6 hours, or if there are significant updates, whichever comes first.

7. monitoring May 15, 2026, 02:27 AM UTC

   Core EDR/MDR customers in the UK data center attempting to perform new installations of the Linux EDR/MDR agent may have experienced installation failures. Service has been restored and is now being validated. We appreciate your patience. While the Core Endpoint Protection component installs successfully, the EDR/MDR components may fail to install, resulting in incomplete agent deployment for new customers in the UK data center. Updates for this issue will be sent every 6 hours, or if there are significant updates, whichever comes first.

8. monitoring May 15, 2026, 08:27 AM UTC

   Core EDR/MDR customers in the UK data center attempting to perform new installations of the Linux EDR/MDR agent may have experienced installation failures. Service has been restored and is now being validated. We appreciate your patience. While the Core Endpoint Protection component installs successfully, the EDR/MDR components may fail to install, resulting in incomplete agent deployment for new customers in the UK data center. Updates for this issue will be sent every 6 hours, or if there are significant updates, whichever comes first.

9. monitoring May 15, 2026, 02:21 PM UTC

   Core EDR/MDR customers in the UK data center attempting to perform new installations of the Linux EDR/MDR agent may have experienced installation failures. Service has been restored and is now being validated. We appreciate your patience. While the Core Endpoint Protection component installs successfully, the EDR/MDR components may fail to install, resulting in incomplete agent deployment for new customers in the UK data center. Updates for this issue will be sent every 6 hours, or if there are significant updates, whichever comes first.

10. monitoring May 15, 2026, 08:30 PM UTC

    Core EDR/MDR customers in the UK data center attempting to perform new installations of the Linux EDR/MDR agent may have experienced installation failures. Service has been restored and is now being validated. We appreciate your patience. While the Core Endpoint Protection component installs successfully, the EDR/MDR components may fail to install, resulting in incomplete agent deployment for new customers in the UK data center. The next update for this issue will be on Monday, 18 May 2026, at 15:00 UTC or if there are significant updates, whichever comes first.

11. monitoring May 18, 2026, 03:00 PM UTC

    Core EDR/MDR customers in the UK data center attempting to perform new installations of the Linux EDR/MDR agent may have experienced installation failures. Service has been restored and is now being validated. We appreciate your patience. While the Core Endpoint Protection component installs successfully, the EDR/MDR components may fail to install, resulting in incomplete agent deployment for new customers in the UK data center. Updates for this issue will be sent every 6 hours, or if there are significant updates, whichever comes first.

12. resolved May 18, 2026, 04:56 PM UTC

    Core EDR/MDR customers in the UK data center attempting to perform new installations of the Linux EDR/MDR agent may have experienced installation failures. The issue is now resolved. We appreciate your patience.

Read the full incident report →

Started May 13, 2026, 01:20 PM UTC· resolved May 29, 2026, 12:45 PM UTC

1. investigating May 13, 2026, 01:20 PM UTC

   We are currently experiencing intermittent errors with the document upload functionality. Our teams have been assembled and are actively investigating the issue. We will provide additional updates as more information becomes available.

2. identified May 13, 2026, 05:06 PM UTC

   The issue causing intermittent errors during document uploads has been identified. The team is currently working on developing and deploying a fix. We will continue to provide updates through this notification as new information becomes available. Ref# IM3925260.

3. monitoring May 13, 2026, 09:37 PM UTC

   The issue causing intermittent upload failures, has been addressed with a fix that is improving upload success rates. We remain focused on further improving document upload stability and success rates with incremental improvements in upcoming updates. We are actively monitoring system performance and will share further updates as they become available. Ref# IM3925260.

4. monitoring May 20, 2026, 02:03 PM UTC

   The issue causing intermittent upload failures has been addressed with a fix that is already improving upload success rates. We remain committed to further enhancing document upload stability and will continue to introduce incremental improvements in upcoming updates. Our teams are actively monitoring system performance and will provide additional updates as they become available. For more details and available workarounds, please refer to: https://support.opentext.com/csm?id=kb_article_view&sysparm_article=KB0865033 Ref# IM3925260.

5. monitoring May 28, 2026, 04:50 PM UTC

   The intermittent document upload issue has been fully resolved following a fix that was implemented on the evening of Friday, May 22, 2026. Since the fix was applied, the system has been under continuous monitoring, and we are pleased to report that there have been zero upload failures. After six consecutive days of stable performance and a 100% upload success rate, we are officially considering this issue resolved as of May 28, 2026. In addition to resolving this issue, we continue to make ongoing improvements to overall system performance across both infrastructure and software. As part of these efforts, a software upgrade is planned in the coming weeks (relevant information will be communicated through a separate system maintenance notification) to bring this region onto the latest code version. If you have any questions regarding this incident or upcoming upgrades, please reach out to Support through your usual channels. For more details and available workarounds, please refer to: https://support.opentext.com/csm?id=kb_article_view&sysparm_article=KB0865033 Ref# IM3925260.

6. resolved May 29, 2026, 12:45 PM UTC

   This incident is now resolved. If you have any questions regarding this incident or upcoming upgrades, please reach out to Support through your usual channels. For more details and available workarounds, please refer to: https://support.opentext.com/csm?id=kb_article_view&sysparm_article=KB0865033 Ref# IM3925260.

Read the full incident report →

Started May 12, 2026, 03:20 PM UTC· resolved May 12, 2026, 03:55 PM UTC

1. investigating May 12, 2026, 03:20 PM UTC

   Core Archive for SAP® Solutions - DE (archive.de.opentext.cloud) is currently experiencing upload and download issues. Teams are currently assembled and working to resolve the issue. We appreciate your patience. Tracking Number: IM3925152

2. monitoring May 12, 2026, 03:39 PM UTC

   Core Archive for SAP® Solutions - DE (archive.de.opentext.cloud) experienced upload and download issues. Service has been restored and is now being validated. We appreciate your patience. Tracking Number: IM3925152

3. resolved May 12, 2026, 03:55 PM UTC

   Core Archive for SAP® Solutions - DE (archive.de.opentext.cloud) experienced upload and download issues. The issue is now resolved. We appreciate your patience. Tracking Number: IM3925152

Read the full incident report →

Started May 10, 2026, 10:08 PM UTC· resolved May 11, 2026, 01:41 AM UTC

1. identified May 10, 2026, 10:08 PM UTC

   Core Archive for SAP® Solutions - DE (archive.de.opentext.cloud) is currently unavailable. The teams have been assembled and they are working towards restoring the site Reference: IM3924061

2. monitoring May 10, 2026, 11:53 PM UTC

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

3. resolved May 11, 2026, 01:41 AM UTC

   This incident has been resolved.

Read the full incident report →