Webroot Outage History

Started Mar 25, 2026, 08:15 AM UTC· resolved Mar 25, 2026, 08:15 AM UTC

1. resolved Mar 25, 2026, 08:15 AM UTC

   The following services were experiencing login issues. The issue is now resolved. We appreciate your patience. - Core Collaboration Access - Core Secure Access - Providerlink Tracking Number: IM3895066

Read the full incident report →

Started Mar 20, 2026, 11:35 AM UTC· resolved Mar 20, 2026, 11:35 AM UTC

1. resolved Mar 20, 2026, 11:35 AM UTC

   Core Secure Access was experiencing intermittent login failures to the applications. The issue is now resolved. We appreciate your patience. Tracking Number: IM3892076

Read the full incident report →

Started Mar 18, 2026, 06:30 PM UTC· resolved Mar 18, 2026, 07:29 PM UTC

1. investigating Mar 18, 2026, 06:30 PM UTC

   Automotive Supplier Portal Core Secure Access is unavailable. Teams are currently assembled and working to resolve the issue. We appreciate your patience. Tracking Number: IM3890899

2. monitoring Mar 18, 2026, 06:43 PM UTC

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

3. resolved Mar 18, 2026, 07:29 PM UTC

   Automotive Supplier Portal Core Secure Access was unavailable. The issue is now resolved. We appreciate your patience. Tracking Number: IM3890899

Read the full incident report →

Started Mar 13, 2026, 05:32 PM UTC· resolved Mar 13, 2026, 06:13 PM UTC

1. investigating Mar 13, 2026, 05:32 PM UTC

   Core Europe is currently experiencing an outage. Teams are being assembled to investigate and remediate the situation. Tracking number: IM3887777

2. monitoring Mar 13, 2026, 05:43 PM UTC

   Core Europe experienced an outage. Service has been restored and is now being validated. We appreciate your patience. Tracking Number: IM3887777

3. resolved Mar 13, 2026, 06:13 PM UTC

   Core Europe experienced an outage. The issue is now resolved. We appreciate your patience. Tracking Number: IM3887777

Read the full incident report →

Started Mar 05, 2026, 02:59 PM UTC· resolved Mar 05, 2026, 05:54 PM UTC

1. investigating Mar 05, 2026, 02:59 PM UTC

   Zix Encryption Services - ZixPortal is currently experiencing an issue with the Administrator Console. Teams are currently assembled and working to resolve the issue. We appreciate your patience. Tracking Number: IM3881913

2. investigating Mar 05, 2026, 04:17 PM UTC

   Zix Encryption Services - ZixPortal is currently experiencing an issue with the Administrator Console. Administrators are unable to configure their portal. Teams are currently assembled and working to resolve the issue. We appreciate your patience. Tracking Number: IM3881913

3. investigating Mar 05, 2026, 05:16 PM UTC

   Zix Encryption Services - ZixPortal is currently experiencing an issue with the Administrator Console. Administrators are unable to configure their portal. Teams are currently assembled and working to resolve the issue. We appreciate your patience. Tracking Number: IM3881913

4. resolved Mar 05, 2026, 05:54 PM UTC

   Zix Encryption Services - ZixPortal experienced an issue with the Administrator Console. Administrators were unable to configure their portal. The issue is now resolved. We appreciate your patience. Tracking Number: IM3881913

Read the full incident report →

Started Mar 03, 2026, 07:54 PM UTC· resolved Mar 04, 2026, 08:17 PM UTC

1. identified Mar 03, 2026, 07:54 PM UTC

   We have an identified an issue with a subset of customers with LDAP imports are unable to log in. We are currently investigating what occurred.

2. monitoring Mar 03, 2026, 10:06 PM UTC

   We have restarted LDAP services which will reimport the users. We are currently in the process of restoring back all user/admin settings back to users that were effected. Tracking ID : IM3881037

3. resolved Mar 04, 2026, 08:17 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Mar 03, 2026, 05:42 PM UTC· resolved Mar 04, 2026, 08:21 PM UTC

