OpenText incident

Core EDR/MDR experienced service degradation

Minor Resolved View vendor source →

OpenText experienced a minor incident on March 23, 2026 affecting Core EDR/MDR, lasting 4h 49m. The incident has been resolved; the full update timeline is below.

Started
Mar 23, 2026, 02:44 PM UTC
Resolved
Mar 23, 2026, 07:34 PM UTC
Duration
4h 49m
Detected by Pingoru
Mar 23, 2026, 02:44 PM UTC

Affected components

Core EDR/MDR

Update timeline

  1. investigating Mar 23, 2026, 02:44 PM UTC

    Core EDR/MDR is currently experiencing service degradation. Workflows may not run as expected in the UK data center. Teams are currently assembled and working to resolve the issue. Please be advised that workflows for malware remediation may not run as expected, and manual remediation may be required. We appreciate your patience. Tracking Number: 5304133

  2. investigating Mar 23, 2026, 03:56 PM UTC

    Core EDR/MDR is currently experiencing service degradation. Workflows may not run as expected in the UK data center. Teams are currently assembled and working to resolve the issue. Please be advised that workflows for malware remediation may not run as expected, and manual remediation may be required. We appreciate your patience. Tracking Number: 5304133

  3. investigating Mar 23, 2026, 04:45 PM UTC

    Core EDR/MDR is currently experiencing service degradation. Workflows may not run as expected in the UK data center. Teams are currently assembled and working to resolve the issue. Please be advised that workflows for malware remediation may not run as expected, 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: 5304133

  4. identified Mar 23, 2026, 05:40 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 on a fix. Please be advised that workflows for malware remediation may not run as expected, 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: 5304133

  5. monitoring Mar 23, 2026, 06:48 PM UTC

    Core EDR/MDR experienced service degradation. Service has been restored and is now being validated. 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: 5304133

  6. resolved Mar 23, 2026, 07:34 PM UTC

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