Carbonite Outage History

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 20, 2026, 07:16 PM UTC· resolved Feb 20, 2026, 09:55 PM UTC

1. investigating Feb 20, 2026, 07:16 PM UTC

   Core EDR/MDR is currently experiencing service degradation affecting API deployment in the UK datacenter and various integration configurations. Teams are currently assembled and working to resolve the issue. We appreciate your patience. Tracking Number: 5218367

2. identified Feb 20, 2026, 08:15 PM UTC

   Core EDR/MDR is currently experiencing service degradation affecting API deployment in the UK datacenter. Integrations have been restored. Teams are currently assembled and working to resolve the issue. We appreciate your patience. Tracking Number: 5218367

3. identified Feb 20, 2026, 09:15 PM UTC

   Core EDR/MDR is currently experiencing service degradation affecting API deployment in the UK datacenter. Integrations have been restored. Teams are currently assembled and working to resolve the issue. We appreciate your patience. Tracking Number: 5218367

4. resolved Feb 20, 2026, 09:55 PM UTC

   Core EDR/MDR experienced service degradation, which affected API deployment in the UK datacenter and various integration configurations. The issue is now resolved. We appreciate your patience. Tracking Number: 5218367

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, 05:30 PM UTC· resolved Feb 17, 2026, 02:34 PM UTC

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

   Core EDR/MDR is currently experiencing service degradation. Workflows may not run as expected in the US and UK data centers. Teams are currently assembled and 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.

2. investigating Feb 16, 2026, 06:36 PM UTC

   Core EDR/MDR is currently experiencing service degradation. Workflows may not run as expected in the US and UK data centers. Teams are currently assembled and 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 2 hours or if there are significant updates, whichever comes first. We appreciate your patience.

3. investigating Feb 16, 2026, 08:33 PM UTC

   Core EDR/MDR is currently experiencing service degradation. Workflows may not run as expected in the US and UK data centers. Teams are currently assembled and 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 2 hours or if there are significant updates, whichever comes first. We appreciate your patience.

4. investigating Feb 16, 2026, 10:31 PM UTC

   Core EDR/MDR is currently experiencing service degradation. Workflows may not run as expected in the US and UK data centers. Teams are currently assembled and 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 2 hours or if there are significant updates, whichever comes first. We appreciate your patience.

5. investigating Feb 17, 2026, 01:28 AM UTC

   Core EDR/MDR is currently experiencing service degradation. Workflows may not run as expected in the US and UK data centers. Teams are currently assembled and 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 2 hours or if there are significant updates, whichever comes first. We appreciate your patience.

6. investigating Feb 17, 2026, 03:45 AM UTC

   Core EDR/MDR is currently experiencing service degradation. Workflows may not run as expected in the US and UK data centers. Teams are currently assembled and 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 2 hours or if there are significant updates, whichever comes first. We appreciate your patience.

7. investigating Feb 17, 2026, 07:26 AM UTC

   Core EDR/MDR is currently experiencing service degradation. Workflows may not run as expected in the US and UK data centers. Teams are currently assembled and 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 2 hours or if there are significant updates, whichever comes first. We appreciate your patience.

8. investigating Feb 17, 2026, 09:27 AM UTC

   Core EDR/MDR is currently experiencing service degradation. Workflows may not run as expected in the US and UK data centers. Teams are currently assembled and 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.

9. investigating Feb 17, 2026, 12:27 PM UTC

   Core EDR/MDR is currently experiencing service degradation. Workflows may not run as expected in the US and UK data centers. Teams are currently assembled and 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.

10. resolved Feb 17, 2026, 02:34 PM UTC

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

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, 02:24 PM UTC· resolved Feb 12, 2026, 07:32 PM UTC

1. identified Feb 12, 2026, 02:24 PM UTC

   Core EDR/MDR is currently experiencing service degradation. Workflows may not run as expected in the UK data center. 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 12, 2026, 03:28 PM UTC

   Core EDR/MDR is currently experiencing service degradation. Workflows may not run as expected in the UK data center. 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 12, 2026, 04:28 PM UTC

   Core EDR/MDR is currently experiencing service degradation. Workflows may not run as expected in the UK data center. 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, 06:29 PM UTC

   Core EDR/MDR experienced service degradation. Service has been restored and is now being validated. We appreciate your patience. Tracking Number: 5196965

5. resolved Feb 12, 2026, 07:32 PM UTC

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

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 →

Started Jan 29, 2026, 03:43 PM UTC· resolved Jan 29, 2026, 09:18 PM UTC

1. investigating Jan 29, 2026, 03:43 PM UTC

   Email to our ticketing system is currently experiencing issues with long delays. Teams are currently assembled and working to resolve the issue. We appreciate your patience. Tracking Number: OTSM 51714775