1. investigating Mar 03, 2026, 05:42 PM UTC

   ZixCentral and Zix Encryption Services - Secure Cloud Email Encryption (AEE/ZEE) is currently experiencing issues with slow page loads. Teams are currently assembled and working to resolve the issue. We appreciate your patience. Tracking Number: IM3880927

2. monitoring Mar 04, 2026, 04:08 PM UTC

   ZixCentral and Zix Encryption Services - Secure Cloud Email Encryption (AEE/ZEE) experienced an issue with slow loading pages. Service has been restored and is now being validated. We appreciate your patience. Tracking Number: IM3880927

3. resolved Mar 04, 2026, 08:21 PM UTC

   ZixCentral and Zix Encryption Services - Secure Cloud Email Encryption (AEE/ZEE) experienced a slow page load issue. The issue is now resolved. We appreciate your patience. Tracking Number: IM3880927

Read the full incident report →

Started Mar 01, 2026, 11:35 PM UTC· resolved Mar 02, 2026, 12:35 AM UTC

1. investigating Mar 01, 2026, 11:35 PM UTC

   We are currently experiencing performance degradation affecting the Core Archive service. Users may notice increased response times or intermittent access delays. Our engineering team is actively investigating and working toward resolution.

2. resolved Mar 02, 2026, 12:35 AM UTC

   Core Archive for SAP® Solutions - IN (archive.in.opentext.cloud) experienced service degradation. The issue is now resolved. We appreciate your patience. Tracking Number: IM3879652

Read the full incident report →

Started Mar 01, 2026, 02:35 PM UTC· resolved Mar 03, 2026, 03:32 PM UTC

1. identified Mar 01, 2026, 02:35 PM UTC

   We have identified an issue that is affecting our UK customer base that cannot access their Email Threat Protection logs or quarantine. We are working to resolve this issue as soon as possible. Incident #: IM3879529

2. identified Mar 01, 2026, 10:04 PM UTC

   We are continuing to work on resolving this issue with our network teams. Inbound mail flow is unaffected during this time. Incident #: IM3879529

3. identified Mar 02, 2026, 02:13 PM UTC

   The networking teams are still working on resolving this issue and are actively troubleshooting and progress is being made. We apologize for any inconvenience this may be causing. Incident #: IM3879529

4. identified Mar 02, 2026, 09:23 PM UTC

   Our team is actively working on bringing the server clusters fully back up. Email logs and Quarantine are loading as expected and final items are being restored. Incident #: IM3879529

5. resolved Mar 03, 2026, 03:32 PM UTC

   We have restored everything back to normal operational capacity. We apologize for any inconvenience this may have caused.

Read the full incident report →

Started Feb 26, 2026, 01:22 PM UTC· resolved Mar 02, 2026, 07:04 PM UTC

1. identified Feb 26, 2026, 01:22 PM UTC

   Core EDR/MDR is experiencing service degradation. Devices running macOS agent version 2.1.7 may experience incomplete or missing event log ingestion. The team has identified the cause and teams are working to resolve the issue. We appreciate your patience.

2. identified Feb 26, 2026, 02:22 PM UTC

   Core EDR/MDR is experiencing service degradation. Devices running macOS agent version 2.1.7 may experience incomplete or missing event log ingestion. The team has identified the cause and are working to resolve the issue. Updates for this issue will be sent every 4 hours or if there are significant updates, whichever comes first. We appreciate your patience.

3. identified Feb 26, 2026, 06:22 PM UTC

   Core EDR/MDR is experiencing service degradation. Devices running macOS agent version 2.1.7 may experience incomplete or missing event log ingestion. The team has identified the cause and is working to resolve the issue. Updates for this issue will be sent every 4 hours or if there are significant updates, whichever comes first. We appreciate your patience.

4. identified Feb 26, 2026, 10:26 PM UTC

   Core EDR/MDR is experiencing service degradation. Devices running macOS agent version 2.1.7 may experience incomplete or missing event log ingestion. The team has identified the cause and is working to resolve the issue. Updates for this issue will be sent every 4 hours or if there are significant updates, whichever comes first. We appreciate your patience.

