Use cases
Software Products E-commerce MSPs Schools Development & Marketing DevOps Agencies Help Desk
Company
Internet Status Blog Pricing Log in Get started free

Outage in OpenText

Core EDR/MDR experienced a service degradation

Resolved Minor
April 23, 2026 - Started 2 days ago - Lasted 1 day
Official incident page

Incident Report

Summary AI Generated

OpenText's Core EDR/MDR service experienced a 25.6-hour degradation in the US Data Center where alerts in the portal failed to load as expected due to a core database issue. The service was restored through database restoration, but some alert records generated between April 23, 2026 02:00-13:00 UTC were permanently lost. Raw event data remained unaffected and available according to retention policies.

Core EDR/MDR experienced a service degradation. Alerts in the portal may not have loaded as expected in the US Data Center. The issue has been identified, and service is now restored. Teams are currently validating and monitoring the service. We appreciate your patience. Tracking Number: 5275019

Trusted by 1,000+ teams

Never miss outages in third-party dependencies

Stop finding out about outages from your users. Monitor 6,320+ cloud services and get alerted the second something breaks.

IsDown status aggregator dashboard
Latest Updates ( sorted recent to last )
RESOLVED about 22 hours ago - at 04/24/2026 05:27PM

Core EDR/MDR experienced a service degradation that required restoration of a core database. Because of this, some Alert records generated from 23 April 2026 02:00 UTC to 23 April 2026 13:00 UTC may no longer be available in the Alerts view.

This incident affected Alerts data only, raw event data was not impacted and remains available according to retention policies. The issue is now resolved. We appreciate your patience.

Tracking Number: 5275019

MONITORING 1 day ago - at 04/24/2026 03:13PM

Core EDR/MDR experienced a service degradation. Alerts in the portal may not have loaded as expected in the US Data Center. The issue has been identified, and service is now restored. Teams continue to monitor the service. The next update will be posted in 2 hours, or if there are significant updates, whichever comes first.

We appreciate your patience.

Tracking Number: 5275019

MONITORING 2 days ago - at 04/23/2026 07:45PM

Core EDR/MDR experienced a service degradation. Alerts in the portal may not have loaded as expected in the US Data Center. The issue has been identified, and service is now restored. Teams continue to monitor the service. The next update will be posted in 16 hours (24 April 2026, at 12:00 UTC), or if there are significant updates, whichever comes first.

We appreciate your patience.

Tracking Number: 5275019

MONITORING 2 days ago - at 04/23/2026 06:44PM

Core EDR/MDR experienced a service degradation. Alerts in the portal may not have loaded as expected in the US Data Center. The issue has been identified, and service is now restored. Teams continue to monitor the service. We appreciate your patience.

Tracking Number: 5275019

MONITORING 2 days ago - at 04/23/2026 03:52PM

Core EDR/MDR experienced a service degradation. Alerts in the portal may not have loaded as expected in the US Data Center. The issue has been identified, and service is now restored. Teams are currently validating and monitoring the service. We appreciate your patience.

Tracking Number: 5275019

Never miss outages in third-party dependencies

With IsDown, you can monitor all your critical services' official status pages from one centralized dashboard and receive instant alerts the moment an outage is detected. Say goodbye to constantly checking multiple sites for updates and stay ahead of outages with IsDown.

Start free trial

No credit card required · Cancel anytime · 6320 services available

Integrations with Slack Microsoft Teams Google Chat Datadog PagerDuty Zapier Discord Webhook