Daily provider-status observations and published incident history for OpenText.
Component incident
OpenText has an active component incident; no global outage is indicated. Verified .
Official provider source.
Looking for an update now? Check the current status, or follow OpenText for future changes.
0%of 37 verified observed days had no reported provider issue
90-Day Trend
Dashed calendar markers below identify legacy observations whose source-at-observation was not recorded.
Monthly Status Summary
Month
Issue-free days
Days Tracked
Days with issues
September 2026
0%
30
30
This percentage summarizes normalized provider-status observations by calendar day. It is not duration-based, component-weighted, or contractual uptime. See the methodology and limitations.
Recorded Daily Status (Last 91 Days)
Jul 2Today
Legacy observation Operational Degraded Partial Outage Major Outage Maintenance No Data
Incident History
September 2026
Core DNS Protection Block Page is currently experiencing an issue
Core DNS Protection Block Page clients accessing blocked HTTPS websites may see a browser certificate warning instead of the DNS Protection block page. Blocked websites remain inaccessible, and DNS Protection continues to enforce policies as expected.
The required DNS Agent update, and a related client utility update is in progress. We appreciate your patience.
No customer action is required at this time. If further action becomes necessary, specific instructions will be provided. Updates for this issue will be sent by 1:00 PM Eastern tomorrow, or if there are significant updates, whichever comes first.
Tracking Number: I5791953
identified
Core DNS Protection Block Page clients accessing blocked HTTPS websites may see a browser certificate warning instead of the DNS Protection block page. Blocked websites remain inaccessible, and DNS Protection continues to enforce policies as expected.
Teams have scheduled the required DNS Agent update to begin today, and a related client utility update is also planned to be deployed. We appreciate your patience.
No customer action is required at this time. If further action becomes necessary, specific instructions will be provided. Updates for this issue will be sent every 6 hours or if there are significant updates, whichever comes first.
Tracking Number: I5791953
identified
Core DNS Protection Block Page clients accessing blocked HTTPS websites may see a browser certificate warning instead of the DNS Protection block page. Blocked websites remain inaccessible, and DNS Protection continues to enforce policies as expected.
Teams are implementing a fix, and the backend update is already in place. The required DNS Agent update is currently being validated before broader deployment, and a related client utility update is also planned to be deployed. We appreciate your patience.
No customer action is required at this time. If further action becomes necessary, specific instructions will be provided. Updates for this issue will be sent every 6 hours or if there are significant updates, whichever comes first.
identified
Core DNS Protection Block Page clients accessing blocked HTTPS websites may see a browser certificate warning instead of the DNS Protection block page. Blocked websites remain inaccessible, and DNS Protection continues to enforce policies as expected.
Teams are implementing a fix, and the backend update is already in place. The required DNS Agent update is currently being validated before broader deployment, and a related client utility update is also planned to be deployed. We appreciate your patience.
No customer action is required at this time. If further action becomes necessary, specific instructions will be provided. Updates for this issue will be sent on 28 September 2026 or if there are significant updates, whichever comes first.
Tracking Number: I5791953
identified
Core DNS Protection Block Page clients accessing blocked HTTPS websites may see a browser certificate warning instead of the DNS Protection block page. Blocked websites remain inaccessible, and DNS Protection continues to enforce policies as expected. Teams have identified the cause and are working to resolve the issue as quickly as possible.
No customer action is required at this time. If further action becomes necessary, specific instructions will be provided. Updates for this issue will be sent every 12 hours or if there are significant updates, whichever comes first. We appreciate your patience.
Tracking Number: I5791953
identified
Core DNS Protection Block Page clients accessing blocked HTTPS websites may see a browser certificate warning instead of the DNS Protection block page. Blocked websites remain inaccessible, and DNS Protection continues to enforce policies as expected. Teams have identified the cause and are working to resolve the issue as quickly as possible.
No customer action is required at this time. If further action becomes necessary, specific instructions will be provided. Updates for this issue will be sent every 12 hours or if there are significant updates, whichever comes first. We appreciate your patience.
Tracking Number: I5791953
identified
Core DNS Protection Block Page clients accessing blocked HTTPS websites may see a browser certificate warning instead of the DNS Protection block page. Blocked websites remain inaccessible, and DNS Protection continues to enforce policies as expected. Teams have identified the cause and are working to resolve the issue as quickly as possible.
No customer action is required at this time. If further action becomes necessary, specific instructions will be provided. Updates for this issue will be sent every 8 hours or if there are significant updates, whichever comes first. We appreciate your patience.
Tracking Number: I5791953
investigating
Core DNS Protection Block Page customers accessing blocked HTTPS websites may see a browser certificate warning instead of the DNS Protection block page. Blocked websites remain inaccessible, and DNS Protection continues to enforce policies as expected. Teams are currently assembled and working to resolve the issue.
No customer action is required at this time. If further action becomes necessary, specific instructions will be provided. We appreciate your patience.
Updates for this issue will be sent every 8 hours or if there are significant updates, whichever comes first.
Tracking Number: I5791953
investigating
Core DNS Protection Block Page customers accessing blocked HTTPS websites may see a browser certificate warning instead of the DNS Protection block page. Blocked websites remain inaccessible, and DNS Protection continues to enforce policies as expected. Teams are currently assembled and working to resolve the issue.
No customer action is required at this time. If further action becomes necessary, specific instructions will be provided. We appreciate your patience.
Updates for this issue will be sent every 8 hours or if there are significant updates, whichever comes first.
Tracking Number: I5791953
investigating
Core DNS Protection Block Page customers accessing blocked HTTPS websites may see a browser certificate warning instead of the DNS Protection block page. Blocked websites remain inaccessible, and DNS Protection continues to enforce policies as expected. Teams are currently assembled and working to resolve the issue.
No customer action is required at this time. If further action becomes necessary, specific instructions will be provided. We appreciate your patience.
Tracking Number: I5791953
investigating
Core DNS Protection Block Page customers accessing blocked HTTPS websites may see a browser certificate warning instead of the DNS Protection block page. Blocked websites remain inaccessible, and DNS Protection continues to enforce policies as expected. Teams are currently assembled and working to resolve the issue.
No customer action is required at this time. If further action becomes necessary, specific instructions will be provided. We appreciate your patience.
Tracking Number: I5791953
investigating
Core DNS Protection Block Page customers accessing blocked HTTPS websites may see a browser certificate warning instead of the DNS Protection block page. Blocked websites remain inaccessible, and DNS Protection continues to enforce policies as expected. Teams are currently assembled and working to resolve the issue.
No customer action is required at this time. If further action becomes necessary, specific instructions will be provided. We appreciate your patience.
Tracking Number: I5791953
Core Capture (corecapture.us.opentext.com)Core Platform - Content Transformation and Injection Services
monitoring
CTIS Service was in a degraded state in OCP US. Customers using CTIS-based ingestion in the OCP US environment may have experienced delays in processing submitted jobs. Service has been restored and is being validated. We appreciate your patience.
Tracking Number: IM4001177
investigating
Customers using CTIS-based ingestion in the OCP US environment may experience delays in processing submitted jobs. Jobs submitted through SFTP or email ingestion may remain in the “Starting” state for an extended period until CTIS service connectivity is restored.
Teams are currently assembled and working to resolve the issue. We appreciate your patience.
Tracking Number: IM4001177
investigating
We are continuing to investigate this issue.
investigating
Customers using CTIS-based ingestion in the OCP US environment may experience delays processing submitted jobs. Jobs submitted through SFTP or email ingestion may remain in the “Starting” state for an extended period until CTIS service connectivity is restored. Teams are assembled and actively looking at the issue for root cause and remediation
Reference: IM4001177
Frankfurt EU8 is currently experiencing service degradation
Frankfurt EU8 is currently experiencing service degradation. Customers may experience intermittent issues accessing the service.
Operations, Engineering, and Support teams are actively investigating the issue and working to restore service as quickly as possible. We are treating this as a high priority and will continue to closely monitor the environment while mitigation efforts are in progress.
We appreciate your patience and understanding. We will share more updates as they become available.
Tracking Number: IM4000627
Frankfurt EU8 experienced a service degradation. Service has been restored and is being validated. We appreciate your patience.
Tracking Number: IM3998323
investigating
Frankfurt EU8 is currently experiencing service degradation. Teams are currently assembled and working to resolve the issue. We appreciate your patience.
Tracking Number: IM3998323
Zix Archive Services - BCA and ZixArchive receiving Error 500
Zix Archive Services - Business Communication ArchiveZix Archive Services - ZixArchive
monitoring
Zix Archive Services BCA and ZixArchive experienced an issue when administrators navigated to the Archive pages of their respective interfaces. Service has been restored and is being validated. We appreciate your patience.
Tracking Number: IM3997654
investigating
Zix Archive Services BCA and ZixArchive are currently experiencing an issue when administrators navigate to the Archive pages of their respective interfaces. Teams are currently assembled and working to resolve the issue. We appreciate your patience.
Tracking Number: IM3997654
Frankfurt EU8 is currently experiencing service degradation
Frankfurt EU8 is currently experiencing service degradation with UCMDB service on EU8 farm. Clients may experience degradation while loading request entities or using an actual service on the EU8 farm. Teams are currently assembled and working to resolve the issue. We appreciate your patience.
Tracking Number: IM3995249
August 2026
Zix - M365 - Some users may be unable to connect to Microsoft 365 Exchange Online
Update from Microsoft:
All user impact scenarios are now resolved as they rectified the additional mitigation efforts for the Outlook impact which occurred in less than one percent of their infrastructure. They will continue to monitor their telemetry to ensure all services remain healthy and plan to close this communication by next update.
monitoring
Update from Microsoft:
Microsoft discovered an issue in less than one percent of their infrastructure, where additional mitigation efforts to resolve impact for Exchange Online did not successfully deploy. The vast majority of impact remains remediated; however, those serviced from the impacted portion of infrastructure may be unable to access previously recovered Outlook connection methods. Microsoft remains committed to restoring all services to all users and will continue to carefully moni...
monitoring
Update from Microsoft:
Their telemetry indicates service availability remains stable above 99 percent and expect the majority of users should no longer be seeing impact from this issue. The continued focus is on balancing the implementation of their fixes across remaining portions of affected infrastructure to ensure persistent recovery, with added attention on ensuring withstanding recovery of scenarios dependent on REST and Graph API connection methods.
monitoring
Update from Microsoft:
Microsoft continues to advance multiple workstreams to restore service and prevent additional impact. Microsoft is prioritizing infrastructure that requires the most immediate attention while carefully expanding corrective actions across additional regions, with continued monitoring throughout this process. In parallel, Microsoft is investigating remaining reports of impact and evaluating additional actions to support full service recovery.
monitoring
Update from Microsoft:
Microsoft observed continued recovery across previously impacted Exchange Online scenarios, with core mail flow functionality remaining healthy. Their focus remains on validating recovery across dependent Microsoft 365 experiences and confirming that remaining impact scenarios are fully addressed. They are maintaining enhanced monitoring while engineering teams complete end-to-end validation before determining whether any further corrective actions are required.
identified
Update from Microsoft:
A substantial portion of the remediation deployment has been completed, and organizations whose environments remain affected are expected to recover as the deployment reaches the relevant infrastructure. As remediation progresses, Microsoft is focused on validating sustained recovery and monitoring for any remaining pockets of impact before determining whether any additional corrective actions are required.
investigating
Update from Microsoft:
Microsoft is continuing to perform comprehensive tests to ensure their mitigation strategy effectively resolves the issue without introducing additional impact. In parallel, they are exploring alternative remediation avenues to minimize impact in the interim.
investigating
Update from Microsoft:
Microsoft has identified a potential corrective action for the affected infrastructure and are evaluating deployment options. They are monitoring service telemetry and affected Exchange Online transactions to determine whether the action is reducing impact and to better understand the scope of affected scenarios.
investigating
Update from Microsoft:
Microsoft isolated a common failure pattern across affected Exchange Online requests that is associated with authentication and protocol connectivity. They are analyzing service telemetry to identify the underlying source of impact and validate potential remediation options. Additionally, they are continuing to assess the scope of impact and monitor for additional affected scenarios.
More info - Users may experience a variety of symptoms related to this event, includi...
investigating
Microsoft O365 Exchange - some users are experiencing an issue connecting to Exchange 365. Microsoft is aware of the issue and has provided Issue ID: EX1464935.
Desktop Messaging BMS is currently experiencing delays in processing outbound fax delivery
Desktop Messaging BMS is currently experiencing delays in processing outbound fax delivery. Document backlogs exist and are currently being processed.
Teams are currently assembled and working to resolve the issue. We appreciate your patience.
Tracking Number: IM3987893
investigating
Desktop Messaging BMS is currently experiencing delays in processing outbound fax delivery. Document backlogs exist and are currently being processed.
Teams are currently assembled and working to resolve the issue. We appreciate your patience.
Tracking Number: IM3987893
Core Communications Europe was unavailable. Teams are currently assembled and working to resolve the issue. Service has been restored and is being validated. We appreciate your patience.
Tracking Number: IM3987509
investigating
Core Communications Europe is currently unavailable. Teams are currently assembled and working to resolve the issue. We appreciate your patience.
Tracking Number: IM3987509
MailStore Cloud was unavailable. Service has been restored and is being validated. We appreciate your patience.
investigating
MailStore Cloud is currently unavailable. Teams are currently assembled and working to resolve the issue. We appreciate your patience.
Legacy Incident Archive
97 archived records restored. These records predate source-at-observation attestation. They are shown as historical ServiceAlert records only and do not establish a provider-reported incident, resolution, duration, or current active state.
June 2026
Zix - Hex - Outlook connectivity Issue
majorSource not attested
Last archived state: resolved
View archived record details
monitoring
We want to inform you of a recent service disruption affecting Outlook connectivity to our Exchange environment.
Earlier today, during routine maintenance, some users experienced issues connecting to Outlook. Upon identifying the cause, our team promptly rolled back changes, which has resolved the issue.
Service has now been fully restored, and Outlook connectivity is functioning normally.
What you need to do:
No action is required. If you are still experiencing issues, we recommend restart...
investigating
We want to inform you of a recent service disruption affecting Outlook connectivity to our Exchange environment.
Earlier today, during routine maintenance, some users experienced issues connecting to Outlook. Upon identifying the cause, our team promptly rolled back changes, which has resolved the issue.
Service has now been fully restored, and Outlook connectivity is functioning normally.
Tracking Number: IM3942421
Content upload degraded in OCP US
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
A fix has been implemented and we are monitoring the environment
investigating
We are currently experiencing degradation in the OCP US environment impacting content uploads. Teams are engaged in troubleshooting to resolve the issue.
Zix Encryption Services - Secure Cloud Email Encryption (AEE) experienced an issue with the delayed processing of emails sent to the DLP service.
Service has been restored and is now being validated. We appreciate your patience.
Tracking Number: IM394167
investigating
Zix Encryption Services - Secure Cloud Email Encryption (AEE) is currently experiencing an issue with the delayed processing of emails sent to the DLP service.
Teams are currently assembled and working to resolve the issue. We appreciate your patience.
Tracking Number: IM394167
Core EDR/MDR experienced service degradation
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
Core EDR/MDR experienced service degradation. Partners in the U.S. data center may have experienced issues downloading agents. Service has been restored and is now being validated. We appreciate your patience.
Updates for this issue will be sent every 4 hours or if there are significant updates, whichever comes first.
If you have any questions or concerns, please reach out to the Support Team.
monitoring
Core EDR/MDR experienced service degradation. Partners in the U.S. data center may have experienced issues downloading agents. Service has been restored and is now being validated. We appreciate your patience.
If you have any questions or concerns, please reach out to the Support Team.
monitoring
Core EDR/MDR experienced service degradation. Partners in the U.S. data center may have experienced issues downloading agents. Service has been restored and is now being validated. We appreciate your patience.
If you have any questions or concerns, please reach out to the Support Team.
investigating
Core EDR/MDR is currently experiencing service degradation. Partners in the U.S. data center may experience issues downloading agents. Teams are currently assembled and working to resolve the issue. We appreciate your patience.
If you have any questions or concerns, please reach out to the Support Team.
Fax Cloud Connect (RightFax) and Fax2Mail experienced intermittent connectivity issues
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
Fax Cloud Connect (RightFax) and Fax2Mail experienced intermittent connectivity issues that started on 3 June 2026 at 10:26 UTC and were restored at 15:26 UTC. Clients were unable to access the portal to send faxes.
Service has been restored, and backlogs are being processed. We appreciate your patience.
Tracking Number: IM3938188
investigating
Fax Cloud Connect (RightFax) and Fax2Mail are currently experiencing intermittent connectivity issues that started on 3 June 2026 at 10:26 UTC. Clients are unable to access the portal to send faxes.
Teams are currently assembled and working to resolve the issue. Backlogs exist and are currently being processed. We appreciate your patience.
Tracking Number: IM3938188
Email Threat Protection Link Protection returning "service unavailable" sproadically
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
Our team is actively monitoring our fix and have seen sporadic reports of "Service Unavailable" when accessing wrapped URL's. Our team is monitoring the logs and have placed fixes in place to mitigate the errors quickly. The team is currently working on testing/deployment of a permanent hotfix for this issue as well.
We apologize for any inconvenience this may be causing.
Incident: IM3936734
ETP Link Protection wrap URL are not loading correctly
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
We have deployed a hotfix and are seeing improvements in the Link Protection scanning completing. We are currently monitoring to ensure the issue is fully reesolved.
Incident #:IM3936734
identified
We have identified the issue and are working with our engineering team to resolve the issue. We are seeing sporadic failures of our Link Protection and are continuing to work towards a resolution.
Incident #:IM3936734
identified
We have identified and issue with the ETP Link Protection service and are working to resolve this issue as soon as possible.
Incident #:IM3936734
Zix Encryption Services - ZixPortal Showing Message Expired when using link
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
Zix - Cybersecurity - Zix Encryption Services - ZixPortal experienced an issue with users receiving "Message Expired" and "Message Deleted" notifications.
Service has been restored and is now being validated.
We appreciate your patience.
Tracking Number: IM3936680
investigating
Zix Encryption Services - ZixPortal is currently experiencing an issue with using the link from the secure message portal invites. Teams are currently assembled and working to resolve the issue.
We appreciate your patience.
Tracking Number: IM3936680
May 2026
Multiple OCP applications are not available in both EU and NA
criticalSource not attested
Last archived state: resolved
View archived record details
monitoring
A fix has been implemented and we are monitoring the results.
identified
Multiple OCP applications are not available in both EU and NA. Teams are engaged and actively working towards a resolution
Email Threat Protection Link Protection returning "Service Unavilable"
minorSource not attested
Last archived state: resolved
View archived record details
investigating
We are currently investigating an issue in which our Link Protection is retuning a "service unavailable" error when accessing a protected link. Out internal teams are actively triaging the issue and will update as soon as more information is made available.
Incident: IM3935335
