OpenText Status Page

Aug 13, 2026 · resolved Aug 14

This incident has been resolved.

Aug 7, 2026 · resolved Aug 13

This incident has been resolved.

Aug 13, 2026 · resolved Aug 13

Desktop Messaging BMS experienced delays in processing fax files. The issue is now resolved. We appreciate your patience. Tracking Number: IM3978817

Aug 8, 2026 · resolved Aug 10

The issue affecting the CP Portal, where users may have encountered an "Unknown Error" message, has been identified and resolved by our Backend Engineering team. The fix has been successfully implemented, and services are now operating as expected. Tracking Number - IM3976014

Aug 9, 2026 · resolved Aug 10

**Root Cause Analysis** **Tracking number:** IM3976323 PM1011709 **Incident window:** August 9, 2026, from 01:00 GMT to 11:35 GMT **Services affected:** OpenText™ Shared Network Services **Overview** On August 9, 2026, at 06:24 GMT, Incident Management was engaged to investigate client-reported access issues affecting multiple OpenText SaaS services. **Impact** Clients were unable to access the OpenText SaaS services. **Root Cause** The investigation determined that a Domain Name System Security Extensions \(DNSSEC\) Key Signing Key \(KSK\) expired for the [microfocus.com](http://microfocus.com) DNS zone, resulting in DNS resolution failures across multiple services. This condition disrupted DNS resolution across multiple DNSSEC-enabled subzones, including [saas.microfocus.com](http://saas.microfocus.com), resulting in service inaccessibility. Furthermore, downstream propagation timelines and varying client-side caching behaviors extended recovery durations for a subset of endpoints. **Resolution** To mitigate the issue, the team implemented a configuration change to generate and apply new DNSSEC signing keys. The existing DNS signatures were removed, and the [microfocus.com](http://microfocus.com) DNS zone was re-signed using the newly generated keys. Following the configuration change, validation activities were completed successfully, and service was restored at 11:35 GMT, ending the impact. Note: Some clients may have continued to experience name-resolution issues due to stale DNS records cached within their internal DNS infrastructure, proxy servers, or firewall appliances. These issues should resolve once the cached DNS records expired or refreshed. **Action Plan** PM1011709-003: Review and optimize DNSSEC KSK alert triggers. - In progress - Target complete: August 14, 2026 PM1011709-004: Implement proactive internal monitoring and automated alert generation for DNSSEC key rollovers. - In progress - Target complete: September 4, 2026 PM1011709-006: Review incident escalation procedures to optimize the process. - In progress - Target complete: September 4, 2026 PM1011709-007: Evaluate external accessibility monitoring capabilities for critical application endpoints. - In progress - Target complete: September 4, 2026

Is OpenText down right now?

Yes — OpenText is reporting a major outage as of Aug 19, 9:40 PM UTC.

What is OpenText's current status?

OpenText: Partial System Outage. Alert24 checks OpenText's status page continuously and can notify you the moment it changes.

How do I get alerted when OpenText goes down?

Alert24 monitors OpenText and 3,700+ other cloud and SaaS providers. When an outage is detected it updates your status page automatically and pages your on-call team — no manual checks. Start free at alert24.net.