2. monitoring Jan 29, 2026, 05:55 PM UTC

   Email to our ticketing system experienced an issue with long delays. Service has been restored and is now being validated. We appreciate your patience. Tracking Number: OTSM 51714775

3. resolved Jan 29, 2026, 09:18 PM UTC

   Email to our ticketing system experienced an issue with long delays. The issue is now resolved. We appreciate your patience. Tracking Number: OTSM 51714775

Read the full incident report →

Started Jan 29, 2026, 02:33 PM UTC· resolved Jan 29, 2026, 04:03 PM UTC

1. investigating Jan 29, 2026, 02:33 PM UTC

   The following services are unavailable. Teams are currently assembled and working to resolve the issue. We appreciate your patience. - OpenText Core Secure Access - OpenText Core Collaboration Access - ProviderLink login - B2B Connect (formerly Covisint Connect) login and UI capability; messaging is currently not impacted. - Supplier Connection login and UI; messaging is currently not impacted. Tracking Number: IM3860358

2. investigating Jan 29, 2026, 03:30 PM UTC

   The following services are unavailable. Teams are currently assembled and working to resolve the issue. We appreciate your patience. - OpenText Core Secure Access - OpenText Core Collaboration Access - ProviderLink login - B2B Connect (formerly Covisint Connect) login and UI capability; messaging is currently not impacted. - Supplier Connection login and UI; messaging is currently not impacted. Tracking Number: IM3860358

3. monitoring Jan 29, 2026, 03:51 PM UTC

   The following services experienced an issue and have been restored. - ProviderLink login - B2B Connect (formerly Covisint Connect) login and UI capability; messaging was not impacted. - Supplier Connection login and UI; messaging was not impacted. - Supplier Portal Core Secure Access and Core Collaboration Access are still being validated. We appreciate your patience. Tracking Number: IM3860358

4. resolved Jan 29, 2026, 04:03 PM UTC

   The following services experienced an issue and have all been restored. The issue is now resolved. We appreciate your patience. - OpenText Core Secure Access - OpenText Core Collaboration Access - ProviderLink login - B2B Connect (formerly Covisint Connect) login and UI capability; messaging is currently not impacted. - Supplier Connection login and UI; messaging is currently not impacted. Tracking Number: IM3860358

Read the full incident report →

Started Jan 22, 2026, 11:27 PM UTC· resolved Jan 23, 2026, 04:58 PM UTC

1. investigating Jan 22, 2026, 11:27 PM UTC

   Core EDR/MDR is currently experiencing an issue, causing the Support Team to be unable to receive emails. Teams are currently assembled and working to resolve the issue. We appreciate your patience. If you require immediate assistance, please contact our Support Team via phone at +1 866 658 2221.

2. investigating Jan 23, 2026, 12:28 AM UTC

   Core EDR/MDR is currently experiencing an issue, causing the Support Team to be unable to receive emails. Teams are currently assembled and working to resolve the issue. We appreciate your patience. If you require immediate assistance, please contact our Support Team via phone at +1 866 658 2221. Updates for this issue will be sent every 2 hours or if there are significant updates, whichever comes first.

3. investigating Jan 23, 2026, 02:27 AM UTC

   Core EDR/MDR is currently experiencing an issue, causing the Support Team to be unable to receive emails. Teams are currently assembled and working to resolve the issue. We appreciate your patience. If you require immediate assistance, please contact our Support Team via phone at +1 866 658 2221. Updates for this issue will be sent every 2 hours or if there are significant updates, whichever comes first.

4. investigating Jan 23, 2026, 04:27 AM UTC

   We are continuing to investigate the earlier issue. While email services appear to have been restored and messages are now being sent, some users may still experience degraded performance. Our team is actively monitoring the situation to ensure full stability. Further updates will be provided as more information becomes available. If you require immediate assistance, please contact our Support Team via phone at +1 866 658 2221. Updates for this issue will be sent every 2 hours or if there are significant updates, whichever comes first.

5. investigating Jan 23, 2026, 06:27 AM UTC

   We are continuing to investigate the earlier issue. While email services appear to have been restored and messages are now being sent, some users may still experience degraded performance. Our team is actively monitoring the situation to ensure full stability. Further updates will be provided as more information becomes available. If you require immediate assistance, please contact our Support Team via phone at +1 866 658 2221. Updates for this issue will be sent every 2 hours or if there are significant updates, whichever comes first.

6. investigating Jan 23, 2026, 08:27 AM UTC

   We are continuing to investigate the earlier issue. While email services appear to have been restored and messages are now being sent, some users may still experience degraded performance. Our team is actively monitoring the situation to ensure full stability. Further updates will be provided as more information becomes available. If you require immediate assistance, please contact our Support Team via phone at +1 866 658 2221. Updates for this issue will be sent every 4 hours or if there are significant updates, whichever comes first.