5. identified Feb 27, 2026, 02:22 AM UTC

   Core EDR/MDR is experiencing service degradation. Devices running macOS agent version 2.1.7 may experience incomplete or missing event log ingestion. The team has identified the cause and is working to resolve the issue. Updates for this issue will be sent every 6 hours or if there are significant updates, whichever comes first. We appreciate your patience.

6. identified Feb 27, 2026, 08:32 AM UTC

   Core EDR/MDR is experiencing service degradation. Devices running macOS agent version 2.1.7 may experience incomplete or missing event log ingestion. The team has identified the cause and is working to resolve the issue. Updates for this issue will be sent every 6 hours or if there are significant updates, whichever comes first. We appreciate your patience.

7. identified Feb 27, 2026, 02:22 PM UTC

   Core EDR/MDR is experiencing service degradation. Devices running macOS agent version 2.1.7 may experience incomplete or missing event log ingestion. The team has identified the cause and is working to resolve the issue. Updates for this issue will be sent every 6 hours or if there are significant updates, whichever comes first. We appreciate your patience.

8. identified Feb 27, 2026, 10:09 PM UTC

   Core EDR/MDR is experiencing service degradation. Devices running macOS agent version 2.1.7 can experience event logs that may not appear as expected in the portal. All data continues to be processed by the agent. Our engineering team has identified the cause and is working to restore full visibility. The next update will be sent on Monday, March 2, 2026, at 14:00 UTC, or if there are significant updates, whichever comes first. We appreciate your patience.

9. identified Mar 02, 2026, 01:39 PM UTC

   Core EDR/MDR is experiencing service degradation. Devices running macOS agent version 2.1.7 can experience event logs that may not appear as expected in the portal. All data continues to be processed by the agent. Our engineering team has identified the cause and is working to restore full visibility. Updates for this issue will be sent every 12 hours or if there are significant updates, whichever comes first. We appreciate your patience.

10. resolved Mar 02, 2026, 07:04 PM UTC

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

Read the full incident report →

Started Feb 25, 2026, 05:29 PM UTC· resolved Feb 25, 2026, 06:41 PM UTC

1. investigating Feb 25, 2026, 05:29 PM UTC

   Zix Encryption Services - Email Message Privacy (EMP) is currently experiencing an issue where notifications are not generated when users send secure email from EMP Web Portal. Secure email notifications (invitation emails, password reset emails, secure email notifications) are not being generated when multiple users send secure emails from the DeliverySlip web portal. Users are unaware of sent secure emails or invitations. US Dallas Site501 (Zix DC) > DB0102 (PROD) Teams are currently assembled and working to resolve the issue. We appreciate your patience. Tracking Number: IM3876558

2. resolved Feb 25, 2026, 06:41 PM UTC

   Zix Encryption Services - Email Message Privacy (EMP) experienced an issue in which notifications are not generated when users send secure email from the EMP Web Portal. Secure email notifications (invitation emails, password reset emails, secure email notifications) are not being generated when multiple users send secure emails from the DeliverySlip web portal. Users are unaware of sent secure emails or invitations. US Dallas Site501 (Zix DC) > DB0102 (PROD). The issue is now resolved. We appreciate your patience. Tracking Number: IM3876558

Read the full incident report →

Started Feb 23, 2026, 09:28 PM UTC· resolved Feb 23, 2026, 09:34 PM UTC

1. identified Feb 23, 2026, 09:28 PM UTC

   We have identified and working on restoring access to our Customer Portal. We apologize for this inconvenience. IM tracking #: IM3875401

2. resolved Feb 23, 2026, 09:34 PM UTC

   We have restored access to the Customer Portal. We apologize for this brief outage.

Read the full incident report →

Started Feb 18, 2026, 07:46 PM UTC· resolved Feb 18, 2026, 08:31 PM UTC

1. investigating Feb 18, 2026, 07:46 PM UTC

   Webroot Management Consoles is currently experiencing service degradation and login issues. Teams are currently assembled and troubleshooting the issue. We appreciate your patience. Tracking Number: IM3872780

2. monitoring Feb 18, 2026, 08:27 PM UTC

   Webroot Management Consoles experienced service degradation and login issues. Service has been restored and is now being validated. We appreciate your patience. Tracking Number: IM3872780

3. resolved Feb 18, 2026, 08:31 PM UTC

   Webroot Management Consoles experienced service degradation and login issues. The issue is now resolved. We appreciate your patience. Tracking Number: IM3872780

Read the full incident report →

Started Feb 16, 2026, 02:10 PM UTC· resolved Feb 16, 2026, 03:29 PM UTC

1. investigating Feb 16, 2026, 02:10 PM UTC

   OpenText is currently experiencing an issue to generate new Exstream licenses. Teams are currently assembled and working to resolve the issue. We appreciate your patience. - Core Communications US - Core Communications Canada - Core Communications Australia Tracking Number: IM3871223

2. identified Feb 16, 2026, 03:15 PM UTC

   OpenText is currently experiencing an issue generating new Exstream licenses. The domain has been validated, and teams are working to resolve the issue. We appreciate your patience. - Core Communications US - Core Communications Canada - Core Communications Australia Tracking Number: IM3871223

3. resolved Feb 16, 2026, 03:29 PM UTC

   OpenText experienced an issue generating new Exstream licenses. The issue is now resolved. We appreciate your patience. Tracking Number: IM3871223

Read the full incident report →

Started Feb 16, 2026, 01:30 PM UTC· resolved Feb 16, 2026, 07:34 PM UTC

1. investigating Feb 16, 2026, 01:30 PM UTC

   Zix - Hosted Exchange (HEX) is currently experiencing an issue with some users unable to access their mailboxes. Teams are currently assembled and working to resolve the issue. We appreciate your patience. Tracking Number: IM3871043

2. investigating Feb 16, 2026, 01:34 PM UTC

   We are continuing to investigate this issue.

3. resolved Feb 16, 2026, 07:34 PM UTC

   Zix - Hosted Exchange (HEX) is resolved. Tracking Number: IM3871043

Read the full incident report →

Started Feb 15, 2026, 08:41 PM UTC· resolved Feb 15, 2026, 11:29 PM UTC

1. investigating Feb 15, 2026, 08:41 PM UTC

   Core Archive for SAP® Solutions CH (archive.emea.opentext.com) is inaccessible. Teams are currently assembled and working to resolve the issue. We appreciate your patience. Tracking Number: IM3870955

2. investigating Feb 15, 2026, 09:42 PM UTC

   Core Archive for SAP® Solutions CH (archive.emea.opentext.com) is inaccessible. Teams are assembled and working to resolve the issue. We appreciate your patience. Tracking Number: IM3870955

3. identified Feb 15, 2026, 10:43 PM UTC

   Core Archive for SAP® Solutions CH (archive.emea.opentext.com) is inaccessible. Teams have identified the cause and are working to resolve the issue. We appreciate your patience. Tracking Number: IM3870955

4. monitoring Feb 15, 2026, 11:20 PM UTC

   Core Archive for SAP® Solutions CH (archive.emea.opentext.com) was inaccessible. Service has been restored and monitoring is in progress. We appreciate your patience. Tracking Number: IM3870955

5. resolved Feb 15, 2026, 11:29 PM UTC

   Core Archive for SAP® Solutions CH (archive.emea.opentext.com) was inaccessible. The issue is now resolved. We appreciate your patience. Tracking Number: IM3870955

Read the full incident report →

Started Feb 15, 2026, 09:20 AM UTC· resolved Feb 15, 2026, 09:27 AM UTC

1. identified Feb 15, 2026, 09:20 AM UTC

   Core Archive for SAP® Solutions NA is currently inaccessible. The issue has been identified. Teams are currently assembled and working to resolve the issue. We appreciate your patience. Tracking Number: IM3870756

2. resolved Feb 15, 2026, 09:27 AM UTC

   Core Archive for SAP® Solutions NA was inaccessible. The issue is now resolved. We appreciate your patience. Tracking Number: IM3870756

Read the full incident report →

Started Feb 12, 2026, 05:11 AM UTC· resolved Feb 12, 2026, 05:11 AM UTC