7. investigating Jan 23, 2026, 12:27 PM UTC

   We are continuing to investigate the earlier issue. While email services appear to have been restored and messages are now being sent, some users may still experience degraded performance. Our team is actively monitoring the situation to ensure full stability. Further updates will be provided as more information becomes available. If you require immediate assistance, please contact our Support Team via phone at +1 866 658 2221. Updates for this issue will be sent every 4 hours or if there are significant updates, whichever comes first.

8. resolved Jan 23, 2026, 04:58 PM UTC

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

Read the full incident report →

Started Jan 22, 2026, 07:59 PM UTC· resolved Jan 23, 2026, 01:01 PM UTC

1. investigating Jan 22, 2026, 07:59 PM UTC

   We are getting multiple reports of M365 users unable to send or receive emails. Microsoft has posted a couple of Service Alerts due to the volume of reports. At this time, the server alerts are providing general information. We will post an update as soon as they provide more details. Microsoft Service Alerts: Issue ID - MO1221364 As Microsoft rapidly pursue an investigation into the nature of the impact and the source of the issue, Microsoft received reports that users may be receiving a "451 4.3.2 temporary server issue" error message when attempting to access the service portals or use Outlook Issue ID - EX1221363 Microsoft is investigating a potential issue and checking for impact to your organization. Users may experience errors or failures when accessing their mailbox via one or more Exchange Online connection methods.

2. investigating Jan 22, 2026, 08:05 PM UTC

   Update from Microsoft: Issue ID - MO1221364 Some of the impacted service functions include, but may not be limited to: - Sending and receiving email through Exchange Online - Accessing service portals

3. identified Jan 22, 2026, 08:44 PM UTC

   Update from Microsoft: Issue ID - MO1221364 Microsoft identified a portion of dependent service infrastructure in the North America region that is not processing traffic as expected. This is impacting Microsoft load balancing processes and general service availability. Microsoft is working to restore this infrastructure to a heathy state and rebalance the service traffic to achieve recovery.

4. identified Jan 22, 2026, 09:18 PM UTC

   Update from Microsoft: Issue ID - MO1221364 Current status: While Microsoft restored the affected infrastructure to a heathy state, further load balancing is required to mitigate persistent impact. Microsoft identified and are implementing additional actions to direct requests and traffic to additional healthy sections of infrastructure to achieve withstanding recovery.

5. identified Jan 22, 2026, 10:11 PM UTC

   Issue ID - MO1221364 Microsoft has implemented a traffic balancing solution within a limited portion of infrastructure and telemetry shows success. Microsoft is applying this solution incrementally across all affected infrastructure to ensure the environment remains balanced as recovery continues. This quick update is designed to give the latest information on this issue.

6. identified Jan 22, 2026, 11:19 PM UTC

   Update from Microsoft: Issue ID - MO1221364 Current status: Microsoft is carefully rebalancing traffic across all affected infrastructure in the region, while monitoring the corresponding health telemetry, to ensure the environment enters into a balanced state as their remediation efforts continue. Microsoft is proceeding as quickly as possible and this incremental approach will also help them identify whether any additional actions may be required to ensure longstanding recovery.

7. identified Jan 23, 2026, 01:50 AM UTC

   Update from Microsoft: Issue ID - MO1221364 Current status: Microsoft is continuing to refine their load balancing configurations to remedy residual imbalances across the environment and further their ongoing recovery efforts.

8. monitoring Jan 23, 2026, 02:57 AM UTC

   Update from Microsoft: Issue ID - MO1221364 Microsoft is seeing continued improvements in service availability and functionality as a result of our load-balancing efforts. Microsoft is actively monitoring performance and making targeted adjustments to further improve stability and availability, while continuing recovery actions to ensure a reliable service experience.

9. resolved Jan 23, 2026, 01:01 PM UTC

   Update from Microsoft: Microsoft confirmed that the affected infrastructure has returned to a healthy state and is operating as expected. Microsoft will continue to closely monitor the remediation actions taken and make any necessary adjustments to maintain stability. If users experience any residual issues, clearing local DNS caches or temporarily lowering DNS TTL values may help ensure a quicker remediation.

Read the full incident report →

Started Jan 20, 2026, 08:15 PM UTC· resolved Jan 20, 2026, 09:44 PM UTC

1. investigating Jan 20, 2026, 08:15 PM UTC

   Core US is currently degraded. Teams are being assembled to investigate and provide resolution.

2. monitoring Jan 20, 2026, 08:34 PM UTC

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

3. resolved Jan 20, 2026, 09:44 PM UTC

   This incident has been resolved.

Read the full incident report →