1. resolved Feb 12, 2026, 05:11 AM UTC

   Alloy North America were unable to send documents. We observed health check failures on our Alloy AS2 server. The issue is now resolved. Please resend transactions that were sent from 11 February 2026 at 11:30 PM GMT. We appreciate your patience. Tracking Number: IM3869001

Read the full incident report →

Started Feb 11, 2026, 08:34 PM UTC· resolved Feb 12, 2026, 06:07 AM UTC

1. identified Feb 11, 2026, 08:34 PM UTC

   Core EDR/MDR is currently experiencing service degradation. Workflows are not running as expected. Teams have identified the cause and are working to resolve the issue. Please be advised that workflows for malware remediation may not function, and manual remediation may be required. We appreciate your patience. Tracking Number: 5196965

2. identified Feb 11, 2026, 09:35 PM UTC

   Core EDR/MDR is currently experiencing service degradation. Workflows are not running as expected. Teams have identified the cause and are working to resolve the issue. Please be advised that workflows for malware remediation may not function, and manual remediation may be required. We appreciate your patience. Tracking Number: 5196965

3. identified Feb 11, 2026, 10:34 PM UTC

   Core EDR/MDR is currently experiencing service degradation. Workflows are not running as expected. Teams have identified the cause and are working to resolve the issue. Please be advised that workflows for malware remediation may not function, and manual remediation may be required. Updates for this issue will be sent every 3 hours or if there are significant updates, whichever comes first. We appreciate your patience. Tracking Number: 5196965

4. monitoring Feb 12, 2026, 12:07 AM UTC

   Workflows have resumed normal operation; however, the platform is still experiencing partial service degradation. The team is actively monitoring system metrics and performance behavior to ensure stability. Updates for this issue will be sent every 3 hours or if there are significant updates, whichever comes first. We appreciate your patience. Tracking Number: 5196965

5. monitoring Feb 12, 2026, 03:08 AM UTC

   Workflows have resumed normal operation; however, the platform is still experiencing partial service degradation. The team is actively monitoring system metrics and performance behavior to ensure stability. Updates for this issue will be sent every 6 hours or if there are significant updates, whichever comes first. We appreciate your patience. Tracking Number: 5196965

6. resolved Feb 12, 2026, 06:07 AM UTC

   Core EDR/MDR operations have returned to normal, and all workflows are running as expected and no further service degradation is observed. This incident is now resolved. Our team will continue to observe post‑recovery metrics to ensure ongoing stability. Tracking Number: 5196965

Read the full incident report →

Started Feb 10, 2026, 02:57 PM UTC· resolved Feb 13, 2026, 04:14 PM UTC

1. investigating Feb 10, 2026, 02:57 PM UTC

   Zix - Hosted Exchange (HEX) is currently experiencing an issue with some users unable to access their mailboxes. Teams are currently assembled and working to resolve the issue. We appreciate your patience. Tracking Number: IM3867884

2. investigating Feb 10, 2026, 05:20 PM UTC

   While access has been restored for many users, some mailboxes are still currently impacted. Teams are currently assembled and working to resolve the issue. We appreciate your patience. Tracking Number: IM3867884

3. investigating Feb 11, 2026, 01:36 PM UTC

   Some mailboxes are still experiencing access issues, and we understand the impact this is having. Our teams are treating this as a top‑priority incident and are actively working to resolve the issue as quickly as possible. We sincerely apologize for the continued disruption and appreciate your patience while we work toward resolution. Tracking Number: IM3867884

4. monitoring Feb 12, 2026, 09:08 PM UTC

   All users identified as affected by this incident have been notified. Thank you for your patience throughout.

5. resolved Feb 13, 2026, 04:14 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Feb 06, 2026, 01:29 PM UTC· resolved Feb 09, 2026, 01:13 PM UTC

1. investigating Feb 06, 2026, 01:29 PM UTC

   Zix Encryption Services - Email Message Privacy (EMP) is currently experiencing an issue with file upload. Teams are currently assembled and working to resolve the issue. We appreciate your patience. Tracking Number: IM3865402

2. identified Feb 06, 2026, 04:38 PM UTC

   Zix - Cybersecurity - Zix Encryption Services - Email Message Privacy (EMP) is currently experiencing issues with file uploads and logins. Teams are currently assembled and working to resolve the issue. We appreciate your patience. Tracking Number: IM3865402

3. monitoring Feb 06, 2026, 05:35 PM UTC

   Zix - Cybersecurity - Zix Encryption Services - Email Message Privacy (EMP) experienced issues with file uploads and login errors. Service has been restored and is now being validated. We appreciate your patience. Tracking Number:

4. resolved Feb 09, 2026, 01:13 PM UTC

   Zix Encryption Services - Email Message Privacy (EMP) experienced issues with file uploads and logins. These issues are now resolved. We appreciate your patience. Tracking Number: IM3865402

Read the full incident report →

Started Feb 06, 2026, 10:09 AM UTC· resolved Feb 06, 2026, 07:10 PM UTC

1. investigating Feb 06, 2026, 10:09 AM UTC

   We are currently seeing issues with the following application in Core US. Teams are working towards identifying root cause. Core Collaboration for Engineering (xchange.us.opentext.com) Core Compliance Core Content Management Core Content Management for SAP® SuccessFactors

2. investigating Feb 06, 2026, 10:32 AM UTC

   The following applications have been resolved: Core US - Core Collaboration for Engineering (xchange.us.opentext.com) Core US - Core Compliance Teams are still working on resolving the issues with Core US - Core Content Management & Core US - Core Content Management for SAP® SuccessFactors

3. monitoring Feb 06, 2026, 11:42 AM UTC

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

4. resolved Feb 06, 2026, 07:10 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Feb 05, 2026, 04:34 PM UTC· resolved Feb 05, 2026, 04:34 PM UTC

1. resolved Feb 05, 2026, 04:34 PM UTC

   Core Archive for SAP® Solutions - US (archive.us.opentext.cloud) experienced an issue that started on 5 February 2026 at 15:30 GMT. Upload/download functionality was unavailable. Service has been restored at 16:00 GMT, and the issue is now resolved. We appreciate your patience. Tracking Number: IM3864715

Read the full incident report →

Started Feb 05, 2026, 03:33 PM UTC· resolved Feb 05, 2026, 05:16 PM UTC

1. investigating Feb 05, 2026, 03:33 PM UTC

   XM SendSecure - Canada is currently experiencing an issue. Clients can log in but are unable to send and receive documents. Teams are currently assembled and working to resolve the issue. We appreciate your patience. Tracking Number: IM3864671

2. investigating Feb 05, 2026, 04:30 PM UTC

   XM SendSecure - Canada is currently experiencing an issue. Clients can log in but are unable to send and receive documents. Teams are currently assembled and working to resolve the issue. We appreciate your patience. Tracking Number: IM3864671

3. monitoring Feb 05, 2026, 05:08 PM UTC

   XM SendSecure - Canada experienced an issue. Clients were unable to send and receive documents. Service has been restored on 5 February 2026 at 16:56 UTC and is now being validated. Any transactions that were sent from 4 February 2026 at 19:00 UTC will need to be resent. We apologize for the inconvenience. Tracking Number: IM3864671

4. resolved Feb 05, 2026, 05:16 PM UTC

   XM SendSecure - Canada experienced an issue. Clients were unable to send and receive documents. Service has been restored on 5 February 2026 at 16:56 UTC, and the issue is now resolved. Any transactions that were sent from 4 February 2026 at 00:00 UTC will need to be resent. We apologize for the inconvenience. Tracking Number: IM3864671

Read the full incident report →

Started Jan 29, 2026, 09:46 PM UTC· resolved Jan 29, 2026, 09:46 PM UTC

1. resolved Jan 29, 2026, 09:46 PM UTC

   Core Messaging - Email may have experienced intermittent message delivery delays, which started on 23 January 2026 at 05:00 UTC. Service has been restored on 29 January 2026 at 21:41 UTC. The issue is now resolved. We appreciate your patience. Tracking Number: IM3859146

Read the full incident report →